linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Nick Piggin <npiggin@suse.de>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Christoph Lameter <clameter@sgi.com>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	GOTO <y-goto@jp.fujitsu.com>
Subject: Re: Warning on memory offline (and possible in usual migration?)
Date: Wed, 30 Apr 2008 08:56:11 +0200	[thread overview]
Message-ID: <20080430065611.GH27652@wotan.suse.de> (raw)
In-Reply-To: <20080429162016.961aa59d.kamezawa.hiroyu@jp.fujitsu.com>

On Tue, Apr 29, 2008 at 04:20:16PM +0900, KAMEZAWA Hiroyuki wrote:
> I myself want to this patch to be included (to next -mm) and put this under
> test. How do you think ? Nick ? Christoph ?

I think it should go upstream, yes. I imagine Andrew is probably just busy
with merging at the moment. I guess we should resubmit if it isn't picked
up in the next few days.

Thanks,
Nick

> 
> Thanks,
> -Kame
> 
> 
> On Wed, 23 Apr 2008 02:48:04 +0200
> Nick Piggin <npiggin@suse.de> wrote:
> > What was happening is that migrate_page_copy wants to transfer the PG_dirty
> > bit from old page to new page, so what it would do is set_page_dirty(newpage).
> > However set_page_dirty() is used to set the entire page dirty, wheras in
> > this case, only part of the page was dirty, and it also was not uptodate.
> > 
> > Marking the whole page dirty with set_page_dirty would lead to corruption or
> > unresolvable conditions -- a dirty && !uptodate page and dirty && !uptodate
> > buffers.
> > 
> > Possibly we could just ClearPageDirty(oldpage); SetPageDirty(newpage);
> > however in the interests of keeping the change minimal...
> > 
> > Signed-off-by: Nick Piggin <npiggin@suse.de>
> > ---
> > Index: linux-2.6/mm/migrate.c
> > ===================================================================
> > --- linux-2.6.orig/mm/migrate.c
> > +++ linux-2.6/mm/migrate.c
> > @@ -383,7 +383,14 @@ static void migrate_page_copy(struct pag
> >  
> >  	if (PageDirty(page)) {
> >  		clear_page_dirty_for_io(page);
> > -		set_page_dirty(newpage);
> > +		/*
> > +		 * Want to mark the page and the radix tree as dirty, and
> > +		 * redo the accounting that clear_page_dirty_for_io undid,
> > +		 * but we can't use set_page_dirty because that function
> > +		 * is actually a signal that all of the page has become dirty.
> > +		 * Wheras only part of our page may be dirty.
> > +		 */
> > +		__set_page_dirty_nobuffers(newpage);
> >   	}
> >  
> >  #ifdef CONFIG_SWAP

--
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:[~2008-04-30  6:56 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-14  5:58 KAMEZAWA Hiroyuki
2008-04-14 17:46 ` Christoph Lameter
2008-04-15 10:13   ` KAMEZAWA Hiroyuki
2008-04-15 19:31     ` Christoph Lameter
2008-04-16  0:23       ` KAMEZAWA Hiroyuki
2008-04-16  2:23         ` KAMEZAWA Hiroyuki
2008-04-16  3:10           ` KAMEZAWA Hiroyuki
2008-04-16  5:22             ` KAMEZAWA Hiroyuki
2008-04-16 18:04             ` Christoph Lameter
2008-04-16 11:00   ` KAMEZAWA Hiroyuki
2008-04-16 18:36     ` Andrew Morton
2008-04-17  0:19       ` KAMEZAWA Hiroyuki
2008-04-17  6:38         ` Warning on memory offline (possible in migration ?) KAMEZAWA Hiroyuki
2008-04-17  6:43           ` Andrew Morton
2008-04-17  6:55             ` KAMEZAWA Hiroyuki
2008-04-22  4:41       ` Warning on memory offline (and possible in usual migration?) Nick Piggin
2008-04-22  4:52   ` Nick Piggin
2008-04-22  7:56     ` KAMEZAWA Hiroyuki
2008-04-22  9:43       ` Nick Piggin
2008-04-22  9:57         ` KAMEZAWA Hiroyuki
2008-04-22 19:16         ` Christoph Lameter
2008-04-23  0:48           ` Nick Piggin
2008-04-23  1:37             ` KAMEZAWA Hiroyuki
2008-04-23  2:41             ` KAMEZAWA Hiroyuki
2008-04-23  2:53               ` Nick Piggin
2008-04-23  3:44                 ` KAMEZAWA Hiroyuki
2008-04-23 15:28                   ` Nick Piggin
2008-04-24  1:34                     ` KAMEZAWA Hiroyuki
2008-04-23 17:50                   ` Christoph Lameter
2008-04-24  1:36                     ` KAMEZAWA Hiroyuki
2008-04-24 19:11                       ` Christoph Lameter
2008-04-25  0:11                         ` KAMEZAWA Hiroyuki
2008-04-23 17:47                 ` Christoph Lameter
2008-04-24  2:13                   ` Nick Piggin
2008-04-29  7:20             ` KAMEZAWA Hiroyuki
2008-04-30  6:56               ` Nick Piggin [this message]
2008-04-30  7:04                 ` KAMEZAWA Hiroyuki
2008-04-30  7:12                 ` Andrew Morton
2008-04-30  7:22                   ` KAMEZAWA Hiroyuki
2008-04-30  7:26                   ` Nick Piggin
2008-04-30 17:59                     ` Christoph Lameter
2008-04-30 18:01                     ` Christoph Lameter
2008-05-01  1:44                       ` Nick Piggin
2008-05-01 19:25                         ` Christoph Lameter
2008-05-02  0:44                           ` Nick Piggin
2008-05-02  1:07                             ` Christoph Lameter
2008-05-02  1:23                               ` Nick Piggin
2008-05-02  1:37                                 ` Christoph Lameter
2008-05-02 21:16                                   ` Christoph Lameter
2008-05-05  4:27                                     ` Nick Piggin
2008-05-05 17:28                                       ` Christoph Lameter
2008-05-06  8:52                                         ` Nick Piggin
2008-05-06 17:49                                           ` Christoph Lameter
2008-04-30 23:29                     ` kamezawa.hiroyu
2008-05-01  0:34                       ` Badari Pulavarty
2008-05-01  8:36                       ` kamezawa.hiroyu
2008-04-22  4:50 ` 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=20080430065611.GH27652@wotan.suse.de \
    --to=npiggin@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=clameter@sgi.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-mm@kvack.org \
    --cc=y-goto@jp.fujitsu.com \
    /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