From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Eric Biggers <ebiggers@kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
David Sterba <dsterba@suse.com>, Theodore Ts'o <tytso@mit.edu>,
Jaegeuk Kim <jaegeuk@kernel.org>, Chao Yu <chao@kernel.org>,
Andrey Albershteyn <aalbersh@redhat.com>,
Matthew Wilcox <willy@infradead.org>,
linux-fsdevel@vger.kernel.org, linux-btrfs@vger.kernel.org,
linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, fsverity@lists.linux.dev
Subject: Re: [PATCH 12/16] fs: consolidate fsverity_info lookup in buffer.c
Date: Mon, 26 Jan 2026 11:17:11 -0800 [thread overview]
Message-ID: <20260126191711.GR5910@frogsfrogsfrogs> (raw)
In-Reply-To: <20260126045212.1381843-13-hch@lst.de>
On Mon, Jan 26, 2026 at 05:50:58AM +0100, Christoph Hellwig wrote:
> Look up the fsverity_info once in end_buffer_async_read_io, and then
> pass it along to the I/O completion workqueue in
> struct postprocess_bh_ctx.
>
> This amortizes the lookup better once it becomes less efficient.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Looks fine now,
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
--D
> ---
> fs/buffer.c | 27 +++++++++++----------------
> 1 file changed, 11 insertions(+), 16 deletions(-)
>
> diff --git a/fs/buffer.c b/fs/buffer.c
> index 3982253b6805..f4b3297ef1b1 100644
> --- a/fs/buffer.c
> +++ b/fs/buffer.c
> @@ -302,6 +302,7 @@ static void end_buffer_async_read(struct buffer_head *bh, int uptodate)
> struct postprocess_bh_ctx {
> struct work_struct work;
> struct buffer_head *bh;
> + struct fsverity_info *vi;
> };
>
> static void verify_bh(struct work_struct *work)
> @@ -309,25 +310,14 @@ static void verify_bh(struct work_struct *work)
> struct postprocess_bh_ctx *ctx =
> container_of(work, struct postprocess_bh_ctx, work);
> struct buffer_head *bh = ctx->bh;
> - struct inode *inode = bh->b_folio->mapping->host;
> bool valid;
>
> - valid = fsverity_verify_blocks(*fsverity_info_addr(inode), bh->b_folio,
> - bh->b_size, bh_offset(bh));
> + valid = fsverity_verify_blocks(ctx->vi, bh->b_folio, bh->b_size,
> + bh_offset(bh));
> end_buffer_async_read(bh, valid);
> kfree(ctx);
> }
>
> -static bool need_fsverity(struct buffer_head *bh)
> -{
> - struct folio *folio = bh->b_folio;
> - struct inode *inode = folio->mapping->host;
> -
> - return fsverity_active(inode) &&
> - /* needed by ext4 */
> - folio->index < DIV_ROUND_UP(inode->i_size, PAGE_SIZE);
> -}
> -
> static void decrypt_bh(struct work_struct *work)
> {
> struct postprocess_bh_ctx *ctx =
> @@ -337,7 +327,7 @@ static void decrypt_bh(struct work_struct *work)
>
> err = fscrypt_decrypt_pagecache_blocks(bh->b_folio, bh->b_size,
> bh_offset(bh));
> - if (err == 0 && need_fsverity(bh)) {
> + if (err == 0 && ctx->vi) {
> /*
> * We use different work queues for decryption and for verity
> * because verity may require reading metadata pages that need
> @@ -359,15 +349,20 @@ static void end_buffer_async_read_io(struct buffer_head *bh, int uptodate)
> {
> struct inode *inode = bh->b_folio->mapping->host;
> bool decrypt = fscrypt_inode_uses_fs_layer_crypto(inode);
> - bool verify = need_fsverity(bh);
> + struct fsverity_info *vi = NULL;
> +
> + /* needed by ext4 */
> + if (bh->b_folio->index < DIV_ROUND_UP(inode->i_size, PAGE_SIZE))
> + vi = fsverity_get_info(inode);
>
> /* Decrypt (with fscrypt) and/or verify (with fsverity) if needed. */
> - if (uptodate && (decrypt || verify)) {
> + if (uptodate && (decrypt || vi)) {
> struct postprocess_bh_ctx *ctx =
> kmalloc(sizeof(*ctx), GFP_ATOMIC);
>
> if (ctx) {
> ctx->bh = bh;
> + ctx->vi = vi;
> if (decrypt) {
> INIT_WORK(&ctx->work, decrypt_bh);
> fscrypt_enqueue_decrypt_work(&ctx->work);
> --
> 2.47.3
>
>
next prev parent reply other threads:[~2026-01-26 19:17 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 4:50 fsverity cleanups, speedup and memory usage optimization v3 Christoph Hellwig
2026-01-26 4:50 ` [PATCH 01/16] fs,fsverity: reject size changes on fsverity files in setattr_prepare Christoph Hellwig
2026-01-26 4:50 ` [PATCH 02/16] fs,fsverity: clear out fsverity_info from common code Christoph Hellwig
2026-01-26 4:50 ` [PATCH 03/16] ext4: don't build the fsverity work handler for !CONFIG_FS_VERITY Christoph Hellwig
2026-01-26 12:22 ` Jan Kara
2026-01-26 19:27 ` Darrick J. Wong
2026-01-26 4:50 ` [PATCH 04/16] f2fs: " Christoph Hellwig
2026-01-26 4:50 ` [PATCH 05/16] fsverity: pass struct file to ->write_merkle_tree_block Christoph Hellwig
2026-01-26 4:50 ` [PATCH 06/16] fsverity: start consolidating pagecache code Christoph Hellwig
2026-01-26 4:50 ` [PATCH 07/16] fsverity: don't issue readahead for non-ENOENT errors from __filemap_get_folio Christoph Hellwig
2026-01-26 19:11 ` Darrick J. Wong
2026-01-26 20:53 ` Eric Biggers
2026-01-27 6:00 ` Christoph Hellwig
2026-01-27 6:20 ` Eric Biggers
2026-01-27 6:28 ` Darrick J. Wong
2026-01-27 6:38 ` Christoph Hellwig
2026-01-28 0:57 ` Eric Biggers
2026-01-27 6:36 ` Christoph Hellwig
2026-01-26 4:50 ` [PATCH 08/16] fsverity: kick off hash readahead at data I/O submission time Christoph Hellwig
2026-01-26 19:26 ` Darrick J. Wong
2026-01-26 20:37 ` Eric Biggers
2026-01-26 4:50 ` [PATCH 09/16] fsverity: constify the vi pointer in fsverity_verification_context Christoph Hellwig
2026-01-26 19:13 ` Darrick J. Wong
2026-01-28 3:22 ` Eric Biggers
2026-01-28 3:32 ` Christoph Hellwig
2026-01-28 3:41 ` Eric Biggers
2026-01-28 3:48 ` Christoph Hellwig
2026-01-26 4:50 ` [PATCH 10/16] fsverity: deconstify the inode pointer in struct fsverity_info Christoph Hellwig
2026-01-26 19:13 ` Darrick J. Wong
2026-01-26 4:50 ` [PATCH 11/16] fsverity: push out fsverity_info lookup Christoph Hellwig
2026-01-26 4:50 ` [PATCH 12/16] fs: consolidate fsverity_info lookup in buffer.c Christoph Hellwig
2026-01-26 12:25 ` Jan Kara
2026-01-26 19:17 ` Darrick J. Wong [this message]
2026-01-26 4:50 ` [PATCH 13/16] ext4: consolidate fsverity_info lookup Christoph Hellwig
2026-01-26 12:27 ` Jan Kara
2026-01-26 4:51 ` [PATCH 14/16] f2fs: " Christoph Hellwig
2026-01-26 4:51 ` [PATCH 15/16] btrfs: " Christoph Hellwig
2026-01-26 4:51 ` [PATCH 16/16] fsverity: use a hashtable to find the fsverity_info Christoph Hellwig
2026-01-26 19:35 ` Darrick J. Wong
2026-01-26 20:40 ` Eric Biggers
2026-01-27 6:15 ` Christoph Hellwig
2026-01-28 3:28 ` Eric Biggers
2026-01-28 3:35 ` Christoph Hellwig
2026-01-28 3:44 ` Eric Biggers
2026-01-28 3:48 ` Christoph Hellwig
2026-01-28 3:59 ` 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=20260126191711.GR5910@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=aalbersh@redhat.com \
--cc=brauner@kernel.org \
--cc=chao@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