From: Robin Holt <holt@sgi.com>
To: Hugh Dickins <hugh@veritas.com>, Nick Piggin <npiggin@suse.de>,
Linus Torvalds <torvalds@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] get_user_pages(..., write==1, ...) may return with readable pte.
Date: Fri, 13 Oct 2006 15:33:42 -0500 [thread overview]
Message-ID: <20061013203342.GA21610@lnx-holt.americas.sgi.com> (raw)
Handle the case in get_user_pages() when a call to __handle_mm_fault()
inserts a writable pte, and a process doing dup_mmap converts it
to readable before get_user_pages() does the subsequent request to
follow_page().
Signed-off-by: Robin Holt <holt@sgi.com>
---
Hugh, Nick, and Linus,
I think I have tripped over another flavor of a get_user_pages bug
we addressed back in 2005. I do not have a test case to prove it is
the issue I am trying to address, but I have done as thorough a code
walk-through as I can.
Assume a pte is currently empty. A first pthread is in the kernel on
a call path which is leading to get_user_pages. A second pthread is
in the process of doing a fork. The process doing get_user_pages()
gets into __handle_mm_fault() and grabs ptl just before the process
doing a fork attempts to grab the ptl to convert the pages to COW.
__handle_mm_fault() will insert the writable pte and unlock ptl then
return with VM_FAULT_WRITE set. The process doing a fork then gets
the lock and starts converting the pte to RO/COW. The get_user_pages()
process then clears FOLL_WRITE from foll_flags and calls follow_page()
without write, adds to the map count for the page, but does not have a
writable mapping.
Index: linux-2.6/mm/memory.c
===================================================================
--- linux-2.6.orig/mm/memory.c 2006-10-06 12:06:25.000000000 -0500
+++ linux-2.6/mm/memory.c 2006-10-13 15:06:38.286230638 -0500
@@ -1063,15 +1063,7 @@ int get_user_pages(struct task_struct *t
int ret;
ret = __handle_mm_fault(mm, vma, start,
foll_flags & FOLL_WRITE);
- /*
- * The VM_FAULT_WRITE bit tells us that do_wp_page has
- * broken COW when necessary, even if maybe_mkwrite
- * decided not to set pte_write. We can thus safely do
- * subsequent page lookups as if they were reads.
- */
- if (ret & VM_FAULT_WRITE)
- foll_flags &= ~FOLL_WRITE;
-
+
switch (ret & ~VM_FAULT_WRITE) {
case VM_FAULT_MINOR:
tsk->min_flt++;
next reply other threads:[~2006-10-13 20:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-13 20:33 Robin Holt [this message]
2006-10-14 4:53 ` Nick Piggin
2006-10-14 5:10 ` Nick Piggin
2006-10-14 10:15 ` Robin Holt
2006-10-15 8:03 ` Nick Piggin
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=20061013203342.GA21610@lnx-holt.americas.sgi.com \
--to=holt@sgi.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@suse.de \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®