On Fri, 16 Oct 2026 11:28:20 -0400 Sasha Levin <[email protected]> wrote: > > Changes since v2: > - Keep the skills in agents/. They are now short pointers into > Documentation/ rather than documentation of their own; see the > discussion on v1 [3]. > - Cut each skill to a single short SKILL.md that points at the existing > documentation, and drop the git how-to (Kees). The skill text went > from about 960 lines to 250.
Thanks for both of these -- it does seem simpler to me this way, which is what I expected. > - Drop the 100 line limit and the exclusion of theoretical issues from > stable-kernel-rules.rst, and require a fix to be correct rather than > obviously correct. If we are going to have a skill for the stable bit and you are updating the list, then may we take the chance to include Rust soundness issue? Please see below. Thanks! Cheers, Miguel >From c2459728a744144a592b45b5b8b807c0f15b8608 Mon Sep 17 00:00:00 2001 From: Miguel Ojeda <[email protected]> Date: Fri, 16 Oct 2026 17:37:25 +0200 Subject: [PATCH] docs: stable-kernel-rules: mention Rust soundness issues Back in 2023 I asked the stable kernel team whether we could consider Rust soundness issues for backporting, since we wanted to be able to protect (as much as possible) downstream users of stable kernels. After the Rust experiment ended, I documented it in the "Submit checklist addendum" in our "Subsystem Profile document" [1] (i.e. `P:` entry in `MAINTAINERS`): #### Soundness issues and backporting In general, fixes for Rust soundness issues should be marked for backport, unless there is a reason not to (such as situations where the backport may require a lot of effort but the risk of users hitting UB is low). For context, while the stable kernel rules mention "theoretical issues" should not be backported (which one could argue Rust soundness issues are if no existing users hit UB), we discussed the topic of Rust soundness issues with the stable team and decided that we would do our best to backport them. The goal is to help to prevent actual issues for downstream users, distributions and vendors that patch the kernel further or even add completely new code on top, since those modifications could hit UB. In other words, the idea is to maintain the "extra layer" of protection in stable kernels too, as much as reasonably possible. Thus make it clearer by briefly mentioning it as well in the stable kernel rules. Link: https://rust-for-linux.com/contributing#soundness-issues-and-backporting [1] Signed-off-by: Miguel Ojeda <[email protected]> --- Documentation/process/stable-kernel-rules.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/process/stable-kernel-rules.rst b/Documentation/process/stable-kernel-rules.rst index edf90bbe30f4..ffa7905543a6 100644 --- a/Documentation/process/stable-kernel-rules.rst +++ b/Documentation/process/stable-kernel-rules.rst @@ -17,7 +17,7 @@ Rules on what kind of patches are accepted, and which ones are not, into the - It fixes a problem like an oops, a hang, data corruption, a real security issue, a hardware quirk, a build error (but not for things marked - CONFIG_BROKEN), or some "oh, that's not good" issue. + CONFIG_BROKEN), a Rust soundness issue, or some "oh, that's not good" issue. - Serious issues as reported by a user of a distribution kernel may also be considered if they fix a notable performance or interactivity issue. As these fixes are not as obvious and have a higher risk of a subtle base-commit: 24a19b953e2a3d0ea5a8c4951a0ab8f32720c907 -- 2.56.0
