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 failures: 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 :)
arm64: Improve HAVE_DYNAMIC_FTRACE_WITH_REGS selection for clang(
Downstream patches: Downstream consumers of our work are not always paying attention to the changes that we land every release so it is important to give them a little help. In this case, we had to disable
CONFIG_FORTIFY_SOURCEfor clang upstream since it was broken, which impacted Android. As this is an important security feature, it is important that it gets re-enabled once it is fixed, which is what the following change does.
Stable backports and patches: These are patches 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.
Backport of 4013e26670c5 and 60210a3d86dc for 4.9 to 5.10(
Fix two instances of -Wstrict-prototypes in drm/amd(
btrfs warning fixes for 5.15 and 5.17
Apply d799769188529abc6cbf035a10087a51f7832b6b to 5.17 and 5.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 everyone 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.
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.
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.
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, 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.
Two new blog posts, which may help other developers over time:
I wrote a Python script for easily driving QEMU, which is useful for testing new changes or verifying issues in a safe and easy to debug manner.