diff options
| author | Daeho Jeong <daeho.jeong@samsung.com> | 2015-07-23 09:46:11 -0400 |
|---|---|---|
| committer | Theodore Ts'o <tytso@mit.edu> | 2015-07-23 09:46:11 -0400 |
| commit | 564bc402526e437729ecafe3c3511f7cab9f0327 (patch) | |
| tree | 172a4b1a015d6d42d01a132f2fca8bd2af27139f /fs/ext4 | |
| parent | bb9a4e7e824e998070c2a2d1d4c67bc971ab72b8 (diff) | |
| download | blackbird-op-linux-564bc402526e437729ecafe3c3511f7cab9f0327.tar.gz blackbird-op-linux-564bc402526e437729ecafe3c3511f7cab9f0327.zip | |
ext4, jbd2: add REQ_FUA flag when recording an error in the superblock
When an error condition is detected, an error status should be recorded into
superblocks of EXT4 or JBD2. However, the write request is submitted now
without REQ_FUA flag, even in "barrier=1" mode, which is followed by
panic() function in "errors=panic" mode. On mobile devices which make
whole system reset as soon as kernel panic occurs, this write request
containing an error flag will disappear just from storage cache without
written to the physical cells. Therefore, when next start, even forever,
the error flag cannot be shown in both superblocks, and e2fsck cannot fix
the filesystem problems automatically, unless e2fsck is executed in
force checking mode.
[ Changed use test_opt(sb, BARRIER) of checking the journal flags -- TYT ]
Signed-off-by: Daeho Jeong <daeho.jeong@samsung.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Diffstat (limited to 'fs/ext4')
| -rw-r--r-- | fs/ext4/super.c | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/fs/ext4/super.c b/fs/ext4/super.c index 14909cd91515..a51db9ca90fd 100644 --- a/fs/ext4/super.c +++ b/fs/ext4/super.c @@ -4667,7 +4667,8 @@ static int ext4_commit_super(struct super_block *sb, int sync) ext4_superblock_csum_set(sb); mark_buffer_dirty(sbh); if (sync) { - error = sync_dirty_buffer(sbh); + error = __sync_dirty_buffer(sbh, + test_opt(sb, BARRIER) ? WRITE_FUA : WRITE_SYNC); if (error) return error; |
