From: Eric Biggers <ebiggers@kernel.org>
To: linux-fscrypt@vger.kernel.org
Cc: linux-ext4@vger.kernel.org, Matthew Wilcox <willy@infradead.org>
Subject: Re: [PATCH] fs/buffer.c: use b_folio for fscrypt work
Date: Tue, 7 Mar 2023 11:42:32 -0800 [thread overview]
Message-ID: <ZAeTqGnVDJxnH/3j@sol.localdomain> (raw)
In-Reply-To: <20230224232503.98372-1-ebiggers@kernel.org>
On Fri, Feb 24, 2023 at 03:25:03PM -0800, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> Use b_folio now that it exists. This removes an unnecessary call to
> compound_head(). No actual change in behavior.
>
> Signed-off-by: Eric Biggers <ebiggers@google.com>
> ---
> fs/buffer.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/buffer.c b/fs/buffer.c
> index 034bece27163..d759b105c1e7 100644
> --- a/fs/buffer.c
> +++ b/fs/buffer.c
> @@ -330,8 +330,8 @@ static void decrypt_bh(struct work_struct *work)
> struct buffer_head *bh = ctx->bh;
> int err;
>
> - err = fscrypt_decrypt_pagecache_blocks(page_folio(bh->b_page),
> - bh->b_size, bh_offset(bh));
> + err = fscrypt_decrypt_pagecache_blocks(bh->b_folio, bh->b_size,
> + bh_offset(bh));
> if (err == 0 && need_fsverity(bh)) {
> /*
> * We use different work queues for decryption and for verity
Applied to https://git.kernel.org/pub/scm/fs/fscrypt/linux.git/log/?h=for-next
- Eric
prev parent reply other threads:[~2023-03-07 19:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 23:25 [PATCH] fs/buffer.c: use b_folio for fscrypt work Eric Biggers
2023-03-07 19:42 ` Eric Biggers [this message]
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=ZAeTqGnVDJxnH/3j@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).