diff options
| author | Linus Torvalds <torvalds@linux-foundation.org> | 2012-10-30 15:35:16 -0700 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2012-10-30 15:35:16 -0700 |
| commit | 8c673cbc7682b3f2862fe42f8069cac20c09e160 (patch) | |
| tree | f20de69903a1c3d95f92098e24139c69c2d6a894 /kernel/module.c | |
| parent | 4476c0eead051ae6ff8abbc358763b00790d1635 (diff) | |
| parent | ffb5387e85d528fb6d0d924abfa3fbf0fc484071 (diff) | |
| download | linux-8c673cbc7682b3f2862fe42f8069cac20c09e160.tar.bz2 | |
Merge tag 'ext4_for_linus_stable' of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4
Pull ext4 bugfix from Ted Ts'o:
"This fixes the root cause of the ext4 data corruption bug which raised
a ruckus on LWN, Phoronix, and Slashdot.
This bug only showed up when non-standard mount options
(journal_async_commit and/or journal_checksum) were enabled, and when
the file system was not cleanly unmounted, but the root cause was the
inode bitmap modifications was not being properly journaled.
This could potentially lead to minor file system corruptions (pass 5
complaints with the inode allocation bitmap) after an unclean shutdown
under the wrong/unlucky workloads, but it turned into major failure if
the journal_checksum and/or jouaral_async_commit was enabled."
* tag 'ext4_for_linus_stable' of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4:
ext4: fix unjournaled inode bitmap modification
Diffstat (limited to 'kernel/module.c')
0 files changed, 0 insertions, 0 deletions