mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Will Trives <will@trivescon.com.au>
To: Dave Kleikamp <shaggy@linux.vnet.ibm.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.21-rc2-git3 Unstable for me
Date: Tue, 6 Mar 2007 09:25:26 +1100	[thread overview]
Message-ID: <20070306092526.0a7cdd0b@disher.kickcrew> (raw)
In-Reply-To: <1173109811.9109.17.camel@kleikamp.austin.ibm.com>

Hello,

Looks like this has fixed the problem for me, it's not falling down
anymore. Thanks Dave.


On Mon, 05 Mar 2007 09:50:11 -0600
Dave Kleikamp <shaggy@linux.vnet.ibm.com> wrote:

> On Mon, 2007-03-05 at 09:36 -0600, Dave Kleikamp wrote:
> > On Mon, 2007-03-05 at 09:59 -0500, Chuck Ebbert wrote:
> > > Will Trives wrote:
> > > 
> > > [adding JFS maintainer to cc:]
> > 
> > Thanks for adding me to the thread.
> > 
> > > Some kind of JFS problem?
> > 
> > I don' t know yet.  I was notified of the problem through bugzilla:
> > http://bugzilla.kernel.org/show_bug.cgi?id=8128
> > 
> > The problem appears that a non-uptodate page has been marked
> > dirty.  I haven't found much in the way of changes between 2.6.20
> > and the current git tree to explain this.  There's this one:
> > http://git.kernel.org/gitweb.cgi?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=22c8ca78f20724676b6006232bf06cc3e9299539
> > 
> > I'm looking for for a caller to ->prepare_write() which marks the
> > page dirty without calling ->commit_write().
> 
> I think I just found it:
> 
> nobh_truncate_page():
> 
> 	ret = a_ops->prepare_write(NULL, page, offset, to);
> 	if (ret == 0) {
> 		kaddr = kmap_atomic(page, KM_USER0);
> 		memset(kaddr + offset, 0, PAGE_CACHE_SIZE - offset);
> 		flush_dcache_page(page);
> 		kunmap_atomic(kaddr, KM_USER0);
> 		set_page_dirty(page);
> 	}
> 	unlock_page(page);
> 	page_cache_release(page);
> 
> > 
> > Will, could you try reverting that patch?  If that fails, narrowing
> > the problem down with git-bisect would be helpful, if you have the
> > time.
> 
> Better yet, try this patch:
> 
> Signed-off-by: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
> 
> diff -Nurp linux-orig/fs/buffer.c linux/fs/buffer.c
> --- linux-orig/fs/buffer.c	2007-02-22 07:59:01.000000000 -0600
> +++ linux/fs/buffer.c	2007-03-05 09:47:07.000000000 -0600
> @@ -2466,6 +2466,7 @@ int nobh_truncate_page(struct address_sp
>  		memset(kaddr + offset, 0, PAGE_CACHE_SIZE - offset);
>  		flush_dcache_page(page);
>  		kunmap_atomic(kaddr, KM_USER0);
> +		SetPageUptodate(page);
>  		set_page_dirty(page);
>  	}
>  	unlock_page(page);
> 

      parent reply	other threads:[~2007-03-05 22:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-05  4:03 Will Trives
2007-03-05 14:59 ` Chuck Ebbert
2007-03-05 15:36   ` Dave Kleikamp
2007-03-05 15:50     ` Dave Kleikamp
2007-03-05 20:58       ` [PATCH] fs: nobh_truncate_page() fix Dave Kleikamp
2007-03-05 21:43         ` Linus Torvalds
2007-03-05 22:57           ` Andrew Morton
2007-03-05 23:10             ` Dave Kleikamp
2007-03-05 23:31               ` Andrew Morton
2007-03-05 23:02           ` Dave Kleikamp
2007-03-05 22:25       ` Will Trives [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=20070306092526.0a7cdd0b@disher.kickcrew \
    --to=will@trivescon.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shaggy@linux.vnet.ibm.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

all inboxes | Powered by JetHome®