diff options
| author | Theodore Ts'o <tytso@mit.edu> | 2012-08-05 19:04:57 -0400 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2012-08-26 15:00:42 -0700 |
| commit | 8b9f3861678e35b18cef66728d0fa896bbda65b6 (patch) | |
| tree | 99a1336ea8e0dcc55d1c7f2a61f21526cfcf2f88 /fs/ext4 | |
| parent | 75a757189880a31759ed25c23229f085890cddb1 (diff) | |
ext4: make sure the journal sb is written in ext4_clear_journal_err()
commit d796c52ef0b71a988364f6109aeb63d79c5b116b upstream.
After we transfer set the EXT4_ERROR_FS bit in the file system
superblock, it's not enough to call jbd2_journal_clear_err() to clear
the error indication from journal superblock --- we need to call
jbd2_journal_update_sb_errno() as well. Otherwise, when the root file
system is mounted read-only, the journal is replayed, and the error
indicator is transferred to the superblock --- but the s_errno field
in the jbd2 superblock is left set (since although we cleared it in
memory, we never flushed it out to disk).
This can end up confusing e2fsck. We should make e2fsck more robust
in this case, but the kernel shouldn't be leaving things in this
confused state, either.
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'fs/ext4')
| -rw-r--r-- | fs/ext4/super.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/fs/ext4/super.c b/fs/ext4/super.c index 7fe3869d33d5..78fb7ff3adb8 100644 --- a/fs/ext4/super.c +++ b/fs/ext4/super.c @@ -4227,6 +4227,7 @@ static void ext4_clear_journal_err(struct super_block *sb, ext4_commit_super(sb, 1); jbd2_journal_clear_err(journal); + jbd2_journal_update_sb_errno(journal); } } |