Ext 4 data corruption bug
 

Hi All. I'm running Slackware 14 with kernel 3.4.17 and am feeling a bit nervous about the ext4 bugs in 3.4 and higher. I have a to run 3.4 for proper ivy bridge support. Has anyone here actually experienced this bug on Slackware?

Unless you have peculiar mount options there is nothing to fear. http://news.softpedia.com/news/Criti...d-303769.shtml

The problem is that there may be yet another bug:
http://www.linuxquestions.org/questi...ug-4175435187/

It's true that the circumstances are rare, but I would NOT go so far as to say "there is nothing to fear". For sure there is a rare change of it happening. So much for a filesystem being popular implying that it is also bug-free.

After just checking the source https://bugs.launchpad.net/ubuntu/+s...x/+bug/1073433: according to some info posted a short while ago, this bug is actually not in ext4 but appears to be a problem based on an interference between networking and shutdown-scripts in Ubuntu, and, so it seems, only in Ubuntu. (But over a couple of hours it might change again...so check that link later on if you worry about ext4.)

Can't you run 3.4.18 where the bug has been fixed?

You'll be fine. No need to update (unless you want any of the other fixes it brings)

Slackware won't help or hurt you with respect to this bug. If you are running an affected kernel and ext4 then you are at risk, no matter the distro.

And people wonder why slackers say that a lack of dep handling in the package management tools is a feature:)

https://bugs.launchpad.net/ubuntu/+s...r/+bug/1058987