Occasionally, I will forget to link something from the mailing list in this post. To see my full mailing list activity (patches, reviews, and reports), you can view it on lore.kernel.org.
Linux kernel patches
Downstream fixes: These are fixes and improvements that occur in a downstream Linux tree, such as Android or ChromeOS, which our continuous integration regularly tests.
Miscellaneous fixes: These are fixes and improvements that don’t fit into a particular category but are important to ClangBuiltLinux.
Warning fixes: These are patches to fix various warnings that appear with LLVM (or in the case of the first one, with GCC as the result of a patch series for ClangBuiltLinux). I used to go into detail about the different warnings and what they mean, but the important takeaway for this section is that the kernel should build warning free, as all developers should be using
CONFIG_WERROR, which will turn these all into failures. Maybe these should be in the build failures section…
Stable backports: It is important to make sure that the stable trees are as free from issues as possible, as those are the trees that devices and users use; for example, Android and Chrome OS regularly merge from stable, so if there is a problem that will impact those trees that we fixed in mainline, it should be backported.
Patch review and input
For the next sections, I link directly to my first response in the thread when possible but there are times where the link is to the main post. My responses can be seen inline by going to the bottom of the thread and clicking on my name.
Reviewing patches that are submitted is incredibly important, as it helps ensure good code quality due to catching mistakes before the patches get accepted and it can help get patches accepted faster, as some maintainers will blindly pick up patches that have been reviewed by someone that they trust.
MIPS: fix build from IR files, nan2008 and FpAbi
Re: [PATCH 1/3] KVM: arm64: vgic: Add Apple M2 cpus to the list of broken SEIS implementations
Re: Linux 6.2-rc2
Re: [PATCH] ext4: Fix function prototype mismatch for ext4_feat_ktype
Re: [RFC PATCH tip] rseq: Fix: Increase AT_VECTOR_SIZE_BASE to match rseq auxvec entries
Re: [PATCH] crypto: hisilicon: Wipe entire pool on error
Re: [PATCH v2] kbuild: rust: remove -v option of scripts/rust_is_available.sh
Re: [PATCH v3] kbuild: export top-level LDFLAGS_vmlinux only to scripts/Makefile.vmlinux
Re: [PATCH] efi: tpm: Avoid READ_ONCE() for accessing the event log
Re: [PATCH] arm64: Fix build with CC=clang, CONFIG_FTRACE=y and CONFIG_STACK_TRACER=y
[Clang][Sema] Enabled implicit conversion warning for CompoundAssignment operator.
Re: [RFT PATCH 0/2] arm64: efi: Call SetVaMap() with a 1:1 mapping
Re: [PATCH] powerpc: add crtsavres.o to always-y instead of extra-y
Re: [PATCH] MIPS: remove CONFIG_MIPS_LD_CAN_LINK_VDSO
Re: [PATCH] arm64: head: Switch endianness before populating the ID map
Re: [PATCH] udf: remove reporting loc in debug output
Re: [PATCH] gpu: host1x: fix uninitialized variable use
Issue triage, input, and reporting
The unfortunate thing about working at the intersection of two projects is we will often find bugs that are not strictly related to the project, which require some triage and reporting back to the original author of the breakage so that they can be fixed and not impact our own testing. Some of these bugs fall into that category while others are issues strictly related to this project.
Re: [PATCH v2] arch: fix broken BuildID for arm64 and riscv
Re: [PATCH 02/30] rseq: Introduce feature size and alignment ELF auxiliary vector entries
Re: next: clang-15: s390x-linux-gnu-ld: BFD (GNU Binutils for Debian) 2.35.2 assertion fail ../../bfd/elf64-s390.c:3349
Re: [PATCH 4/8] migrate_pages: split unmap_and_move() to _unmap() and _move()
-Wattribute-warning in drivers/crypto/hisilicon/sgl.c
-Wattribute-warning in drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_bloom_filter.c
"Synchronous Exception at..." when booting arm64 kernel built with CONFIG_LTO_CLANG_THIN=y
nm vmlinux error in arch/arm reappears after upgrade to make 4.4
Re: [PATCH v3 2/2] arm64: efi: Account for the EFI runtime stack in stack unwinder
error: cannot be defined in '__builtin_offsetof' (Kernel 6.1.5)
Re: [PATCH 4.14 230/338] wifi: brcmfmac: Fix potential shift-out-of-bounds in brcmf_fw_alloc_request()
clang 15 fails ppc64 BE kernel build - ld.lld: error: undefined symbol: .early_setup (kernel 6.1-rc5, powerpc64-gentoo-linux-musl)
Missing cfi_ignorelist.txt in tuxmake images
Re: [PATCH 5/6] hw/mips/gt64xxx_pci: Endian-swap using PCI_HOST_BRIDGE MemoryRegionOps
Re: [PATCH v7 4/6] arm64: head: avoid cache invalidation when entering with the MMU on
Re: [PATCH v4 2/2] tools/resolve_btfids: Alter how HOSTCC is forced
These are changes to various tools that we use, such as our continuous integration setup, booting utilities, toolchain building scripts, or other closely related projects such as AOSP’s distribution of LLVM and TuxMake.
build-binutils.py: Fix using relative paths for folders
patches: mainline: Add tentative fix for 99cb0d917ff
Revert OpenSUSE configuration changes
Remove -next patches (January 4th, 2023)
4.9 is now EOL
Add support for LoongArch
Print total script durations
Drop mainline patch (January 23, 2023)
Update kernel to 6.1.7 and bump known good revision
LLVM main is now 17
patches: android13-5.10: Remove pahole series
docker: install libclang-rt-dev on LLVM 14+
Behind the scenes
- Every day that there is a new linux-next release, I rebase and build a few different kernel trees then boot and runtime test them on several different machines, including a Raspberry Pi 4, a Raspberry Pi 3, a SolidRun Honeycomb LX2, an Intel-based desktop, an AMD-based desktop, and an Intel-based laptop. This is not always visible because I do not report anything unless there is something broken but it can take up to a few hours each day, depending on the amount of churn and issues uncovered.
Special thanks to Google and the Linux Foundation for sponsoring my work.