ext4: save error to disk in __ext4_grp_locked_error()
authorZhouyi Zhou <zhouzhouyi@gmail.com>
Wed, 10 Jan 2018 05:34:19 +0000 (00:34 -0500)
committerBen Hutchings <ben@decadent.org.uk>
Thu, 31 May 2018 23:30:06 +0000 (00:30 +0100)
commitc98b8a3d91dfdefd23e4e804ce96051b1945c7f4
tree7a2c3c43db0c2e02b459050c1080ba2672777b85
parent1de5a50baa2740e190e650bf6a394af377c4d5da
ext4: save error to disk in __ext4_grp_locked_error()

commit 06f29cc81f0350261f59643a505010531130eea0 upstream.

In the function __ext4_grp_locked_error(), __save_error_info()
is called to save error info in super block block, but does not sync
that information to disk to info the subsequence fsck after reboot.

This patch writes the error information to disk.  After this patch,
I think there is no obvious EXT4 error handle branches which leads to
"Remounting filesystem read-only" will leave the disk partition miss
the subsequence fsck.

Signed-off-by: Zhouyi Zhou <zhouzhouyi@gmail.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
fs/ext4/super.c