Re: [PATCH v15 00/25] fs-verity support for XFS with post EOF merkle tree
Andrey Albershteyn <[email protected]>
| Newsgroups | org.kernel.vger.linux-block,dev.linux.lists.fsverity,net.sourceforge.lists.linux-f2fs-devel,org.kernel.vger.linux-btrfs,org.kernel.vger.linux-ext4,org.kernel.vger.linux-fsdevel,org.kernel.vger.linux-unionfs,org.kernel.vger.linux-xfs |
|---|---|
| Message-ID | <[email protected]> |
On 2026-08-17 09:02:40, Christoph Hellwig wrote: > On Fri, Aug 14, 2026 at 11:24:17AM +0200, Andrey Albershteyn wrote: > > Hi all, > > > > This is next revision of fsverity for XFS. > > > > Range-diff with v14 also below. > > > > Patches without review: > > [PATCH v15 07/25] block: add task-context bio completion > > [PATCH v15 08/25] block: don't delay bio task completions > > [PATCH v15 16/25] xfs: handle fsverity I/O in write/read path > > [PATCH v15 18/25] xfs: make xfs_free_eofblocks() work with fsverity > > > > The patchset include some patches from lazy-bounce@hch-misc series for > > BIO completion in task context > > A different version of that landed in the block tree. oh didn't know that > So let's hash > out how we want to handle this for the 7.4-rc merge window after the > dust for the current merges settles. 7.3-rc? > I can have the lazy bounce series > ready early for the merge window, and should be able to send it out > once all depdendency trees hit mainline. Does that sound good? > Or should we split the minimum requirements into a separate > branch? Then the only patches I will need is IOMAP_IOEND_INTEGRITY with the helper. This is probably a bit too small change for separate series, but this will also work. I'm fine with waiting for lazy bounce, as I still will have at least one more revision. -- - Andrey