aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorZhouyi Zhou2018-01-09 23:34:19 -0600
committerGreg Kroah-Hartman2018-02-22 08:45:00 -0600
commitab63d810345106d97ec0580598426550a63cf65e (patch)
treecd4a5f7c9cbf926936ec0fd5daec8323d8a7e349
parent99863c1bfdbf08d9a9001ac2c7c4d4e66fcdab6d (diff)
downloadkernel-omap-ab63d810345106d97ec0580598426550a63cf65e.tar.gz
kernel-omap-ab63d810345106d97ec0580598426550a63cf65e.tar.xz
kernel-omap-ab63d810345106d97ec0580598426550a63cf65e.zip
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>
-rw-r--r--fs/ext4/super.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/fs/ext4/super.c b/fs/ext4/super.c
index 8bdb0cc2722f..742455292dfe 100644
--- a/fs/ext4/super.c
+++ b/fs/ext4/super.c
@@ -688,6 +688,7 @@ __acquires(bitlock)
688 } 688 }
689 689
690 ext4_unlock_group(sb, grp); 690 ext4_unlock_group(sb, grp);
691 ext4_commit_super(sb, 1);
691 ext4_handle_error(sb); 692 ext4_handle_error(sb);
692 /* 693 /*
693 * We only get here in the ERRORS_RO case; relocking the group 694 * We only get here in the ERRORS_RO case; relocking the group