On Wed, Oct 24, 2012 at 8:09 PM, Kerin Millar <kerfra...@fastmail.co.uk> wrote: > Canek Peláez Valdés wrote: >> >> On Wed, Oct 24, 2012 at 8:54 AM, Nikos Chantziaras<rea...@gmail.com> >> wrote: >>> >>> Kernels 3.4, 3.5, and 3.6 can result in severe data corruption if you're >>> using the EXT4 filesystem: >>> >>> http://www.phoronix.com/scan.php?page=news_item&px=MTIxNDQ >>> >>> This includes gentoo-sources. I hope the Gentoo developers are on top of >>> this. In the meantime, avoid doing reboots after too short an uptime. >> >> >> Doesn't seem to be that serious: >> >> https://plus.google.com/u/0/117091380454742934025/posts/Wcc5tMiCgq7 > > > Might I enquire as to the manner in which this comment impartially > establishes that the consequences of the bug upon those affected is not > serious?
"I suppose I should be glad the potential ext4 corruption that two users have reported potentially impacting v3.6.2 and v3.6.3 has promoted some minor increase in revenue (due to advertising hits) for Slashdot and Phoronix, but really, people should chill out." "That's not to say that we're not treating this seriously; I was up until late last night trying to get a handle on it. But folks shouldn't be running around with their heads cut off. " "It now looks like the reproduction involved something very esoteric indeed, involving using umount -l and shutdowns while the file system was still being unmounted --- and the user had nobarrier specified in the mount options as well." http://thread.gmane.org/gmane.linux.kernel/1379725/focus=34994 http://thread.gmane.org/gmane.linux.kernel/1379725/focus=35003 That, and the picture with the big "DON'T PANIC" letters on it. Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
