tree 172a4b1a015d6d42d01a132f2fca8bd2af27139f
parent bb9a4e7e824e998070c2a2d1d4c67bc971ab72b8
author Daeho Jeong <daeho.jeong@samsung.com> 1437659171 -0400
committer Theodore Ts'o <tytso@mit.edu> 1437659171 -0400

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>