From: patchwork-bot+f2fs@kernel.org
To: Andrey Albershteyn <aalbersh@kernel.org>
Cc: linux-xfs@vger.kernel.org, fsverity@lists.linux.dev,
linux-fsdevel@vger.kernel.org, ebiggers@kernel.org,
djwong@kernel.org, linux-unionfs@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-ext4@vger.kernel.org, hch@lst.de,
linux-btrfs@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH v9 01/22] fsverity: report validation errors through fserror to fsnotify
Date: Wed, 24 Jun 2026 08:59:32 +0000 [thread overview]
Message-ID: <178229157279.2577930.17428386350924230713.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260428083332.768693-2-aalbersh@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Christian Brauner <brauner@kernel.org>:
On Tue, 28 Apr 2026 10:33:07 +0200 you wrote:
> Reported verification errors to fsnotify through recently added fserror
> interface.
>
> Reviewed-by: Darrick J. Wong <djwong@kernel.org>
> Reviewed-by: Christoph Hellwig <hch@lst.de>
> Acked-by: Eric Biggers <ebiggers@kernel.org>
> Signed-off-by: Andrey Albershteyn <aalbersh@kernel.org>
>
> [...]
Here is the summary with links:
- [f2fs-dev,v9,01/22] fsverity: report validation errors through fserror to fsnotify
(no matching commit)
- [f2fs-dev,v9,02/22] fsverity: expose ensure_fsverity_info()
(no matching commit)
- [f2fs-dev,v9,03/22] ovl: use core fsverity ensure info interface
(no matching commit)
- [f2fs-dev,v9,04/22] fsverity: generate and store zero-block hash
https://git.kernel.org/jaegeuk/f2fs/c/07d09774e2bf
- [f2fs-dev,v9,05/22] fsverity: pass digest size and hash of the all-zeroes block to ->write
(no matching commit)
- [f2fs-dev,v9,06/22] fsverity: hoist pagecache_read from f2fs/ext4 to fsverity
(no matching commit)
- [f2fs-dev,v9,07/22] iomap: introduce IOMAP_F_FSVERITY and teach writeback to handle fsverity
(no matching commit)
- [f2fs-dev,v9,08/22] iomap: teach iomap to read files with fsverity
(no matching commit)
- [f2fs-dev,v9,09/22] iomap: introduce iomap_fsverity_write() for writing fsverity metadata
https://git.kernel.org/jaegeuk/f2fs/c/36a36c4cac91
- [f2fs-dev,v9,10/22] xfs: introduce fsverity on-disk changes
(no matching commit)
- [f2fs-dev,v9,11/22] xfs: initialize fs-verity on file open
(no matching commit)
- [f2fs-dev,v9,12/22] xfs: don't allow to enable DAX on fs-verity sealed inode
(no matching commit)
- [f2fs-dev,v9,13/22] xfs: disable direct read path for fs-verity files
(no matching commit)
- [f2fs-dev,v9,14/22] xfs: handle fsverity I/O in write/read path
(no matching commit)
- [f2fs-dev,v9,15/22] xfs: use read ioend for fsverity data verification
(no matching commit)
- [f2fs-dev,v9,16/22] xfs: add fs-verity support
(no matching commit)
- [f2fs-dev,v9,17/22] xfs: remove unwritten extents after preallocations in fsverity metadata
(no matching commit)
- [f2fs-dev,v9,18/22] xfs: add fs-verity ioctls
(no matching commit)
- [f2fs-dev,v9,19/22] xfs: advertise fs-verity being available on filesystem
(no matching commit)
- [f2fs-dev,v9,20/22] xfs: check and repair the verity inode flag state
(no matching commit)
- [f2fs-dev,v9,21/22] xfs: introduce health state for corrupted fsverity metadata
(no matching commit)
- [f2fs-dev,v9,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
next prev parent reply other threads:[~2026-06-24 8:59 UTC|newest]
Thread overview: 26+ 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-06-24 8:59 ` patchwork-bot+f2fs [this message]
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 ` [PATCH v9 00/22] fs-verity support for XFS with post EOF merkle tree Christoph Hellwig
2026-05-11 11:15 ` 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=178229157279.2577930.17428386350924230713.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=aalbersh@kernel.org \
--cc=djwong@kernel.org \
--cc=ebiggers@kernel.org \
--cc=fsverity@lists.linux.dev \
--cc=hch@lst.de \
--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