Re: [PATCH v15 00/25] fs-verity support for XFS with post EOF merkle tree
Christoph Hellwig <[email protected]>
| Newsgroups | org.kernel.vger.linux-btrfs,dev.linux.lists.fsverity,net.sourceforge.lists.linux-f2fs-devel,org.kernel.vger.linux-block,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 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. 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. 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?