Re: [f2fs-dev] [PATCH v10 00/22] fs-verity support for XFS with post EOF merkle tree

patchwork-bot+f2fs--- via Linux-f2fs-devel <[email protected]>
Newsgroups net.sourceforge.lists.linux-f2fs-devel,dev.linux.lists.fsverity,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 <178229157126.2577930.6775564706271606889.git-patchwork-notify@kernel.org>
Hello:

This series was applied to jaegeuk/f2fs.git (dev)
by Christian Brauner <[email protected]>:

On Wed, 20 May 2026 14:36:58 +0200 you wrote:
> Hi all,
> 
> This patch series adds fs-verity support for XFS. This version stores
> merkle tree beyond end of the file, the same way as ext4 does it. The
> difference is that verity descriptor is stored at the next aligned 64k
> block after the merkle tree last block. This is done due to sparse
> merkle tree which doesn't store hashes of zero data blocks.
> 
> [...]

Here is the summary with links:
  - [f2fs-dev,v10,01/22] fsverity: report validation errors through fserror to fsnotify
    (no matching commit)
  - [f2fs-dev,v10,02/22] fsverity: expose ensure_fsverity_info()
    (no matching commit)
  - [f2fs-dev,v10,03/22] ovl: use core fsverity ensure info interface
    (no matching commit)
  - [f2fs-dev,v10,04/22] fsverity: generate and store zero-block hash
    https://git.kernel.org/jaegeuk/f2fs/c/07d09774e2bf
  - [f2fs-dev,v10,05/22] fsverity: pass digest size and hash of the all-zeroes block to ->write
    (no matching commit)
  - [f2fs-dev,v10,06/22] fsverity: hoist pagecache_read from f2fs/ext4 to fsverity
    (no matching commit)
  - [f2fs-dev,v10,07/22] iomap: introduce IOMAP_F_FSVERITY and teach writeback to handle fsverity
    https://git.kernel.org/jaegeuk/f2fs/c/63e242afa466
  - [f2fs-dev,v10,08/22] iomap: teach iomap to read files with fsverity
    https://git.kernel.org/jaegeuk/f2fs/c/1d140731753a
  - [f2fs-dev,v10,09/22] iomap: introduce iomap_fsverity_write() for writing fsverity metadata
    https://git.kernel.org/jaegeuk/f2fs/c/36a36c4cac91
  - [f2fs-dev,v10,10/22] xfs: introduce fsverity on-disk changes
    (no matching commit)
  - [f2fs-dev,v10,11/22] xfs: initialize fs-verity on file open
    (no matching commit)
  - [f2fs-dev,v10,12/22] xfs: don't allow to enable DAX on fs-verity sealed inode
    (no matching commit)
  - [f2fs-dev,v10,13/22] xfs: disable direct read path for fs-verity files
    (no matching commit)
  - [f2fs-dev,v10,14/22] xfs: handle fsverity I/O in write/read path
    (no matching commit)
  - [f2fs-dev,v10,15/22] xfs: use read ioend for fsverity data verification
    (no matching commit)
  - [f2fs-dev,v10,16/22] xfs: add fs-verity support
    (no matching commit)
  - [f2fs-dev,v10,17/22] xfs: remove unwritten extents after preallocations in fsverity metadata
    (no matching commit)
  - [f2fs-dev,v10,18/22] xfs: add fs-verity ioctls
    (no matching commit)
  - [f2fs-dev,v10,19/22] xfs: advertise fs-verity being available on filesystem
    (no matching commit)
  - [f2fs-dev,v10,20/22] xfs: check and repair the verity inode flag state
    (no matching commit)
  - [f2fs-dev,v10,21/22] xfs: introduce health state for corrupted fsverity metadata
    (no matching commit)
  - [f2fs-dev,v10,22/22] xfs: enable ro-compat fs-verity flag
    (no matching commit)

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html




_______________________________________________
Linux-f2fs-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.