From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: linux-fscrypt@vger.kernel.org, Eric Biggers <ebiggers@kernel.org>
Cc: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] fs-verity: use memcpy_from_page()
Date: Fri, 19 Aug 2022 13:16:15 +0200 [thread overview]
Message-ID: <8113955.T7Z3S40VBb@localhost.localdomain> (raw)
In-Reply-To: <20220818223903.43710-1-ebiggers@kernel.org>
On Friday, August 19, 2022 12:39:03 AM CEST Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> Replace extract_hash() with the memcpy_from_page() helper function.
>
> This is simpler, and it has the side effect of replacing the use of
> kmap_atomic() with its recommended replacement kmap_local_page().
>
> Signed-off-by: Eric Biggers <ebiggers@google.com>
> ---
> fs/verity/verify.c | 14 ++------------
> 1 file changed, 2 insertions(+), 12 deletions(-)
>
It looks good to me...
Reviewed-by: Fabio M. De Francesco <fmdefrancesco@gmail.com>
Thanks,
Fabio
> diff --git a/fs/verity/verify.c b/fs/verity/verify.c
> index 14e2fb49cff561..bde8c9b7d25f64 100644
> --- a/fs/verity/verify.c
> +++ b/fs/verity/verify.c
> @@ -39,16 +39,6 @@ static void hash_at_level(const struct merkle_tree_params
*params,
> (params->log_blocksize - params->log_arity);
> }
>
> -/* Extract a hash from a hash page */
> -static void extract_hash(struct page *hpage, unsigned int hoffset,
> - unsigned int hsize, u8 *out)
> -{
> - void *virt = kmap_atomic(hpage);
> -
> - memcpy(out, virt + hoffset, hsize);
> - kunmap_atomic(virt);
> -}
> -
> static inline int cmp_hashes(const struct fsverity_info *vi,
> const u8 *want_hash, const u8
*real_hash,
> pgoff_t index, int level)
> @@ -129,7 +119,7 @@ static bool verify_page(struct inode *inode, const
struct fsverity_info *vi,
> }
>
> if (PageChecked(hpage)) {
> - extract_hash(hpage, hoffset, hsize,
_want_hash);
> + memcpy_from_page(_want_hash, hpage, hoffset,
hsize);
> want_hash = _want_hash;
> put_page(hpage);
> pr_debug_ratelimited("Hash page already
checked, want %s:%*phN\n",
> @@ -158,7 +148,7 @@ static bool verify_page(struct inode *inode, const
struct fsverity_info *vi,
> if (err)
> goto out;
> SetPageChecked(hpage);
> - extract_hash(hpage, hoffset, hsize, _want_hash);
> + memcpy_from_page(_want_hash, hpage, hoffset, hsize);
> want_hash = _want_hash;
> put_page(hpage);
> pr_debug("Verified hash page at level %d, now want %s:
%*phN\n",
>
> base-commit: 568035b01cfb107af8d2e4bd2fb9aea22cf5b868
> --
> 2.37.1
>
>
prev parent reply other threads:[~2022-08-19 11:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 22:39 [PATCH] fs-verity: use memcpy_from_page() Eric Biggers
2022-08-19 11:16 ` Fabio M. De Francesco [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=8113955.T7Z3S40VBb@localhost.localdomain \
--to=fmdefrancesco@gmail.com \
--cc=ebiggers@kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.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 NNTP newsgroup(s).