From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
stable-commits@vger.kernel.org, Qu Wenruo <wqu@suse.com>,
Chris Mason <clm@fb.com>, David Sterba <dsterba@suse.com>,
David Sterba <dsterba@suse.cz>
Subject: Re: Patch "btrfs: move large data folios out of experimental features" has been added to the 7.1-stable tree
Date: Mon, 17 Aug 2026 11:24:43 -0400 [thread overview]
Message-ID: <20260817150000.5@kernel.org> (raw)
In-Reply-To: <20260817103330.GA54102@suse.cz>
> Can this be handled in a more generic way, the fixes to experimental
> features? If you pass that through AI, it should be clear from the
> context (changelog or code).
Agreed, and done: the selection rules now reject both commits that
promote a feature out from behind a CONFIG_*_EXPERIMENTAL (or equivalent
staging) gate, and fixes to code that is only reachable when such a
symbol is enabled. It keys off the config gate in the diff rather than
the changelog wording, since neither commit here reads as "experimental"
in prose.
> The config option has been added also for that purpose, it does not make
> sense to backport that and assign CVE's eventually.
CVE assignment runs separately from the stable queue; I will pass the
same signal along there.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-08-17 15:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260812000703.4150441-1-sashal@kernel.org>
2026-08-12 0:43 ` Patch "btrfs: move large data folios out of experimental features" has been added to the 7.1-stable tree Qu Wenruo
2026-08-12 11:44 ` Sasha Levin
2026-08-17 10:33 ` David Sterba
2026-08-17 15:24 ` Sasha Levin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260817150000.5@kernel.org \
--to=sashal@kernel.org \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=dsterba@suse.cz \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=wqu@suse.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox