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

[Sasha Levin <sashal@kernel.org>]

On Sat, Nov 07, 2026 at 11:04:47AM -0800, Eric Biggers wrote:
>On Sat, Nov 07, 2026 at 05:15:44AM -0500, Sasha Levin wrote:
>> The patch below does not apply to the 6.18-stable tree.
>> If someone wants it applied there, or to any other stable or longterm
>> tree, then please email the backport, including the original git commit
>> id to <stable@vger.kernel.org>.
>>
>> To reproduce the conflict and resubmit, you may use the following commands:
>>
>> git fetch https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/ linux-6.18.y
>> git checkout FETCH_HEAD
>> git cherry-pick -x 1acb4fd2d011c4bd6cc961095ae17361c71ff61a
>> # <resolve conflicts, build, test, etc.>
>> git commit -s
>> git send-email --to '<stable@vger.kernel.org>' --in-reply-to '20261107051544-failed-6.18-1acb4fd2d011@kernel.org' --subject-prefix 'PATCH 6.18.y' 'HEAD^..'
>>
>> Thanks,
>> Sasha
>>
>
>Actually a clean cherry-pick, and failed to Cc the fsverity mailing

Ah interesting, looks like my scripts were a bit confused about the two Fixes:
tags. I'll look into that.

>list.

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

-- 
Thanks,
Sasha