Slashdot Mirror

← Back to Stories (view on slashdot.org)

2.4.20 ext3 Data Corrupting Bug Fixed

Posted by timothy on from the does-not-fix-mind-corruption dept.

An anonymous reader writes "The ext3 data corrupting bug found in the latest stable Linux kernel and reported by Slashdot here and here has been fixed. In this interesting KernelTrap story Andrew Morton describes the problem and offers a working patch. Evidently the bug has its roots in a much bigger design issue, something that won't likely be fixed in the current 2.4 kernel series. In any case, with Morton's patch applied your data will not be corrupted."

2 of 34 comments (clear)

  1. Should be front page. by jericho4.0 · · Score: 4, Insightful
    Why did /. have to cover this 3 times in the dev section. I know many non-dev types who jump on point releases as soon as they come out. They should know about this.

    I hate to say it, but maybe /. doesn't like stories that make linix look bad.

    --
    "A language that doesn't affect the way you think about programming, is not worth knowing" - Alan Perlis
  2. Re:Which as-shipped distros are affected by this? by Cecil · · Score: 4, Informative

    Which distributions ship using ext3 filesystems by default and setting them to mode journalled in their default ISO images? Um, none?

    Did you mean that you run your ext3 filesystems in full-journal mode, and would like to know if you have to update? Yes. Regardless of distro.

    In either case, please remember that journalled mode is NOT the default. The default is ordered. Unless you're explicitly setting your filesystem to full journalling, you aren't affected by this problem.

    HTH.

    --
    Random and weird software I've written.