remarkable-linux/fs/jbd2
Hidehiro Kawai 77e841de8a jbd2: abort when failed to log metadata buffers
If we failed to write metadata buffers to the journal space and
succeeded to write the commit record, stale data can be written
back to the filesystem as metadata in the recovery phase.

To avoid this, when we failed to write out metadata buffers,
abort the journal before writing the commit record.

We can also avoid this kind of corruption by using the journal
checksum feature because it can detect invalid metadata blocks in the
journal and avoid them from being replayed.  So we don't need to care
about asynchronous commit record writeout with a checksum.

Signed-off-by: Hidehiro Kawai <hidehiro.kawai.ez@hitachi.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
2008-10-12 16:39:16 -04:00
..
checkpoint.c ext4: Add debugging markers that can be used by systemtap 2008-10-05 20:50:06 -04:00
commit.c jbd2: abort when failed to log metadata buffers 2008-10-12 16:39:16 -04:00
journal.c ext4/jbd2: Avoid WARN() messages when failing to write to the superblock 2008-10-06 21:35:40 -04:00
Makefile
recovery.c jbd2: If a journal checksum error is detected, propagate the error to ext4 2008-06-06 17:50:40 -04:00
revoke.c jdb2: replace remaining __FUNCTION__ occurrences 2008-04-17 10:38:59 -04:00
transaction.c lockdep: rename map_[acquire|release]() => lock_map_[acquire|release]() 2008-08-11 10:30:30 +02:00