From: William Lee Irwin III <wli@holomorphy.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: [bugfix] fix do_wp_page_mk_pte_writable() in 2.6.10-rc2-mm3
Date: Mon, 22 Nov 2004 03:17:09 -0800 [thread overview]
Message-ID: <20041122111709.GD2714@holomorphy.com> (raw)
On Sun, Nov 21, 2004 at 10:39:29PM -0800, Andrew Morton wrote:
> 4level-core-patch.patch
> 4level core patch
vma->vm_ops->page_mkwrite() is supposed to be able to sleep, but this
function doesn't unmap the pte across the call and worse yet, reuses
the pte across a drop and reacquisition of ->page_table_lock.
Index: mm3-2.6.10-rc2/mm/memory.c
===================================================================
--- mm3-2.6.10-rc2.orig/mm/memory.c 2004-11-22 02:54:12.815541779 -0800
+++ mm3-2.6.10-rc2/mm/memory.c 2004-11-22 02:57:22.095766811 -0800
@@ -1268,6 +1268,7 @@
static inline int do_wp_page_mk_pte_writable(struct mm_struct *mm,
struct vm_area_struct *vma,
unsigned long address,
+ pmd_t *pmd,
pte_t *page_table,
struct page *old_page,
pte_t pte)
@@ -1279,6 +1280,7 @@
if (vma->vm_ops && vma->vm_ops->page_mkwrite) {
/* Notify the page owner without the lock held so they can
* sleep if they want to */
+ pte_unmap(page_table);
spin_unlock(&mm->page_table_lock);
if (vma->vm_ops->page_mkwrite(vma, old_page) < 0)
@@ -1291,6 +1293,7 @@
* return, as we can count on the MMU to tell us if they didn't
* also make it writable
*/
+ page_table = pte_offset_map(pmd, address);
if (!pte_same(*page_table, pte))
goto minor_fault;
}
@@ -1352,7 +1355,7 @@
unlock_page(old_page);
if (reuse)
/* We can just make the PTE writable */
- return do_wp_page_mk_pte_writable(mm, vma, address,
+ return do_wp_page_mk_pte_writable(mm, vma, address, pmd,
page_table, old_page,
pte);
}
reply other threads:[~2004-11-22 11:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20041122111709.GD2714@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.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