From: Andrew Morton <akpm@linux-foundation.org>
To: Nick Piggin <npiggin@suse.de>,
miklos@szeredi.hu,
Linux Memory Management List <linux-mm@kvack.org>,
linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [patch 8/6] mm: fix cpdfio vs fault race
Date: Wed, 7 Mar 2007 03:34:00 -0800 [thread overview]
Message-ID: <20070307033400.83922b12.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070307032038.f08333a8.akpm@linux-foundation.org>
On Wed, 7 Mar 2007 03:20:38 -0800 Andrew Morton <akpm@linux-foundation.org> wrote:
>
> > ===================================================================
> > --- linux-2.6.orig/mm/memory.c
> > +++ linux-2.6/mm/memory.c
> > @@ -1676,6 +1676,17 @@ gotten:
> > unlock:
> > pte_unmap_unlock(page_table, ptl);
> > if (dirty_page) {
> > + /*
> > + * Yes, Virginia, this is actually required to prevent a race
> > + * with clear_page_dirty_for_io() from clearing the page dirty
> > + * bit after it clear all dirty ptes, but before a racing
> > + * do_wp_page installs a dirty pte.
> > + *
> > + * do_fault is protected similarly by holding the page lock
> > + * after the dirty pte is installed.
> > + */
> > + lock_page(dirty_page);
> > + unlock_page(dirty_page);
> > set_page_dirty_balance(dirty_page);
> > put_page(dirty_page);
>
> Yes, I think that'll plug it. A wait_on_page_locked() should suffice.
Or will it? Suppose after the unlock_page() a _second_
clear_page_dirty_for_io() gets run - the same thing happens?
Extending the lock_page() coverage around the set_page_dirty() would
prevent that.
I guess not needed - the second clear_page_dirty_for_io() will have cleaned the
pte.
--
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:[~2007-03-07 11:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-07 11:04 Nick Piggin
2007-03-07 11:20 ` Andrew Morton
2007-03-07 11:31 ` Nick Piggin
2007-03-07 21:02 ` Andrew Morton
2007-03-07 21:33 ` Linus Torvalds
2007-03-08 5:50 ` Nick Piggin
2007-03-07 11:34 ` Andrew Morton [this message]
2007-03-07 11:37 ` 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=20070307033400.83922b12.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=miklos@szeredi.hu \
--cc=npiggin@suse.de \
--cc=torvalds@linux-foundation.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