Re: FAILED: patch "[PATCH] fsverity: Explicitly require FMODE_READ to retrieve hashes" failed to apply to 6.18-stable tree

[Eric Biggers <ebiggers@kernel.org>]

On Sun, Nov 08, 2026 at 08:47:35AM -0500, Greg KH wrote:
> On Sat, Nov 07, 2026 at 01:26:33PM -0800, Eric Biggers wrote:
> > On Sat, Nov 07, 2026 at 04:14:47PM -0500, Sasha Levin wrote:
> > > So I feel we have had the Cc discussion quite a few times now. We really have
> > > to limit how many mails end up going out: this last release had thousands of
> > > mails which took hours to send. Adding more lists will simply kill the mail
> > > server and will harm everyone.
> > > 
> > > We have solutions for that!
> > > 
> > > See Konstantin's writeup[1] about lei with filters like dfn: or dfhh:.
> > > 
> > > We're not going to change this on our end: the kernel.org folks will complain,
> > > mails will take days, and people will be grumpy at us.
> > > 
> > > If this is really not something you can work around, then we can figure out a
> > > filter to exclude your patches so that all of us can continue being happy going
> > > forward.
> > > 
> > > 
> > > [1] https://people.kernel.org/monsieuricon/lore-lei-part-1-getting-started
> > 
> > I've already started to use lei to work around this issue with the
> > stable process, but everyone else will as well, which seems unlikely to
> > work well.  This also effectively means that subsystem mailing lists are
> > deprecated, as some of the development process is happening off-list.
> 
> No, all of the people involved in the patch that failed is copied.  It's
> very odd that people who are not on the s-o-b chain would want to get
> notice that a patch did not apply.

No, it's not odd at all.  Same reason we have subsystem mailing lists at
all: Linux kernel development is a collaborative process and lots of
people are involved, not just the people in MAINTAINERS (who also change
over time, may be unresponsive, go on vacation, etc.).  Just because
someone doesn't have a tag on a commit doesn't mean they weren't
involved or don't need to know about it.  We need to catch regressions
and missed backports, and failing to Cc the subsystem list is a very bad
start as then some of the people best able to help are left in the dark
unless they happen to take the time to use the lei workaround.

- Eric