From: Gaudenz Steinlin <gaudenz@soziologie.ch>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Christoph Hellwig <hch@lst.de>,
xfs-masters@oss.sgi.com, Eric Sandeen <sandeen@sandeen.net>,
xfs@oss.sgi.com, johannes@sipsolutions.net,
linux-kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [xfs-masters] Re: filesystem corruption on xfs after 2.6.25-rc1 (bisected, powerpc related?)
Date: Tue, 26 Feb 2008 08:34:07 +0100 [thread overview]
Message-ID: <20080226073407.GA5762@soziologie.ch> (raw)
In-Reply-To: <200802260113.57875.rjw@sisk.pl>
On Tue, Feb 26, 2008 at 01:13:56AM +0100, Rafael J. Wysocki wrote:
> On Tuesday, 26 of February 2008, Christoph Hellwig wrote:
> > On Tue, Feb 26, 2008 at 12:52:56AM +0100, Rafael J. Wysocki wrote:
> > > > I'm not suggesting a partial revert; I just wonder which part of the
> > > > change is causing the problem, as part of the debugging process.
> > >
> > > Understood.
> > >
> > > My point is, if that's not practical (whatever the reason), I'd consider
> > > reverting all of the commits in question.
> >
> > If you could revert all of them and verify it makes the problem go away
> > that would be a very good start already.
>
> The original reporter (CC added) said exactly that, if I understood him
> correctly:
>
> http://lkml.org/lkml/2008/2/25/123
Sorry if I was not clear. The problematic commit after bisecting is
a69b176df246d59626e6a9c640b44c0921fa4566. Reverting this commit and
commit edd319dc527733e61eec5bdc9ce20c94634b6482 fixes the problem. So
all other commits in the XFS merge for 2.6.25 seem to be OK. I had to
revert the second commit only to avoid a merge conflict.
And I forget to mention on my first post: Please CC me on all replies.
I'm not subscribed to the lists.
Gaudenz
--
Ever tried. Ever failed. No matter.
Try again. Fail again. Fail better.
~ Samuel Beckett ~
next prev parent reply other threads:[~2008-02-26 7:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-25 11:23 Gaudenz Steinlin
2008-02-25 11:34 ` Johannes Berg
2008-02-25 18:15 ` [xfs-masters] " Eric Sandeen
2008-02-25 23:42 ` Rafael J. Wysocki
2008-02-25 23:48 ` Eric Sandeen
2008-02-25 23:52 ` Rafael J. Wysocki
2008-02-25 23:57 ` [xfs-masters] " Christoph Hellwig
2008-02-26 0:13 ` Rafael J. Wysocki
2008-02-26 7:34 ` Gaudenz Steinlin [this message]
2008-02-26 11:44 ` Gaudenz Steinlin
2008-02-26 18:11 ` Johannes Berg
2008-02-28 14:40 ` Eric Sandeen
2008-02-26 20:05 ` Eric Sandeen
2008-02-26 20:59 ` Mark Goodwin
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=20080226073407.GA5762@soziologie.ch \
--to=gaudenz@soziologie.ch \
--cc=hch@lst.de \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=sandeen@sandeen.net \
--cc=xfs-masters@oss.sgi.com \
--cc=xfs@oss.sgi.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®