From: Christoph Hellwig <hch@lst.de>
To: Andrey Albershteyn <aalbersh@kernel.org>
Cc: linux-xfs@vger.kernel.org, fsverity@lists.linux.dev,
linux-fsdevel@vger.kernel.org, ebiggers@kernel.org, hch@lst.de,
linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-btrfs@vger.kernel.org, linux-unionfs@vger.kernel.org,
djwong@kernel.org, david@fromorbit.com
Subject: Re: [PATCH v9 00/22] fs-verity support for XFS with post EOF merkle tree
Date: Thu, 7 May 2026 07:52:17 +0200 [thread overview]
Message-ID: <20260507055217.GA19888@lst.de> (raw)
In-Reply-To: <20260428083332.768693-1-aalbersh@kernel.org>
On Tue, Apr 28, 2026 at 10:33:06AM +0200, Andrey Albershteyn wrote:
> This series based on v7.0 with Christoph's read ioends patchset [1].
That's not a good baseline. We'll need it on the -rc that has everything
from the current merge window at least. It might also interact with
the fsverity fix that just went in.
This might also be time to come up with a merge plan to figure out through
what tree(s) to merge it as there don't seem to be any maintainer
objections.
next prev parent reply other threads:[~2026-05-07 5:52 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 8:33 [PATCH v9 00/22] fs-verity support for XFS with post EOF merkle tree Andrey Albershteyn
2026-04-28 8:33 ` [PATCH v9 01/22] fsverity: report validation errors through fserror to fsnotify Andrey Albershteyn
2026-04-28 8:33 ` [PATCH v9 02/22] fsverity: expose ensure_fsverity_info() Andrey Albershteyn
2026-04-28 8:33 ` [PATCH v9 03/22] ovl: use core fsverity ensure info interface Andrey Albershteyn
2026-04-28 8:33 ` [PATCH v9 04/22] fsverity: generate and store zero-block hash Andrey Albershteyn
2026-04-28 8:33 ` [PATCH v9 05/22] fsverity: pass digest size and hash of the all-zeroes block to ->write Andrey Albershteyn
2026-04-28 8:33 ` [PATCH v9 06/22] fsverity: hoist pagecache_read from f2fs/ext4 to fsverity Andrey Albershteyn
2026-04-28 8:33 ` [PATCH v9 07/22] iomap: introduce IOMAP_F_FSVERITY and teach writeback to handle fsverity Andrey Albershteyn
2026-04-28 8:33 ` [PATCH v9 08/22] iomap: teach iomap to read files with fsverity Andrey Albershteyn
2026-04-28 8:33 ` [PATCH v9 09/22] iomap: introduce iomap_fsverity_write() for writing fsverity metadata Andrey Albershteyn
2026-04-28 8:33 ` [PATCH v9 10/22] xfs: introduce fsverity on-disk changes Andrey Albershteyn
2026-04-28 8:33 ` [PATCH v9 11/22] xfs: initialize fs-verity on file open Andrey Albershteyn
2026-04-28 8:33 ` [PATCH v9 12/22] xfs: don't allow to enable DAX on fs-verity sealed inode Andrey Albershteyn
2026-04-28 8:33 ` [PATCH v9 13/22] xfs: disable direct read path for fs-verity files Andrey Albershteyn
2026-04-28 8:33 ` [PATCH v9 14/22] xfs: handle fsverity I/O in write/read path Andrey Albershteyn
2026-04-28 8:33 ` [PATCH v9 15/22] xfs: use read ioend for fsverity data verification Andrey Albershteyn
2026-04-28 8:33 ` [PATCH v9 16/22] xfs: add fs-verity support Andrey Albershteyn
2026-04-28 8:33 ` [PATCH v9 17/22] xfs: remove unwritten extents after preallocations in fsverity metadata Andrey Albershteyn
2026-04-28 8:33 ` [PATCH v9 18/22] xfs: add fs-verity ioctls Andrey Albershteyn
2026-04-28 8:33 ` [PATCH v9 19/22] xfs: advertise fs-verity being available on filesystem Andrey Albershteyn
2026-04-28 8:33 ` [PATCH v9 20/22] xfs: check and repair the verity inode flag state Andrey Albershteyn
2026-04-28 8:33 ` [PATCH v9 21/22] xfs: introduce health state for corrupted fsverity metadata Andrey Albershteyn
2026-04-28 8:33 ` [PATCH v9 22/22] xfs: enable ro-compat fs-verity flag Andrey Albershteyn
2026-05-07 5:52 ` Christoph Hellwig [this message]
2026-05-11 11:15 ` [PATCH v9 00/22] fs-verity support for XFS with post EOF merkle tree Andrey Albershteyn
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=20260507055217.GA19888@lst.de \
--to=hch@lst.de \
--cc=aalbersh@kernel.org \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=ebiggers@kernel.org \
--cc=fsverity@lists.linux.dev \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
/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