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 :)
-
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 and improvements: 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. 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…MIPS: Add prototypes for plat_post_relocation() and relocate_kernel()(v1)kselftest: Mark functions that unconditionally call exit() as __noreturn(v1)bcachefs: Fix format specifier in validate_bset_keys()(v1)drivers/s390: Fix instances of -Wcast-function-type-strict(v1)ALSA: scarlett2: Zero initialize ret in scarlett2_ag_target_ctl_get()(v1)bcachefs: Fix type of flags parameter for some ->trigger() implementations(v1)bcachefs: Fix format specifiers in bch2_btree_key_cache_to_text()(v1)drm/amd/display: Avoid -Wenum-float-conversion in add_margin_and_round_to_dfs_grainularity()(v1)drm/amd/display: Use frame_warn_flag consistently in dml2 Makefile(v1)
LLVM patches
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 v3] rust: make mutually exclusive with CFI_CLANGRe: [PATCH 1/4] kbuild: turn on -Wextra by defaultRe: [PATCH] ARM: Add a memory clobber to the fmrx instructionRe: [PATCH v2] ARM: Add a memory clobber to the fmrx instructionRe: [PATCH] kbuild: buildtar: Add arm supportRe: [PATCH 2/3] selftests: timers: Fix uninitialized variable warning in ksft_min_kernel_versionRe: [PATCH v2] kbuild: buildtar: Add explicit 32-bit arm supportRe: [PATCH] selftests: Mark ksft_exit_fail_perror() as __noreturnRe: [PATCH] ubsan: Add awareness of signed integer overflow trapsRe: [PATCH 0/2] Enable building of the devel RPM package from KbuildRe: [PATCH] x86/purgatory: Switch to the position-independent small code modelRe: [PATCH] x86: enable HAVE_LD_DEAD_CODE_DATA_ELIMINATIONRe: [PATCH] kbuild: buildtar: remove warning for the default caseRe: [RFC PATCH 2/2] objtool/powerpc: Enhance objtool to fixup alternate feature relative addressesRe: [RFC PATCH 2/9] x86/purgatory: Simplify stack handlingRe: [PATCH v5 4/7] soc: mediatek: Add MediaTek DVFS Resource Collector (DVFSRC) driverRe: [PATCH] ubsan: Avoid i386 UBSAN handler crashes with ClangRe: [PATCH v1 0/3] overlayfs: Optimize override/revert credsRe: [PATCH v2] ubsan: Avoid i386 UBSAN handler crashes with ClangRe: [PATCH] hardening: Refresh KCFI options, add some more
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.
[linux-6.1.y] MIPS: ./scripts/check-local-export: llvm-nm failedRe: [PATCH v4 05/13] mm/arch: Provide pud_pfn() fallbackRe: kernel/sched/core.c:961:15: error: incompatible pointer to integer conversion passing 'typeof-Wduplicate-decl-specifier and LLVM "error in backend: Unsupported expression in static initializer" crash trying to enable CONFIG_USE_X86_SEG_SUPPORTRe: [PATCH v6 01/37] fix missing vmalloc.h includes-Wframe-larger-than in drivers/media/platform/mediatek/vcodec/decoder/vdec/vdec_vp9_req_lat_if.c with ARCH=loongarch allmodconfigRe: [PATCH net-next v11 01/13] net: phy: Introduce ethernet link topology representation[RemoveDIs] Add flag to preserve the debug info format of input IRCoCo code breaks with CFIkexec_file is broken with LLVM 18 and newer on x86_64Kernel BUG() on Linux 6.8 with Clang 17+ and LTO, rt5640 audio failsi386 without CONFIG_X86_CMPXCHG64 "error: inline assembly requires more registers than available" in kernel/bpf/core.c after commit 95ece48165c1 in -nextFortify warning in net/xfrm/xfrm_user.c with arm64 CONFIG_KASAN=y after LLVM commit 90ba33099cbb1BOLT's stage system requirementsRe: [PATCH rdma-next v3 4/6] RDMA/mana_ib: enable RoCE on portRe: [PATCH 10/11] fs/ntfs3: Remove cached label from sbiKASAN does not seem to work (no "KASAN init done" in dmesg) when kernel is built with clang (kernel 6.9-rc4, ppc32, clang-18)
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.
Update default PGO kernel to 6.8.0 and update known good revisionUpdate patches (April 3, 2024)Add and enable Fedora LTO buildUpdate korg-clang-18 to 18.1.3Disable CONFIG_DRM_WERROR when CONFIG_WERROR is disabledDrop arm64 patches due to 6.9-rc3 fast forwardpatches: Drop 5.15x86: Update machine and fix '--efi'Drop '-mhard-float' patch everywhereUpdate korg-clang-18 to 18.1.4Update patches (April 25, 2024)patches: Drop Bluetooth patch from -tipDrop RISC-V GKI builds
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, 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.
-
I ran the April 3rd and April 17th ClangBuiltLinux meetings.
-
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.