mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
To: Chuck Ebbert <cebbert@redhat.com>
Cc: Will Trives <will@trivescon.com.au>,
	linux-kernel@vger.kernel.org,
	Nick Piggin <nickpiggin@yahoo.com.au>
Subject: Re: 2.6.21-rc2-git3 Unstable for me
Date: Mon, 05 Mar 2007 09:36:25 -0600	[thread overview]
Message-ID: <1173108985.9109.11.camel@kleikamp.austin.ibm.com> (raw)
In-Reply-To: <45EC3058.2010903@redhat.com>

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().

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.

Thanks,
Shaggy
-- 
David Kleikamp
IBM Linux Technology Center


  reply	other threads:[~2007-03-05 15:37 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 [this message]
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       ` 2.6.21-rc2-git3 Unstable for me Will Trives

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=1173108985.9109.11.camel@kleikamp.austin.ibm.com \
    --to=shaggy@linux.vnet.ibm.com \
    --cc=cebbert@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=will@trivescon.com.au \
    /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®