public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <haveblue@us.ibm.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Timur Tabi <timur.tabi@ammasso.com>,
	linux-mm <linux-mm@kvack.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	kernelnewbies@nl.linux.org
Subject: Re: get_user_pages() still broken in 2.6
Date: Tue, 28 Sep 2004 16:21:18 -0700	[thread overview]
Message-ID: <1096413678.16198.16.camel@localhost> (raw)
In-Reply-To: <20040929000325.A6758@infradead.org>

On Tue, 2004-09-28 at 16:03, Christoph Hellwig wrote:
> get_user_pages locks the page in memory.  It doesn't do anything about ptes.

You probably want mlock(2) to keep the kernel from messing with the ptes
at all.  But, you should probably really be thinking about why you're
accessing the page tables at all.  I count *ONE* instance in drivers/
where page tables are accessed directly.

-- Dave


  reply	other threads:[~2004-09-28 23:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-28 22:40 get_user_pages() still broken in 2.6 Timur Tabi
2004-09-28 23:03 ` Christoph Hellwig
2004-09-28 23:21   ` Dave Hansen [this message]
2004-09-29 14:46     ` Timur Tabi
2004-09-29 14:48   ` Timur Tabi
2004-09-29 15:01     ` Christoph Hellwig
2004-09-29  4:49 ` opening a file inside the kernel module Rakesh Jagota
2004-09-29  5:00   ` Jeff Garzik
2004-09-29  5:56     ` Rakesh Jagota
2004-09-29 15:52       ` Stuart MacDonald
     [not found] <2JyXo-77W-19@gated-at.bofh.it>
     [not found] ` <2JzgH-7rT-11@gated-at.bofh.it>
     [not found]   ` <2JOpu-1y1-21@gated-at.bofh.it>
2004-09-29 15:41     ` get_user_pages() still broken in 2.6 Andi Kleen

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=1096413678.16198.16.camel@localhost \
    --to=haveblue@us.ibm.com \
    --cc=hch@infradead.org \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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