The patch titled jbd: abort when failed to log metadata buffers has been removed from the -mm tree. Its filename was jbd-abort-when-failed-to-log-metadata-buffers.patch This patch was dropped because I don't think we want to go read-only on file data write errors The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/ ------------------------------------------------------ Subject: jbd: abort when failed to log metadata buffers From: Hidehiro Kawai <hidehiro.kawai.ez@xxxxxxxxxxx> 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. Signed-off-by: Hidehiro Kawai <hidehiro.kawai.ez@xxxxxxxxxxx> Acked-by: Jan Kara <jack@xxxxxxx> Cc: <linux-ext4@xxxxxxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- fs/jbd/commit.c | 3 +++ 1 file changed, 3 insertions(+) diff -puN fs/jbd/commit.c~jbd-abort-when-failed-to-log-metadata-buffers fs/jbd/commit.c --- a/fs/jbd/commit.c~jbd-abort-when-failed-to-log-metadata-buffers +++ a/fs/jbd/commit.c @@ -734,6 +734,9 @@ wait_for_iobuf: /* AKPM: bforget here */ } + if (err) + journal_abort(journal, err); + jbd_debug(3, "JBD: commit phase 6\n"); if (journal_write_commit_record(journal, commit_transaction)) _ Patches currently in -mm which might be from hidehiro.kawai.ez@xxxxxxxxxxx are jbd-abort-when-failed-to-log-metadata-buffers.patch jbd-fix-error-handling-for-checkpoint-io.patch ext3-abort-ext3-if-the-journal-has-aborted.patch ext3-abort-ext3-if-the-journal-has-aborted-warning-fix.patch -- To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html