[lkml]   [2018]   [May]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Patch in this message
Subject[PATCH 3.2 039/153] ext4: save error to disk in __ext4_grp_locked_error()
3.2.102-rc1 review patch.  If anyone has any objections, please let me know.


From: Zhouyi Zhou <>

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 <>
Signed-off-by: Theodore Ts'o <>
Signed-off-by: Ben Hutchings <>
fs/ext4/super.c | 1 +
1 file changed, 1 insertion(+)

--- a/fs/ext4/super.c
+++ b/fs/ext4/super.c
@@ -700,6 +700,7 @@ __acquires(bitlock)

ext4_unlock_group(sb, grp);
+ ext4_commit_super(sb, 1);
* We only get here in the ERRORS_RO case; relocking the group
 \ /
  Last update: 2018-05-30 13:15    [W:0.841 / U:1.372 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site