On Fri, Nov 2, 2012 at 10:55 AM, Dale <[email protected]> wrote: > Kerin Millar wrote: >> Helmut Jarausch wrote: >>> On 10/24/2012 03:54:39 PM, Nikos Chantziaras wrote: >>>> Kernels 3.4, 3.5, and 3.6 can result in severe data corruption if >>>> you're using the EXT4 filesystem: >>> >>> It looks as if Eric Sandeen has found the culprit and Theodore Ts'o has >>> suggested this patch yesterday >>> https://lkml.org/lkml/2012/10/28/309 >>> >>> Helmut. >>> >> >> Here's the final patch: >> >> https://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=ffb5387 >> >> >> It turns out to have had nothing to do with nobarrier. >> >> --Kerin >> >> > > > Could you explain a little on who it could have affected? Is it more > serious or less serious than originally thought? This is for those of > us who don't subscribe to the kernel mailing list, which I have read is > hugely active. > > Thanks much.
Well, it fixes a bug introduced in early February. If your kernel is older than that, you're probably not affected. More specific than that...it's a race condition that's unlikely to affect machines that aren't creating many new files while shutting down where the ext4 filesystem isn't being unmounted cleanly. It's probably worth getting patched, but I'd wait until the relevant kernel version's ebuild hits stable, same as usual.
