From: Nick Piggin <npiggin@suse.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Sage Weil <sage@newdream.net>,
Trond Myklebust <trond.myklebust@fys.uio.no>,
linux-fsdevel@vger.kernel.org,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [patch] mm: close page_mkwrite races (try 3)
Date: Thu, 16 Apr 2009 04:23:57 +0200 [thread overview]
Message-ID: <20090416022357.GB22216@wotan.suse.de> (raw)
In-Reply-To: <20090415183847.d4fa1efb.akpm@linux-foundation.org>
Here's an incremental patch.
--
On Wed, Apr 15, 2009 at 06:38:47PM -0700, Andrew Morton wrote:
> Whoa. Running file_update_time() under lock_page() opens a whole can
> of worms, doesn't it? That thing can do journal commits and all sorts
> of stuff. And I don't think this ordering is necessary here?
Signed-off-by: Nick Piggin <npiggin@suse.de>
---
mm/memory.c | 14 ++++++++------
1 file changed, 8 insertions(+), 6 deletions(-)
Index: linux-2.6/mm/memory.c
===================================================================
--- linux-2.6.orig/mm/memory.c
+++ linux-2.6/mm/memory.c
@@ -2105,9 +2105,6 @@ gotten:
unlock:
pte_unmap_unlock(page_table, ptl);
if (dirty_page) {
- if (vma->vm_file)
- file_update_time(vma->vm_file);
-
/*
* Yes, Virginia, this is actually required to prevent a race
* with clear_page_dirty_for_io() from clearing the page dirty
@@ -2129,6 +2126,10 @@ unlock:
page_cache_release(dirty_page);
balance_dirty_pages_ratelimited(mapping);
}
+
+ /* file_update_time outside page_lock */
+ if (vma->vm_file)
+ file_update_time(vma->vm_file);
}
return ret;
oom_free_new:
@@ -2760,15 +2761,16 @@ out:
if (dirty_page) {
struct address_space *mapping = page->mapping;
- if (vma->vm_file)
- file_update_time(vma->vm_file);
-
if (set_page_dirty(dirty_page))
page_mkwrite = 1;
unlock_page(dirty_page);
put_page(dirty_page);
if (page_mkwrite)
balance_dirty_pages_ratelimited(mapping);
+
+ /* file_update_time outside page_lock */
+ if (vma->vm_file)
+ file_update_time(vma->vm_file);
} else {
unlock_page(vmf.page);
if (anon)
--
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:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-04-16 2:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 7:11 [patch] mm: close page_mkwrite races (try 2) Nick Piggin
2009-04-15 8:25 ` [patch] mm: close page_mkwrite races (try 3) Nick Piggin
2009-04-16 1:38 ` Andrew Morton
2009-04-16 2:03 ` Nick Piggin
2009-04-16 2:23 ` Nick Piggin [this message]
2009-04-28 18:57 ` Ravikiran G Thirumalai
2009-04-29 7:12 ` Nick Piggin
2009-04-29 7:24 ` Andrew Morton
2009-04-29 7:45 ` Nick Piggin
2009-04-29 12:39 ` Trond Myklebust
2009-04-29 15:27 ` Andrew Morton
2009-04-29 16:45 ` Trond Myklebust
2009-04-30 14:22 ` Rince
2009-04-30 14:33 ` Rince
2009-05-02 22:12 ` Rince
2009-05-03 1:38 ` Trond Myklebust
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=20090416022357.GB22216@wotan.suse.de \
--to=npiggin@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sage@newdream.net \
--cc=trond.myklebust@fys.uio.no \
/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;
as well as URLs for NNTP newsgroup(s).