OSDN Git Service

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)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Thu, 22 Feb 2018 14:42:26 +0000 (15:42 +0100)
commit2e38988253c165a8b81d3ceea55fb68cb2d19e1c
tree7eba70dd37b90404471f4eac575358b2fe28ee06
parent4d4d103a1b7e2990bcdbf83a24a83b3e351b6838
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>
Cc: stable@vger.kernel.org
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
fs/ext4/super.c