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
-- Attached file included as plaintext by Ecartis --
-- File: signature.asc
-- Desc: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Comment: Johannes Berg (powerbook)
iQIVAwUAR8KnwqVg1VMiehFYAQJcvw//ePAx/m2dCWUYptVRrufyOCNwIRcpzb8q
9KNNuooErqBihVp3XfXx7TWoPOEadj0dTuvaYTIsj8TLK6CijcgV+YT7mM7elvQB
HbsLctwUBLz/Sg//Q6L5WWAUaA4RaYtKvyKox9aUe9noHNQvLdntRQwvk3TbHTpj
Waejx4u+j+jPwNIna/QxWoBBhMvRp4zoHK2U+hY0zlDT0Tli+O0KNM+xjfeS1Bav
IF9uCymJudbHwdWucvcd4DWR8I1PLSHsEqp97XtYY8wrz9h735vsuFooHY1IWZL4
uK4XnoOuMHVqUaF/9S1DA3aGfnqKwEVT9A0FnjteDsEkyZPoF18LQl5pslmZBoBR
cq/cLD1J+OUWEtCUKEjk2CE9f7cVYDq5bhjUBUo+075Pa5xpnZAoaJt4ikLdpXZX
VLAYrtaNrHKQ7UuHjJlQMTy0xrBey8lt1eplzK/Pkx0qziiJyTp+T5K9eEtSMC5R
RjdyqQVwVW/VQEuzEQMCftqg+NC9TuO5i4T+iZmjIBe1sWsWnIoZiIUHP5Pzh2Bj
g0IXqhNvKIYWzB+LUZjtTrYtXjTDwAQV6qdvKc+sWwalN4vd2b0sjWc4v+EBEg78
5F8Z5NZteuP1n5ApOxCGASTU1eELwRbvOnvt2lSbgWTs9RErn7vAGlDozqhFbZ99
JrIzSUvu1OE=
=OX4E
-----END PGP SIGNATURE-----
|