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
Android changes: Android is one of the largest downstream consumers of our work. Our continuous integeration tests the Android trees with newer versions of LLVM to help catch any issues that will impact Android once they upgrade their version of LLVM, which can lag behind at times.
Build errors: These are patches to fix various build errors that I found through testing different configurations with LLVM or were exposed by our continuous integration setup. The kernel needs to build in order to be run :)
Miscellaneous fixes: These are fixes that don’t fit into a particular category but are important to ClangBuiltLinux. In this case, I noticed that Chimera Linux was carrying a patch downstream to enable the stackprotector on x86_64 when cross compiling, which typically means the
--targetflag is missing somewhere, which I fixed with this patch.
x86/Kconfig: Fix CONFIG_CC_HAS_SANE_STACKPROTECTOR when cross compiling with clang(
Stable patches and backport requests: 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.
Warning fixes: These are patches to fix various warnings that appear with LLVM. 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…
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.
Re: [PATCH] netfilter: conntrack: fix this -Wformat clang warning:
Re: [PATCH] rtw88: 8821c: fix access const table of channel parameters
Re: [PATCH] s390: disable -Warray-bounds
Re: [PATCH v3] include/uapi/linux/swab.h: move explicit cast outside ternary
Re: [PATCH] KVM: SVM: Hide SEV migration lockdep goo behind CONFIG_DEBUG_LOCK_ALLOC
Re: [PATCH] hinic: Replace memcpy() with direct assignment
Re: [PATCH] Documentation/llvm: Update Supported Arch table
Re: [PATCH] Fix use of uninitialized variable in rts5261_init_from_hw, when efuse_valid == 1
Re: [PATCH 16/31] drm/amd/display: refactor function transmitter_to_phy_id
Re: [PATCH] [RFC] Kbuild: change CONFIG_FRAME_WARN for 32-bit
Re: [PATCH] scripts/Makefile.clang: set --target for host based on make -v
Re: [PATCH for-next 03/10] io_uring: fix io_poll_remove_all clang warnings
stage 4 & stage 5
Re: [PATCH] lib/test_printf.c: fix clang -Wformat warnings
Issue triage 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 09/15] swiotlb: make the swiotlb_init interface more useful
Re: [PATCH v11 1/4] trace: Add trace any kernel object
Considering uninitialized function parameters UB
LLD segfaults while linking drivers/scsi/megaraid/megaraid_mm.ko
Re: [PATCH v3 4/4] rtw88: Fix Sparse warning for rtw8821c_hw_spec
INIT_STACK_ALL_ZERO - Framework Laptop system freezes (kernel oops?) on boot
error: write on a pipe with no reader
"Unable to apply kernel patch" when git quiltimport works locally
-Wframe-larger-than in sound/soc/intel/avs/path.c
Contextual conflict between kspp and rcu trees
Re: linux-next: Tree for Jun 15 (drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c)
-Wunused-but-set-variable building perf
Re: [PATCH for-next v3 16/16] io_uring: mutex locked poll hashing
Re: [GIT PULL] Char/Misc driver fixes 5.19-rc3
Re: [PATCH] kbuild: pass jobserver to cmd_ld_vmlinux.o
Re: [TCWG CI] Regression caused by llvm: [GlobalOpt] Perform store->dominated load forwarding for stored once globals
Re: mainline build failure due to 281d0c962752 ("fortify: Add Clang support")
Triggered assertion from "mm: Add an assertion that PG_private and folio->private are in sync"
Re: [PATCH v1 1/2] arm64: vdso32: add ARM.exidx* sections
Re: Regression for duplicate (?) console parameters on next-20220630
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.
patches: Add RISC-V inline asm fixes to mainline and -next
Switch to self-hosted GitHub Actions for llvm-project
Update to Linux 5.18 and update known good revision
boot-uml.sh: Remove exec hack
build-llvm.py: Add LLVM_DEFAULT_TARGET_TRIPLE when possible
patches: mainline: Drop a RISC-V patch
Improve shell script style
ci.sh: Use release/14.x for testing
kernel/build.sh: Support all*config for Hexagon, RISC-V, and s390
ci/test-clang.sh: Skip toolchain archive creation when run locally
Improve podman compatibility
Add support for arm64 to llvm-project
Drop objtool patch on stable and 5.15
Fix tags and update Makefile workflow to match
github: build-test-llvm-project: Add build-args
Re-enable ChromeOS jobs
patches: mainline: Add a fix for ARCH=arm allmodconfig
patches: mainline: Drop watchdog patch
Drop -next patches (June 21st, 2022)
Disable ChromeOS jobs again
Drop mainline patches (June 24th, 2022)
kernel/build.sh: Print kernel version and small fix for header
Enable ChromeOS jobs (round 3)
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 Windows Subsystem for Linux instance, a Raspberry Pi 3 and 4, 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.