Slashdot Mirror

← Back to Stories (view on slashdot.org)

Data Corrupting ext3 Bug In Latest Linux 2.4.20

Posted by Hemos on from the bad-news dept.

An anonymous reader writes "Andrew Morton alerted readers of the Linux Kernel mailing list today that ext3 in the 2.4.20 kernel has a new bug that can easily cause file data corruption at unmount time. The bug will only affect people using ext3 in "data=journal" mode, which fortunately is not the default... Full details can be read on KernelTrap."

2 of 50 comments (clear)

  1. Re:Why isn't this on the front page? by walt-sjc · · Score: 4, Insightful

    Um, maybe because regular non-developer type people don't run out and grab the latest kernel that just came out and compile it themselve for the hell of it. Instead, they run whatever version comes with their distro.

    Anyone running the latest bleeding edge stuff keeps up with the LKML anyway, and KNOWS what is going on, way before it would hit a news site like /.

    The sky is falling! Sheesh...

  2. Re:another victory for open source by Phexro · · Score: 4, Insightful

    "While the kernel which has fs corruption bug is supposed to be used by non-production, testing environment, and for those you like to use bleeding edge release."

    Bzzt. 2.4 is the current stable Linux branch, and 2.4.20 is the latest stable version of that branch.

    While this kind of thing is not uncommon in the development branch, it's awful to see in a point release of the stable branch.