From: Souptick Joarder <jrdr.linux@gmail.com>
To: John Hubbard <jhubbard@nvidia.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux-MM <linux-mm@kvack.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/gup.c: Handle error at earliest for incorrect nr_pages value
Date: Sat, 2 May 2020 03:16:40 +0530 [thread overview]
Message-ID: <CAFqt6zaZcTeh+-ZQCanpu-tQL7zD7-iQ0DFvHLJ6Bdwkr9ZXrg@mail.gmail.com> (raw)
In-Reply-To: <c25cf212-8684-a107-bc9c-c7067dea7447@nvidia.com>
On Sat, May 2, 2020 at 3:03 AM John Hubbard <jhubbard@nvidia.com> wrote:
>
> On 2020-04-30 13:11, Souptick Joarder wrote:
> > As per documentation, pin_user_pages_fast() & get_user_pages_fast()
> > will return 0, if nr_pages <= 0. But this can be figure out only after
> > going inside the internal_get_user_pages_fast().
> >
> > This can be handled early. Adding a check for the same.
>
>
> Please, no. For precisely the reasons that Andrew gave: you are
> attempting to optimize for a case that doesn't matter other than
> for error handling, and which is already handled adequately. And
> as he also pointed out, it very slightly UN-optimizes the path that
> we *do* care about. So why are you still advocating for this?
>
> If you want to change the gup/pup API so that asking for zero pages
> means -EINVAL, then fine, go for it. That's a large thing, and a
> tree-wide audit, but if you feel it's worth pursuing then it's at
> least consistent.
>
> But this patch here needs to be abandoned.
Sure, will drop this patch.
>
>
> thanks,
> --
> John Hubbard
> NVIDIA
>
> >
> > Signed-off-by: Souptick Joarder <jrdr.linux@gmail.com>
> > ---
> > mm/gup.c | 4 ++++
> > 1 file changed, 4 insertions(+)
> >
> > diff --git a/mm/gup.c b/mm/gup.c
> > index 50681f0..a13aaa6 100644
> > --- a/mm/gup.c
> > +++ b/mm/gup.c
> > @@ -2817,6 +2817,8 @@ int get_user_pages_fast(unsigned long start, int nr_pages,
> > */
> > if (WARN_ON_ONCE(gup_flags & FOLL_PIN))
> > return -EINVAL;
> > + if (nr_pages <= 0)
> > + return 0;
> >
> > /*
> > * The caller may or may not have explicitly set FOLL_GET; either way is
> > @@ -2854,6 +2856,8 @@ int pin_user_pages_fast(unsigned long start, int nr_pages,
> > /* FOLL_GET and FOLL_PIN are mutually exclusive. */
> > if (WARN_ON_ONCE(gup_flags & FOLL_GET))
> > return -EINVAL;
> > + if (nr_pages <= 0)
> > + return 0;
> >
> > gup_flags |= FOLL_PIN;
> > return internal_get_user_pages_fast(start, nr_pages, gup_flags, pages);
> >
>
prev parent reply other threads:[~2020-05-01 21:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 20:11 Souptick Joarder
2020-04-30 21:23 ` Andrew Morton
2020-04-30 21:24 ` Ira Weiny
2020-05-01 21:16 ` Souptick Joarder
2020-05-01 21:33 ` John Hubbard
2020-05-01 21:46 ` Souptick Joarder [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=CAFqt6zaZcTeh+-ZQCanpu-tQL7zD7-iQ0DFvHLJ6Bdwkr9ZXrg@mail.gmail.com \
--to=jrdr.linux@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel@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