diff options
| author | Vegard Nossum <vegard.nossum@oracle.com> | 2016-07-14 23:21:35 -0400 | 
|---|---|---|
| committer | Andreas Blaesius <skate4life@gmx.de> | 2017-05-10 17:45:22 +0200 | 
| commit | cf47c5c53757d49dbcf7088364d00e99b3f8774e (patch) | |
| tree | 5f81c013640880a777cc70b317eaadfb5e4e5460 | |
| parent | 967b50c7e99f26564b219d042953b61ffc5491cd (diff) | |
| download | kernel_samsung_espresso10-cf47c5c53757d49dbcf7088364d00e99b3f8774e.zip kernel_samsung_espresso10-cf47c5c53757d49dbcf7088364d00e99b3f8774e.tar.gz kernel_samsung_espresso10-cf47c5c53757d49dbcf7088364d00e99b3f8774e.tar.bz2  | |
ext4: short-cut orphan cleanup on error
commit c65d5c6c81a1f27dec5f627f67840726fcd146de upstream.
If we encounter a filesystem error during orphan cleanup, we should stop.
Otherwise, we may end up in an infinite loop where the same inode is
processed again and again.
    EXT4-fs (loop0): warning: checktime reached, running e2fsck is recommended
    EXT4-fs error (device loop0): ext4_mb_generate_buddy:758: group 2, block bitmap and bg descriptor inconsistent: 6117 vs 0 free clusters
    Aborting journal on device loop0-8.
    EXT4-fs (loop0): Remounting filesystem read-only
    EXT4-fs error (device loop0) in ext4_free_blocks:4895: Journal has aborted
    EXT4-fs error (device loop0) in ext4_do_update_inode:4893: Journal has aborted
    EXT4-fs error (device loop0) in ext4_do_update_inode:4893: Journal has aborted
    EXT4-fs error (device loop0) in ext4_ext_remove_space:3068: IO failure
    EXT4-fs error (device loop0) in ext4_ext_truncate:4667: Journal has aborted
    EXT4-fs error (device loop0) in ext4_orphan_del:2927: Journal has aborted
    EXT4-fs error (device loop0) in ext4_do_update_inode:4893: Journal has aborted
    EXT4-fs (loop0): Inode 16 (00000000618192a0): orphan list check failed!
    [...]
    EXT4-fs (loop0): Inode 16 (0000000061819748): orphan list check failed!
    [...]
    EXT4-fs (loop0): Inode 16 (0000000061819bf0): orphan list check failed!
    [...]
Change-Id: I5004d92629fecfbca5e2d8b1225bec2038199a54
See-also: c9eb13a9105 ("ext4: fix hang when processing corrupted orphaned inode list")
Cc: Jan Kara <jack@suse.cz>
Signed-off-by: Vegard Nossum <vegard.nossum@oracle.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
| -rw-r--r-- | fs/ext4/super.c | 10 | 
1 files changed, 10 insertions, 0 deletions
diff --git a/fs/ext4/super.c b/fs/ext4/super.c index e2725f0..9651d22 100644 --- a/fs/ext4/super.c +++ b/fs/ext4/super.c @@ -2190,6 +2190,16 @@ static void ext4_orphan_cleanup(struct super_block *sb,  	while (es->s_last_orphan) {  		struct inode *inode; +		/* +		 * We may have encountered an error during cleanup; if +		 * so, skip the rest. +		 */ +		if (EXT4_SB(sb)->s_mount_state & EXT4_ERROR_FS) { +			jbd_debug(1, "Skipping orphan recovery on fs with errors.\n"); +			es->s_last_orphan = 0; +			break; +		} +  		inode = ext4_orphan_get(sb, le32_to_cpu(es->s_last_orphan));  		if (IS_ERR(inode)) {  			es->s_last_orphan = 0;  | 
