From: patchwork-bot+f2fs@kernel.org
To: Christoph Hellwig <hch@lst.de>
Cc: ebiggers@kernel.org, fsverity@lists.linux.dev,
brauner@kernel.org, tytso@mit.edu, djwong@kernel.org,
aalbersh@redhat.com, willy@infradead.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, viro@zeniv.linux.org.uk,
jaegeuk@kernel.org, dsterba@suse.com, jack@suse.cz,
linux-ext4@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH 01/15] fs, fsverity: reject size changes on fsverity files in setattr_prepare
Date: Tue, 17 Feb 2026 21:14:28 +0000 [thread overview]
Message-ID: <177136286807.643511.1738733092656907396.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260128152630.627409-2-hch@lst.de>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Eric Biggers <ebiggers@kernel.org>:
On Wed, 28 Jan 2026 16:26:13 +0100 you wrote:
> Add the check to reject truncates of fsverity files directly to
> setattr_prepare instead of requiring the file system to handle it.
> Besides removing boilerplate code, this also fixes the complete lack of
> such check in btrfs.
>
> Fixes: 146054090b08 ("btrfs: initial fsverity support")
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> Reviewed-by: Jan Kara <jack@suse.cz>
> Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
>
> [...]
Here is the summary with links:
- [f2fs-dev,01/15] fs, fsverity: reject size changes on fsverity files in setattr_prepare
https://git.kernel.org/jaegeuk/f2fs/c/e9734653c523
- [f2fs-dev,02/15] fs, fsverity: clear out fsverity_info from common code
https://git.kernel.org/jaegeuk/f2fs/c/70098d932714
- [f2fs-dev,03/15] ext4: don't build the fsverity work handler for !CONFIG_FS_VERITY
https://git.kernel.org/jaegeuk/f2fs/c/fb2661645909
- [f2fs-dev,04/15] f2fs: don't build the fsverity work handler for !CONFIG_FS_VERITY
https://git.kernel.org/jaegeuk/f2fs/c/6f9fae2f738c
- [f2fs-dev,05/15] fsverity: pass struct file to ->write_merkle_tree_block
(no matching commit)
- [f2fs-dev,06/15] fsverity: start consolidating pagecache code
(no matching commit)
- [f2fs-dev,07/15] fsverity: don't issue readahead for non-ENOENT errors from __filemap_get_folio
(no matching commit)
- [f2fs-dev,08/15] fsverity: kick off hash readahead at data I/O submission time
(no matching commit)
- [f2fs-dev,09/15] fsverity: deconstify the inode pointer in struct fsverity_info
https://git.kernel.org/jaegeuk/f2fs/c/7e36e044958d
- [f2fs-dev,10/15] fsverity: push out fsverity_info lookup
(no matching commit)
- [f2fs-dev,11/15] fs: consolidate fsverity_info lookup in buffer.c
https://git.kernel.org/jaegeuk/f2fs/c/f6ae956dfb34
- [f2fs-dev,12/15] ext4: consolidate fsverity_info lookup
(no matching commit)
- [f2fs-dev,13/15] f2fs: consolidate fsverity_info lookup
(no matching commit)
- [f2fs-dev,14/15] btrfs: consolidate fsverity_info lookup
https://git.kernel.org/jaegeuk/f2fs/c/b0160e4501bb
- [f2fs-dev,15/15] fsverity: use a hashtable to find the fsverity_info
(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-02-17 21:14 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-28 15:26 fsverity cleanups, speedup and memory usage optimization v4 Christoph Hellwig
2026-01-28 15:26 ` [PATCH 01/15] fs,fsverity: reject size changes on fsverity files in setattr_prepare Christoph Hellwig
2026-02-17 21:14 ` patchwork-bot+f2fs [this message]
2026-01-28 15:26 ` [PATCH 02/15] fs,fsverity: clear out fsverity_info from common code Christoph Hellwig
2026-01-28 15:26 ` [PATCH 03/15] ext4: don't build the fsverity work handler for !CONFIG_FS_VERITY Christoph Hellwig
2026-01-28 15:26 ` [PATCH 04/15] f2fs: " Christoph Hellwig
2026-01-28 15:26 ` [PATCH 05/15] fsverity: pass struct file to ->write_merkle_tree_block Christoph Hellwig
2026-01-28 15:26 ` [PATCH 06/15] fsverity: start consolidating pagecache code Christoph Hellwig
2026-01-28 15:26 ` [PATCH 07/15] fsverity: don't issue readahead for non-ENOENT errors from __filemap_get_folio Christoph Hellwig
2026-01-28 16:32 ` Darrick J. Wong
2026-01-28 23:48 ` Eric Biggers
2026-01-30 5:48 ` Christoph Hellwig
2026-01-28 15:26 ` [PATCH 08/15] fsverity: kick off hash readahead at data I/O submission time Christoph Hellwig
2026-01-28 16:33 ` Darrick J. Wong
2026-01-28 22:56 ` Eric Biggers
2026-01-28 23:22 ` Darrick J. Wong
2026-01-30 5:55 ` Christoph Hellwig
2026-01-30 5:51 ` Christoph Hellwig
2026-01-28 15:26 ` [PATCH 09/15] fsverity: deconstify the inode pointer in struct fsverity_info Christoph Hellwig
2026-01-28 15:26 ` [PATCH 10/15] fsverity: push out fsverity_info lookup Christoph Hellwig
2026-01-28 15:26 ` [PATCH 11/15] fs: consolidate fsverity_info lookup in buffer.c Christoph Hellwig
2026-01-28 15:26 ` [PATCH 12/15] ext4: consolidate fsverity_info lookup Christoph Hellwig
2026-01-28 16:28 ` Jan Kara
2026-01-28 15:26 ` [PATCH 13/15] f2fs: " Christoph Hellwig
2026-01-28 15:26 ` [PATCH 14/15] btrfs: " Christoph Hellwig
2026-01-28 15:26 ` [PATCH 15/15] fsverity: use a hashtable to find the fsverity_info Christoph Hellwig
2026-01-29 0:07 ` fsverity cleanups, speedup and memory usage optimization v4 Eric Biggers
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=177136286807.643511.1738733092656907396.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=aalbersh@redhat.com \
--cc=brauner@kernel.org \
--cc=djwong@kernel.org \
--cc=dsterba@suse.com \
--cc=ebiggers@kernel.org \
--cc=fsverity@lists.linux.dev \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=jaegeuk@kernel.org \
--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=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.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