diff options
| author | Zhouyi Zhou <zhouzhouyi@gmail.com> | 2018-01-10 00:34:19 -0500 |
|---|---|---|
| committer | Theodore Ts'o <tytso@mit.edu> | 2018-01-10 00:34:19 -0500 |
| commit | 06f29cc81f0350261f59643a505010531130eea0 (patch) | |
| tree | e40713910babd2c1b54ebfa488a7c5aa7cb8441a /fs/ext4 | |
| parent | f69120ce6c024aa634a8fc25787205e42f0ccbe6 (diff) | |
| download | linux-06f29cc81f0350261f59643a505010531130eea0.tar.gz linux-06f29cc81f0350261f59643a505010531130eea0.tar.xz | |
ext4: save error to disk in __ext4_grp_locked_error()
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
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 2a7faf94bb90..be71f24a75a0 100644 --- a/fs/ext4/super.c +++ b/fs/ext4/super.c @@ -743,6 +743,7 @@ __acquires(bitlock) } ext4_unlock_group(sb, grp); + ext4_commit_super(sb, 1); ext4_handle_error(sb); /* * We only get here in the ERRORS_RO case; relocking the group |