Re: [PATCH] e2fsck: zap extent-format inode with no extent header

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, Nov 28, 2015 at 01:51:32PM -0800, Darrick J. Wong wrote:
> The kernel requires all inodes with the extent flag set to have a
> valid extent tree header in i_block.  The ext2fs_extent_open2 prefers
> to initialize the header if i_block is zeroed, but e2fsck never writes
> the new header to disk.  Since the kernel won't create inodes with the
> flag and no header anyway, zap such files.
> 
> Reported-by: Bo Branten <bosse@xxxxxxxxxx>
> Signed-off-by: Darrick J. Wong <darrick.wong@xxxxxxxxxx>

Thanks, applied.

						- 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



[Index of Archives]     [Reiser Filesystem Development]     [Ceph FS]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite National Park]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]     [Linux Media]

  Powered by Linux