> I've been off-list and not paying much attention since Andre
> acknowledged it was a bug (and didn't like my patch).
I can imagine why ...
> Let me be very clear: this bug has corrupted filesystems on three
> machines of mine. All of these had PIIX chipsets. I have also
> reproduced it on a VIA chipset, but since that machine was production I
> didn't try very hard to corrupt the fs.
You may try that patch with a VIA boxen and I am quite sure you may experience
a bug that none of your harddisks may be recognized and result in a
> The patch is not a real fix, merely a workaround. But since 6 months
> have already elapsed, can I request that the patch be applied now, and
> when Andre creates a proper fix we can use that.
I had the same Fix in WOLK some time ago and many users with VIA chipset
complained that with the fix their mashine does not recognize any harddisks
and after trying to recognize they had a panic();
Maybe it's working for you with some VIA chipsets but I removed that fix and
after removal all users with VIA were happy. I've never heard of a FS
corruption of them.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Nov 30 2002 - 22:00:16 EST