| From 06f29cc81f0350261f59643a505010531130eea0 Mon Sep 17 00:00:00 2001 |
| From: Zhouyi Zhou <zhouzhouyi@gmail.com> |
| Date: Wed, 10 Jan 2018 00:34:19 -0500 |
| Subject: ext4: save error to disk in __ext4_grp_locked_error() |
| |
| From: Zhouyi Zhou <zhouzhouyi@gmail.com> |
| |
| 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 | 1 + |
| 1 file changed, 1 insertion(+) |
| |
| --- a/fs/ext4/super.c |
| +++ b/fs/ext4/super.c |
| @@ -688,6 +688,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 |