On Mon, Jan 26, 2015 at 11:36:50PM -0800, Darrick J. Wong wrote: > If we decide to clear a special inode because of bad mappings, we need > to zero the i_block array. The clearing routine depends on setting > i_links_count to zero to keep us from re-checking the block maps, > but that field isn't checked for special inodes. Therefore, if we > haven't erased the mappings, check_blocks will restart fsck and fsck > will try to check the blocks again, leading to an infinite loop. > > (This seems easy to trigger if the bootloader inode extent map is > corrupted.) > > Signed-off-by: Darrick J. Wong <darrick.wong@xxxxxxxxxx> Applied, thanks. - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
