linux-kernel - Re: [xfs-masters] Re: filesystem corruption on xfs after 2.6.25-rc1 (bisected, powerpc related?)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 26 Feb 2008 08:34:07 +0100
From:	Gaudenz Steinlin <gaudenz@...iologie.ch>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	Christoph Hellwig <hch@....de>, xfs-masters@....sgi.com,
	Eric Sandeen <sandeen@...deen.net>, xfs@....sgi.com,
	johannes@...solutions.net,
	linux-kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [xfs-masters] Re: filesystem corruption on xfs after
	2.6.25-rc1 (bisected, powerpc related?)

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 ~
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/