linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Timur Tabi <timur.tabi@ammasso.com>
To: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	kernelnewbies@nl.linux.org
Subject: get_user_pages() still broken in 2.6
Date: Tue, 28 Sep 2004 17:40:26 -0500	[thread overview]
Message-ID: <4159E85A.6080806@ammasso.com> (raw)

I was hoping that this bug would be fixed in the 2.6 kernels, but 
apparently it hasn't been.

Function get_user_pages() is supposed to lock user memory.  However, 
under extreme memory constraints, the kernel will swap out the "locked" 
memory.

I have a test app which does this:

1) Calls our driver, which issues a get_user_pages() call for one page.
2) Calls our driver again to get the physical address of that page (the 
driver uses pgd/pmd/pte_offset).
3) Tries allocate 1GB of memory (this system has 1GB of physical RAM).
4) Tries to get the physical address again.

In step 4, the physical address is usually zero, which means either 
pgd_offset or pmd_offset failed.  This indicates the page was swapped out.

I don't understand how this bug can continue to exist after all this 
time.  get_user_pages() is supposed to lock the memory, because drivers 
use it for DMA'ing directly into user memory.

-- 
Timur Tabi
Staff Software Engineer
timur.tabi@ammasso.com
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>

             reply	other threads:[~2004-09-28 22:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-28 22:40 Timur Tabi [this message]
2004-09-28 23:03 ` Christoph Hellwig
2004-09-28 23:21   ` Dave Hansen
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, linux-kernel-owner

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=4159E85A.6080806@ammasso.com \
    --to=timur.tabi@ammasso.com \
    --cc=kernelnewbies@nl.linux.org \
    --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