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 and improvements: These are fixes and improvements that don’t fit into a particular category but are important to ClangBuiltLinux.
Allow CONFIG_PPC64_BIG_ENDIAN_ELF_ABI_V2 with ld.lld 15+(
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…
f2fs: Fix type of single bit bitfield in f2fs_io_info(
ASoC: mchp-spdifrx: Fix uninitialized use of mr in mchp_spdifrx_hw_params()(
dm flakey: Fix clang -Wparentheses-equality in flakey_map()(
drm: omapdrm: Do not use helper unininitialized in omap_fbdev_init()(
net/sched: cls_api: Move call to tcf_exts_miss_cookie_base_destroy()(
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.
static call fixes for clang's conditional tail calls (6.2 and 6.1)(
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] Documentation/llvm: add Chimera Linux, Google and Meta datacenters
Re: [PATCH v2] tools/resolve_btfids: Tidy host CFLAGS forcing
Re: [PATCH bpf-next] tools/resolve_btfids: Compile resolve_btfids as host program
Re: [PATCH] arm64: kprobes: Drop ID map text from kprobes blacklist
Re: [PATCH] x86/vdso: Fake 32bit VDSO build on 64bit compile for vgetcpu.
Re: [PATCH] randstruct: disable Clang 15 support
Re: [PATCH 00/10] objtool: Honey, I shrunk the instruction
Re: [PATCH] RDMA/cma: Distinguish between sockaddr_in and sockaddr_in6 by size
Re: [PATCH] rust: allow to use INIT_STACK_ALL_ZERO
Re: [PATCH] EDAC/amd64: remove unneeded call to reserve_mc_sibling_devs()
[llvm][SelectionDAGBuilder] use getRegistersForValue to generate legal copies
Re: [PATCH] powerpc/vmlinux.lds: Add .text.asan/tsan sections
Re: [PATCH] kbuild: rpm-pkg: remove unneeded KERNELRELEASE from modules/headers_install
Re: [PATCH] kbuild: modinst: Enable multithread xz compression
RISC-V: avoid build issues for clang/llvm-17 with binutils 2.35
Re: [PATCH] hw/mips/gt64xxx_pci: Don't endian-swap GT_PCI0_CFGADDR
[PowerPC] Recognize long CPU name for -mtune in Clang
Re: [PATCH v2] MIPS: Workaround clang inline compat branch issue
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.
[BOLT] Missing VCSRevision.h dependency
Alpine/Musl segfault when building BOLT in stage 3
Fortify source failure in drivers/infiniband/core/cma.c with s390 allmodconfig
Re: [PATCH v7 2/6] arm64: kernel: move identity map out of .text mapping
Re: [PATCH 6.1 00/28] 6.1.10-rc1 review
Re: [linux-next:master 8959/10357] ld.lld: error: no machine record defined
Re: [TCWG CI] Failure after v6.1.8-105-gf5e58b546cbe: drm/panfrost: fix GENERIC_ATOMIC64 dependency
Re: x86/include/asm/arch_hweight.h:49:15: error: invalid input size for constraint 'D'
Re: [PATCH v4 6/6] Driver: VMBus: Add device tree support
Re: [PATCH qemu v3] x86: don't let decompressed kernel image clobber setup_data
static calls on x86_64 are broken with clang conditional tail calls
x86_64 kernels fail to boot after D140931
Re: [PATCH -next v2 1/3] driver core: add error handling for devtmpfs_create_node()
Clang THINLTO BTRFS balance dmesg regression with RAID
'power10' is not a recognized processor for this target (ignoring processor)
Re: stable-rc: 5.10: riscv: defconfig: clang-nightly: build failed - Invalid or unknown z ISA extension: 'zifencei'
Invalid or unknown z ISA extension: 'zifencei'
Re: [PATCH] gpu: host1x: fix uninitialized variable use
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.
Disable s390 builds with LLVM < 13 on 5.10
Replace Exception with more specific RuntimeError
boot-utils: Fix new pylint warnings
Enable KCSAN on stable
scripts/markdown-badges.py: Stop relying on parse_version()
Add patches for current issues (February 8th, 2023)
Add support for LLVM 16
Add script to locally build TuxSuite configurations
Update patches (February 23, 2023)
boot-qemu.py: Rewrite using classes
patches: mainline: Add fix for host1x -Wuninitialized warning
patches: stable: Drop alternatives series
Initial stab at front end cache checks
Follow up fixes for ruff
Add script to print the number of builds done per week per workflow
patches: Drop next series (February 28, 2023)
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 February 22nd, 2023 ClangBuiltLinux bi-weekly meeting/sync and took notes.