linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: John Hubbard <jhubbard@nvidia.com>
To: Minchan Kim <minchan@kernel.org>
Cc: linux-mm <linux-mm@kvack.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: pin_user_pages supports NULL pages arguments?
Date: Thu, 10 Feb 2022 11:20:31 -0800	[thread overview]
Message-ID: <7b19b521-01cf-fafb-e616-21deced2cd5b@nvidia.com> (raw)
In-Reply-To: <YgVkxwYtLov6Z5WZ@google.com>

On 2/10/22 11:17, Minchan Kim wrote:
>   * pin_user_pages() - pin user pages in memory for use by other devices
>   < snip >
>   * @pages:      array that receives pointers to the pages pinned.
>   *              Should be at least nr_pages long. Or NULL, if caller
>   *              only intends to ensure the pages are faulted in.
> 
> pin_user_pages(,, pages = NULL, );
>    gup_flags |= FOLL_PIN
>    __get_user_pages_locked
>      __get_user_pages
>        ..
>        VM_BUG_ON(!!pages != !!(gup_flags & (FOLL_GET | FOLL_PIN)));

Only FOLL_GET or FOLL_PIN are supposed to fill in the **pages array. So
if a caller passes a null **pages arg, then that caller must not also
set FOLL_GET or FOLL_PIN. That's what the VM_BUG_ON() is expressing.

Perhaps that should be part of the documentation. It sort of is already,
for get_user_pages*().

thanks,
-- 
John Hubbard
NVIDIA


  reply	other threads:[~2022-02-10 19:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10 19:17 Minchan Kim
2022-02-10 19:20 ` John Hubbard [this message]
2022-02-10 19:29   ` Minchan Kim
2022-02-10 20:20     ` John Hubbard
2022-02-10 21:17       ` Minchan Kim

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=7b19b521-01cf-fafb-e616-21deced2cd5b@nvidia.com \
    --to=jhubbard@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=minchan@kernel.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