linux-kernel - 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]

Message-Id: <1203939267.13162.93.camel@johannes.berg>
Date:	Mon, 25 Feb 2008 12:34:27 +0100
From:	Johannes Berg <johannes@...solutions.net>
To:	Gaudenz Steinlin <gaudenz@...iologie.ch>
Cc:	xfs-masters@....sgi.com, xfs@....sgi.com,
	linux-kernel@...r.kernel.org
Subject: Re: filesystem corruption on xfs after 2.6.25-rc1 (bisected,
	powerpc related?)

Hi,

> Git reset is just the easiest way to reproduce it.

Interesting :)

> I was able to track this corruption down to commit
> a69b176df246d59626e6a9c640b44c0921fa4566 ([XFS] Use the generic bitops
> rather than implementing them ourselves.) using git bisect.
> 
> Reverting edd319dc527733e61eec5bdc9ce20c94634b6482 ([XFS] Fix
> xfs_lowbit64) to avoid merge conflicts and the faulty commit on top of
> 2.6.25-rc3 fixes the problem.

Odd. The replaced code doesn't look like it has any sort of endianness
assumptions.

> My filesystem is on an LVM2 logical volume and my computer is a
> PowerBook G4 (model 5,8). I'm using GCC 4.2.3.
> 
> My problem is similar to the problem Johannes Berg reported in:
> http://oss.sgi.com/archives/xfs/2008-02/msg00244.html
> 
> AFAIK Johannes also uses a PowerBook.

Indeed, I do, forgot to mention that, thanks for copying me.

johannes

Download attachment "signature.asc" of type "application/pgp-signature" (829 bytes)