From: Matthew Wilcox <willy@infradead.org>
To: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
Cc: linux-fscrypt@vger.kernel.org, Eric Biggers <ebiggers@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] fs-verity: use kmap_local_page() instead of kmap()
Date: Fri, 19 Aug 2022 19:29:31 +0100 [thread overview]
Message-ID: <Yv/Wi/2IH/bY05zG@casper.infradead.org> (raw)
In-Reply-To: <44912540.fMDQidcC6G@opensuse>
On Fri, Aug 19, 2022 at 09:50:37AM +0200, Fabio M. De Francesco wrote:
> On venerdì 19 agosto 2022 00:40:10 CEST Eric Biggers wrote:
> > From: Eric Biggers <ebiggers@google.com>
> >
> > Convert the use of kmap() to its recommended replacement
> > kmap_local_page(). This avoids the overhead of doing a non-local
> > mapping, which is unnecessary in this case.
> >
> > Signed-off-by: Eric Biggers <ebiggers@google.com>
> > ---
> > fs/verity/read_metadata.c | 6 +++---
> > 1 file changed, 3 insertions(+), 3 deletions(-)
>
> It looks good to me...
>
> > - virt = kmap(page);
> > + virt = kmap_local_page(page);
> > if (copy_to_user(buf, virt + offs_in_page, bytes_to_copy))
> {
> > - kunmap(page);
> > + kunmap_local(virt);
> > put_page(page);
> > err = -EFAULT;
> > break;
> > }
> > - kunmap(page);
> > + kunmap_local(virt);
Is this a common pattern? eg do we want something like:
static inline int copy_user_page(void __user *dst, struct page *page,
size_t offset, size_t len)
{
char *src = kmap_local_page(page) + offset;
int err = 0;
VM_BUG_ON(offset + len > PAGE_SIZE);
if (copy_to_user(dst, src, len))
err = -EFAULT;
kunmap_local(src);
return err;
}
in highmem.h?
next prev parent reply other threads:[~2022-08-19 18:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 22:40 Eric Biggers
2022-08-19 7:50 ` Fabio M. De Francesco
2022-08-19 18:29 ` Matthew Wilcox [this message]
2022-08-19 22:31 ` Fabio M. De Francesco
2022-08-19 11:14 ` Fabio M. De Francesco
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=Yv/Wi/2IH/bY05zG@casper.infradead.org \
--to=willy@infradead.org \
--cc=ebiggers@kernel.org \
--cc=fmdefrancesco@gmail.com \
--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