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.
-
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] drm/xe: Fix warning on impossible condition
Re: [PATCH] scripts/min-tool-version.sh: Raise min clang version to 18.0.0 for loongarch
RISC-V boot failure after LLVM commit e87f33d9ce785668223c3bcc4e06956985cccda1
Re: [PATCH] Compiler Attributes: counted_by: bump compiler versions
Re: [PATCHv2 1/2] Compiler Attributes: counted_by: bump min gcc version
Re: [PATCHv2 2/2] Compiler Attributes: counted_by: fixup clang URL
Re: [PATCH 1/1] Fix a wrong value passed to __find_vmap_area()
Re: [PATCH] docs: kbuild/kconfig: reformat/cleanup
check all builds for metadata
Re: [RFC PATCH 4/5] x86/head64: Replace pointer fixups with PIE codegen
[lld] Add target support for SystemZ (s390x)
Re: [PATCH v2 00/17] x86: Confine early 1:1 mapped startup code
Re: [PATCH linux-next v3 00/14] Split crash out from kexec and clean up related config items
Re: [RFC] arm64: use different compiler inlining options for arm64 kernel builds
Re: [PATCH] RISC-V: fix check for zvkb with tip-of-tree clang
Re: [PATCH] crypto: virtio/akcipher - Fix stack overflow on memcpy
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.
clang-nightly images have not been updated in three weeks
Re: [bcachefs:header_cleanup 21/51] /bin/bash: line 1: 19420 Segmentation fault...
New fortify warning in fs/smb/client/cifsencrypt.c after LLVM commit d77067d08a3f56dc2d0e6c95bd2852c943df743a
[MC][RISCV][LoongArch] Add AlignFragment size if layout is available and not need insert nops
[LoongArch] Allow delayed decision for ADD/SUB relocations
Re: [PATCH v4 2/4] arch/x86: Move internal setup_data structures into setup_data.h
Re: riscv: clang-nightly-allmodconfig: failed on stable-rc 6.6 and 6.1
Clang 18.0.0: Linux 6.1 and 6.6 giving unused-variable warnings despite used attribute
Compile time fortify warning in Linux kernel after commit d77067d08a3f56d
Re: drivers/net/ethernet/mellanox/mlx5/core/esw/bridge.c:1833:4: warning: 'snprintf' will always be truncated; specified size is 80, but format string expands to at least 94
Re: [akpm-mm:mm-nonmm-unstable 22/23] lib/group_cpus.c:352:16: error: array initializer must be an initializer list
Segmentation fault in modpost when building UML on mainline after LLVM commit 4bf8a688956a
Link failure when building UML on linux-6.1.y after LLVM commit ec92d74a0ef89
Re: [GIT PULL]: dmaengine updates for v6.8
Fio test trigger ext4 kernel panic
LoongArch clang-nightly container appears to be stale
AMD64 segfault during LTO building linux-6.7.0 with clang-17.0.6
Re: [PATCH -next v21 23/27] riscv: detect assembler support for .option arch
Re: [PATCH v2 2/4] modpost: inform compilers that fatal() never returns
Support C++20 Modules in clang-repl
Re: [PATCH 5.10 000/286] 5.10.209-rc1 review
Re: [PATCH] tty: serial: amba-pl011: Remove QDF2xxx workarounds
Re: [PATCH v4 08/10] workqueue: Introduce struct wq_node_nr_active
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 stable to 6.7 and add separate 6.6 builds
android15-6.6
Update LoongArch builds for latest developments
tc_build: kernel: Add support for LoongArch
Update default PGO kernel to 6.7.0 and update known good revision
Fix ChromeOS arm64 fragment name
Add chromeos-6.1 and chromeos-6.6
Fix ChromeOS x86_64 configurations
Update LLVM tip of tree anchor to 19
Decompose generator.yml
Patch all outstanding failures (Jan 24, 2024)
Add support for RISC-V LTO on -next
Add a patch to fix the PowerPC build on 5.4
Combine certain YAML files further
Restructure repository and add documentation
Update patches (January 27, 2024)
patches: next: Drop ARCH=um series
caching: Add hash of contents of patches folder
patches: tip: Drop smb __bdos() patch
build-binutils.py: 2.42
patches: arm64-fixes: Drop smb __bdos() patch
Drop LLVM 11/12 builds on -next and LLVM 11 builds on mainline
Attempt to rebalance builds
Temporarily disable LLVM tip of tree builds for RISC-V
Update {upload,download}-artifact actions to v4
Add LLVM 18 builds
workflows: python_lint: Update setup-python action to v5
boot-qemu.py: Fix GDB check in QEMURunner
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 January 10th and January 24th ClangBuiltLinux meetings.
-
I continue to upload stable LLVM releases to kernel.org to ensure kernel developers have easy access to LLVM for reproducing and fixing issues that they introduce.
Special thanks
Special thanks to Google and the Linux Foundation for sponsoring my work.