From: Eric Biggers <ebiggers@kernel.org>
To: Alexander Larsson <alexl@redhat.com>
Cc: miklos@szeredi.hu, linux-unionfs@vger.kernel.org,
amir73il@gmail.com, tytso@mit.edu, fsverity@lists.linux.dev
Subject: Re: [PATCH v4 0/3] ovl: Add support for fs-verity checking of lowerdata
Date: Tue, 20 Jun 2023 09:15:07 -0700 [thread overview]
Message-ID: <20230620161507.GA864@sol.localdomain> (raw)
In-Reply-To: <cover.1687255035.git.alexl@redhat.com>
On Tue, Jun 20, 2023 at 12:15:15PM +0200, Alexander Larsson wrote:
> This series depends on the commit
> fsverity: rework fsverity_get_digest() again
> Which is in the "for-next" branch of
> https://git.kernel.org/pub/scm/fs/fsverity/linux.git/
>
> This series, plus the above commit are also in git here:
> https://github.com/alexlarsson/linux/tree/overlay-verity
>
> I would love to see this go into 6.5. So Eric, could you maybe Ack the
> implementation patches separately from the documentation patches? Then
> maybe we can get this in early, and I promise to try to get the
> documentation up to standard during the 6.5 cycle as needed.
I think it's gotten too late for 6.5. If there is no 6.4-rc8, then the 6.5
merge window will open just 5 days from now. This series has recently gone
through some significant changes, including in the version just sent out today
which I haven't had a chance to review yet.
Please don't try to rush things in when they involve UAPI and on-disk format
changes, which will have to be supported forever. We need to take the time to
get them right.
I also see that the overlayfs tree is already very busy in 6.5, with the support
for data-only lower layers, lazy lookup of lowerdata, and the new mount API.
I think 6.6 would be a more realistic target. That would give time to write
proper documentation as well, which is super important. (Very often while
writing documentation, I realize that I should do something differently in the
code. Please don't think of documentation as something can be done "later".)
- Eric
next prev parent reply other threads:[~2023-06-20 16:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 10:15 [PATCH v4 0/3] ovl: Add support for fs-verity checking of lowerdata Alexander Larsson
2023-06-20 10:15 ` [PATCH v4 1/3] ovl: Add framework for verity support Alexander Larsson
2023-06-20 12:41 ` Amir Goldstein
2023-06-20 10:15 ` [PATCH v4 2/3] ovl: Validate verity xattr when resolving lowerdata Alexander Larsson
2023-06-20 13:50 ` Amir Goldstein
2023-06-20 10:15 ` [PATCH v4 3/3] ovl: Handle verity during copy-up Alexander Larsson
2023-06-20 12:10 ` Amir Goldstein
2023-06-20 16:15 ` Eric Biggers [this message]
2023-06-21 11:27 ` [PATCH v4 0/3] ovl: Add support for fs-verity checking of lowerdata Alexander Larsson
2023-06-21 12:57 ` Amir Goldstein
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=20230620161507.GA864@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=alexl@redhat.com \
--cc=amir73il@gmail.com \
--cc=fsverity@lists.linux.dev \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.