From: "Colin Walters" <walters@verbum.org>
To: "Eric Biggers" <ebiggers@kernel.org>
Cc: "Amir Goldstein" <amir73il@gmail.com>,
"Christoph Hellwig" <hch@infradead.org>,
"Miklos Szeredi" <miklos@szeredi.hu>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
fsverity@lists.linux.dev
Subject: Re: overlayfs: verity validation broken since f77f281b6118
Date: Tue, 05 May 2026 14:44:36 -0400 [thread overview]
Message-ID: <fcb47ece-926f-45d3-b2f8-734714c462ca@app.fastmail.com> (raw)
In-Reply-To: <20260505171827.GB2291@sol>
On Tue, May 5, 2026, at 1:18 PM, Eric Biggers wrote:
> Please do a fix patch first, and then any cleanup second as separate
> patch(es).
>
> You'll also need to submit your patches correctly, otherwise they cannot
> be accepted into the kernel:
> https://docs.kernel.org/process/submitting-patches.html
Yeah, I kind of intentionally was not formally submitting the patches, just drafting the shape of fixes because again they were more "generated" and I was hoping a maintainer here could pick up things since this is a straight up regression, not a feature I'm arguing for.
But anyways to get things moving I posted the first patch narrowed to a 1-liner after I noticed we didn't actually need the copy_up change because we could rely on the side effects from `ovl_ensure_verity_loaded`.
Posted to https://lore.kernel.org/linux-fsdevel/6630d44f-967d-41f0-81ce-6958b371465a@app.fastmail.com/T/#u
prev parent reply other threads:[~2026-05-05 18:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-01 17:14 overlayfs: verity validation broken since f77f281b6118 Colin Walters
2026-05-01 18:07 ` Eric Biggers
2026-05-05 18:07 ` Andrey Albershteyn
2026-05-05 20:19 ` Colin Walters
2026-05-02 9:23 ` Amir Goldstein
2026-05-05 16:51 ` Colin Walters
2026-05-05 17:18 ` Eric Biggers
2026-05-05 18:44 ` Colin Walters [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=fcb47ece-926f-45d3-b2f8-734714c462ca@app.fastmail.com \
--to=walters@verbum.org \
--cc=amir73il@gmail.com \
--cc=ebiggers@kernel.org \
--cc=fsverity@lists.linux.dev \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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