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: These are fixes and improvements that don’t fit into a particular category but are important to ClangBuiltLinux.
-
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.
-
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…coresight: cti-sysfs: Mark coresight_cti_reg_store() as __maybe_unused
(v1
)net/mlx5e: Ensure macsec_rule is always initiailized in macsec_fs_{r,t}x_add_rule()
(v1
,v2
)power: supply: bq25890: Fix enum conversion in bq25890_power_supply_set_property()
(v1
)drm/amd/display: Reduce number of arguments of dml314's CalculateWatermarksAndDRAMSpeedChangeSupport()
(v1
)drm/amd/display: Reduce number of arguments of dml314's CalculateFlipSchedule()
(v1
)thermal/intel/int340x: Initialized ret in error path in int340x_thermal_zone_add()
(v1
)usb: gadget: uvc: Fix argument to sizeof() in uvc_register_video()
(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: [PATCH] Makefile.extrawarn: re-enable -Wformat for clang; take 2
Re: [PATCH 0/2] fortify: Add run-time WARN for cross-field memcpy()
Re: [PATCH v4 00/21] KCFI support
Re: [PATCH v2 2/2] powerpc/math-emu: Remove -w build flag and fix warnings
Failure with zero call-used registers
Re: [PATCH v3 2/2] RISC-V: Clean up the Zicbom block size probing
Re: [PATCH v2 2/5] Makefile.compiler: Use KBUILD_AFLAGS for as-option
Re: [PATCH] powerpc/pseries: Fix plpks crash on non-pseries
Re: [PATCH v4] RISC-V: Clean up the Zicbom block size probing
Re: [PATCH] scripts/clang-tools: remove unused module
Re: [PATCH] fortify: Adjust KUnit test for modular build
Re: [PATCH] net: davicom: Fix return type of dm9000_start_xmit
Re: [PATCH] net: ethernet: ti: davinci_emac: Fix return type of emac_dev_xmit
Re: [PATCH] net: ethernet: litex: Fix return type of liteeth_start_xmit
Re: [PATCH] net: korina: Fix return type of korina_send_packet
Re: [PATCH] staging: rtl8192u: Fix return type of ieee80211_xmit
Re: [PATCH] staging: rtl8712: Fix return type of r8712_xmit_entry
Re: [PATCH] staging: rtl8723bs: Fix rtw_xmit_entry return type
Re: [PATCH v2] staging: r8188eu: Fix return type of rtw_xmit_entry
Re: [PATCH] drm/exynos: Fix return type for mixer_mode_valid and hdmi_mode_vali
Re: [PATCH] drm/i915: Fix return type of mode_valid function hook
Re: [PATCH] drm/msm: Fix return type of mdp4_lvds_connector_mode_valid
Re: [PATCH] drm/rockchip: Fix return type of cdn_dp_connector_mode_valid
Re: [PATCH] drm: xlnx: Fix return type of zynqmp_dp_connector_mode_valid
Re: [PATCH v2] staging: octeon: Fix return type of cvm_oct_xmit and cvm_oct_xmit_pow
Re: [PATCH] openvswitch: Change the return type for vport_ops.send function hook to int
Re: [PATCH] x86: Avoid relocation information in final vmlinux
Re: [PATCH 2/2] x86/paravirt: add extra clobbers with ZERO_CALL_USED_REGS enabled
Re: [PATCH] kbuild: Add an option to skip vmlinux.bz2 in the rpm's
Re: [PATCH v2] Compiler Attributes: Introduce __access_*() function attribute
Re: [PATCH v5 29/30] thermal/intel/int340x: Replace parameter to simplify
[C2x] reject type definitions in offsetof
[Clang] Don't warn if deferencing void pointers in unevaluated context
Re: [PATCH -next] Makefile: add implicit enum-conversion check for compile build
Re: [PATCH -next v2 0/2] Remove unused variables in x86/boot
Re: [PATCH] include/uapi/linux/swab: Fix potentially missing __always_inline
Re: [PATCH] Revert "kbuild: Check if linker supports the -X option"
Re: [PATCH] net: lan966x: Fix return type of lan966x_port_xmit
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: [kbuild-all] Re: powerpc-linux-objdump: Warning: Unrecognized form: 0x23
Re: [LKP] Re: [mm] d88f8edb09: dmesg.Kernel_panic-not_syncing:Fatal_exception
Re: [jpoimboe:s390 2/2] Unsupported relocation type: 26
Re: [linux-next:master 4627/4736] ld.lld: error: vmlinux.o:(.debug_info+0x2096020d): relocation R_AARCH64_ABS32 out of range: 4295813883 is not in
Re: drivers/usb/gadget/udc/fsl_qe_udc.c:624:4: warning: unannotated fall-through between switch labels
Re: drivers/gpu/drm/i915/display/intel_display.c:7539:3: warning: unannotated fall-through between switch labels
Re: [PATCH v2 1/3] powerpc/pseries: define driver for Platform KeyStore
ld.lld: error: undefined symbol: __tsan_mem{cpy,move,set}
Re: [arm-integrator:virt-to-pfn-v6.0-rc1 21/24] ld.lld: error: arch/powerpc/kernel/vdso/vdso32.lds:244: unknown directive: static
Re: [TCWG CI] Failure after v6.0-rc3-161-g9cb252c4c1c5: net: skb: export skb drop reaons to user by TRACE_DEFINE_ENUM
Re: machine_kexec_file.c:undefined reference to `__tsan_memset'
Re: [TCWG CI] Failure after v6.0-rc4-215-ge35ff25f9fda: Merge tag 'linux-kselftest-kunit-fixes-6.0-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest
Re: [PATCH 05/15] kbuild: build init/built-in.a just once
Re: [peterz-queue:call-depth-tracking 11/59] ld.lld: error: arch/x86/built-in.a(kvm.o at 12382) <inline asm>:48:149: expected newline
Re: [PATCH v2 2/3] fortify: Add KUnit test for FORTIFY_SOURCE internals
Illegal operation with clang + CONFIG_MARCH_Z13
__mulodi4 from u32_u32__int_overflow_test in lib/overflow_kunit.c
Re: mainline build failure (new) for x86_64 allmodconfig with clang
Re: [PATCH v2 7/8] arm64: alternatives: add alternative_has_feature_*()
Re: [kbuild-all] Re: [linux-next:master 6296/7172] ERROR: modpost: "kvm_spurious_fault" [arch/x86/kvm/kvm-intel.ko] undefined!
argument unused during compilation: '-march=armv6k'
Re: INFO: task systemd-udevd:94 blocked for more than 120 seconds.
Re: [PATCH v3 bpf-next 2/3] net: netfilter: add bpf_ct_set_nat_info kfunc helper
Several instances of -Wvoid-ptr-dereference
[Clang] Warn when trying to deferencing void pointers in C
Re: arch/arm/probes/kprobes/core.c:409:30: error: .fnstart must precede .save or .vsave directives
LLVM/GNU binutils interop: non-constant .uleb128 is not supported
die__process_unit: DW_TAG_label (0xa) @ <0x7b> not handled!
Re: [PATCH] Drivers: hv: vmbus: Split memcpy of flex-array
Re: [objtool] ca5e2b42c0: kernel_BUG_at_arch/x86/kernel/jump_label.c
Re: [PATCH v4] usb: gadget: uvc: increase worker prio to WQ_HIGHPRI
Fortify source failure in drivers/infiniband/core/cma.c with s390 allmodconfig
LLVM commit d1ad006a8f64bdc disables CONFIG_EFI_STUB
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.
Disable CONFIG_PSERIES_PLPKS for Fedora's ppc64le configuration
boot-utils: Remove skiboot
Disable CONFIG_KCSAN builds for tip of tree LLVM
patches: mainline: Drop mchp-spdiftx patch
boot-utils: Flush print commands to ensure output is properly ordered
Revert "generator.yml: Disable CONFIG_PSERIES_PLPKS for Fedora's ppc64le configuration"
patches: tip: Drop mchp-spdiftx patch
tc-build: Flush print commands to ensure output is properly ordered
Drop -next patches (September 14th, 2022)
Drop stable tree patches (September 15th, 2022)
Drop mainline patches (September 16th, 2022)
Fix location of '--patch-series' in tuxsuite commands
Apply drm/amd/display patches for dml314 to mainline
Add OpenSUSE's riscv64 configuration
Add Alpine Linux configurations
utils.py: Handle OpenSUSE riscv64 configuration in get_cbl_name()
Enable x86_64 KCSAN build on -next
Revert "patches: mainline: Apply drm/amd/display patches for dml314"
generate_workflow.py: Do not run TuxSuite workflows on pushes to the main branch
boot-qemu: Move from 'powernv8' to 'powernv' machine
patches: tip: Remove drm/amd/display patch
Disable OpenSUSE's RISC-V configuration when using GNU as
boot-utils: Update to latest main
Reduce permissions of GITHUB_TOKEN
Adjust CFI builds for kCFI
Add support for testing with LLVM
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, an Intel-based laptop, and a SolidRun Honeycomb LX2. 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 participated in the 2022 Linux Plumbers Conference in Dublin, Ireland, which was great for interfacing with the greater kernel community and making them more aware of our work.
Special thanks to:
- Google and the Linux Foundation for sponsoring my work.