public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Roland Dreier <roland@topspin.com>
To: Timur Tabi <timur.tabi@ammasso.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: get_user_pages() and shared memory question
Date: Tue, 21 Jun 2005 10:33:59 -0700	[thread overview]
Message-ID: <523brbwr5k.fsf@topspin.com> (raw)
In-Reply-To: <42B82DF2.2050708@ammasso.com> (Timur Tabi's message of "Tue, 21 Jun 2005 10:10:42 -0500")

    Timur> Hi, Is it possible for a page of memory that's been
    Timur> "grabbed" with get_user_pages() to ever be allocated to
    Timur> another process?  I'm assuming the answer is no, but I have
    Timur> a specific case I want to ask about.

Not to the best of my knowledge, although you should probably read the
code to convince yourself.

    Timur> Until 2.6.7, there was a bug in the VM where a page that
    Timur> was grabbed with get_user_pages() could be swapped out.
    Timur> Those of you familar with the OpenIB work know what I'm
    Timur> talking about.  Would that bug affect anything I'm talking
    Timur> about?

This isn't what the bug caused.  What could happen was that the
swapper could unmap a page from a process's virtual memory map before
it noticed that the page had an elevated reference count.  The page
wouldn't get swapped out, but when the process caused a page fault to
bring the virtual address back, it would get a different piece of
physical memory.

 - R.

  reply	other threads:[~2005-06-21 17:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-21 15:10 get_user_pages() and shared memory question Timur Tabi
2005-06-21 17:33 ` Roland Dreier [this message]
2005-06-21 18:02 ` Hugh Dickins
2005-06-21 18:21   ` Timur Tabi
2005-06-21 19:38     ` Hugh Dickins
2005-06-21 19:43 ` Brice Goglin
2005-06-21 19:55   ` Timur Tabi

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=523brbwr5k.fsf@topspin.com \
    --to=roland@topspin.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=timur.tabi@ammasso.com \
    /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