the IDE/DMA problems coming from old WD hardware may affect read, however
I've got no reports that even hint at that ever being the case, and WD
dont say a lot except how to apply the firmware update.
> > Me not being an fs expert (far from it) I wonder what makes you so sure
> > it was in the cache? Config.h was one of the files (Makefile was the
> > other, i was editing both) that was 'hit' by the error and fsck found an
> > error in that file's inode.
If the dirty bits get corrupted as well as data then junk will get written
back - any OS, any kernel.
There are certainly a couple of memory corruption bugs left in 2.1.12x. One
of them is in the bttv driver when capturing to main memory. Its extermination
is in progress
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/