linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Miklos Szeredi <miklos@szeredi.hu>
To: akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	nickpiggin@yahoo.com.au, torvalds@linux-foundation.org
Subject: Re: [patch 1/8] fix race in clear_page_dirty_for_io()
Date: Wed, 07 Mar 2007 11:31:59 +0100	[thread overview]
Message-ID: <E1HOtR9-00007G-00@dorka.pomaz.szeredi.hu> (raw)
In-Reply-To: <20070307021518.3b1ff4a2.akpm@linux-foundation.org> (message from Andrew Morton on Wed, 7 Mar 2007 02:15:18 -0800)

> (cc's reinstated)
> 
> On Wed, 07 Mar 2007 09:09:50 +0100 Miklos Szeredi <miklos@szeredi.hu> wrote:
> 
> > There's a race in clear_page_dirty_for_io() that allows a page to have
> > cleared PG_dirty, while being mapped read-write into the page table(s).
> 
> I assume you refer to this:
> 
> 		 * FIXME! We still have a race here: if somebody
> 		 * adds the page back to the page tables in
> 		 * between the "page_mkclean()" and the "TestClearPageDirty()",
> 		 * we might have it mapped without the dirty bit set.
> 		 */
> 		if (page_mkclean(page))
> 			set_page_dirty(page);
> 		if (TestClearPageDirty(page)) {
> 			dec_zone_page_state(page, NR_FILE_DIRTY);
> 			return 1;
> 		}
> 

Yes.

> I guess the comment actually refers to a writefault after the
> set_page_dirty() and before the TestClearPageDirty().  The fault handler
> will run set_page_dirty() and will return to userspace to rerun the write. 
> The page then gets set pte-dirty but this thread of control will now make
> the page !PageDirty() and will write it out.

Yes.

> With Nick's proposed lock-the-page-in-pagefaults patches, we have
> lock_page() synchronisation between pagefaults and
> clear_page_dirty_for_io() which I think will fix this.

After a quick look, I don't think it does.  It locks the page in
do_no_page(), but not for the whole fault.  In particular do_wp_page()
is not affected.  But I haven't yet looked closely at that patch, so I
could be wrong.

Miklos

--
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>

      reply	other threads:[~2007-03-07 10:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070307080949.290171170@szeredi.hu>
     [not found] ` <20070307082337.101759335@szeredi.hu>
2007-03-07 10:15   ` Andrew Morton
2007-03-07 10:31     ` Miklos Szeredi [this message]

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=E1HOtR9-00007G-00@dorka.pomaz.szeredi.hu \
    --to=miklos@szeredi.hu \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=nickpiggin@yahoo.com.au \
    --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