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
-
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 and improvements: These are fixes and improvements that don’t fit into a particular category but are important to ClangBuiltLinux.
-
Stable backports and fixes: 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.
Re: FAILED: patch "[PATCH] ARM: 9443/1: Require linker to support KEEP within OVERLAY" failed to apply to 6.13-stable tree
Re: FAILED: patch "[PATCH] ACPI: platform-profile: Fix CFI violation when accessing" failed to apply to 6.13-stable tree
Backports of 84ffc79bfbf7 for 6.12 and earlier
Please apply 8b55f8818900 to 6.12 through 6.1
lib/Kconfig.ubsan: Remove 'default UBSAN' from UBSAN_INTEGER_WRAP
(6.14
,6.12
)
-
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…drm/sysfb: efidrm: Avoid clang -Wsometimes-uninitialized in efidrm_device_create()
(v1
,v2
)riscv: Avoid fortify warning in syscall_get_arguments()
(v1
)ASoC: cs48l32: Use modern PM_OPS
(v1
)drm/panel: himax-hx8279: Always initialize goa_{even,odd}_valid in hx8279_check_goa_config()
(v1
,v2
)btrfs: Fix use of GCC_VERSION in messages.h
(v1
)scsi: dc395x: Remove leftover if statement in reselect()
(v1
)kbuild: Properly disable -Wunterminated-string-initialization for clang
(v1
)
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: [GIT PULL] string fixes for v6.15-rc1
Re: [PATCH 5.15 253/279] mmc: sdhci-brcmstb: Add ability to increase max clock rate for 72116b0
Re: [PATCH] ref_tracker: use %ld format specifier for PTR_ERR() during directory creation failure
Re: [PATCH] correct disabling of -Wshift-negative-value
Re: [PATCH] HID: simplify code in fetch_item()
Re: [PATCH] Bluetooth: vhci: Avoid needless snprintf() calls
Disable -fdollars-in-identifiers by default
Add basic support for building Rust
Re: [PATCH] kbuild: Switch from -Wvla to -Wvla-larger-than=0
Re: [PATCH] wifi: iwlwifi: mld: Work around Clang loop unrolling bug
Re: [PATCH v2] wifi: iwlwifi: mld: Work around Clang loop unrolling bug
Re: [PATCH 1/1] hardening: simplify CONFIG_CC_HAS_COUNTED_BY
Re: [PATCH] kunit: fix longest symbol length test
[C] Modify -Wdefault-const-init
__attribute__((nonstring)) and -Wunterminated-string-initialization
Re: [PATCH] kbuild: distributed build support for Clang ThinLTO
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 v10 2/2] riscv: Add runtime constant support
Re: [GIT PULL] more printk for 6.15
Re: [PATCH 6.1 051/198] Xen/swiotlb: mark xen_swiotlb_fixup() __init
Re: [PATCH v7 2/6] syscall.h: add syscall_set_arguments()
Re: [PATCH 6.13 444/499] x86/tdx: Fix arch_safe_halt() execution for TDX VMs
Boot failures on arm64 after LLVM commit b326cb6792b3951881d63d5a02ea163921da18d9
Build error in x86 vDSO with x32 enabled using clang and ld.lld
modpost errors due to undefined __ubsan_handle_*_overflow
LLVM assembler does not support '.set eva'
New instances of -Wframe-larger-than in arm64 allmodconfig with clang-17 and earlier after 6f110a5e4f99
Re: drivers/bluetooth/hci_vhci.o: error: objtool: vhci_coredump_hdr(): STT_FUNC at end of section
call to '__bad_copy_from' declared with 'error' attribute:
Re: [PATCH v2 0/2] pidfs: ensure consistent ENOENT/ESRCH reporting
Re: [PATCH 07/10] pinctrl: sx150x: enable building modules with COMPILE_TEST=y
Re: [PATCH] x86/e820: discard high memory that can't be addressed by 32-bit systems
Please apply 8dcd71b45df3 to 5.4
Re: [akpm-mm:mm-nonmm-unstable 66/67] fs/ocfs2/aops.c:1133:17: warning: variable 'i' is uninitialized when used here
[SDag][ARM][RISCV] Allow lowering CTPOP into a libcall
Adding __popcountsi2 and __popcountdi2
Re: clang and drm issue: objtool warnings from clang build
[C] Warn on uninitialized const objects
Re: [PATCH 6.1 000/167] 6.1.136-rc1 review
Tooling improvements
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.
Add wcslen() patch series to every tree that needs it
Apply 96dc364d483bc12ab6f49bd9c214b639497d6198 to android-mainline
Add android16-6.12
Add wcslen() patch to every tree that needs it (April 7, 2025)
patches: android-mainline: Drop .ARM.attributes patch
Apply 3d9c49ab to mainline trees
patches: Drop stable and 6.12 (April 21, 2025)
patches: Drop 6.6 and 6.1 (April 25, 2025)
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 Ampere Altra Developer Platform, two Intel-based desktops, 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.
-
I continue to upload prebuilt, fast versions of LLVM for kernel developers and our continuous integration to use.
Special thanks
Special thanks to Google and the Linux Foundation for sponsoring my work.