Re: [PATCH 12/49] libext2fs: during inlinedata expand, don't corrupt inode

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

 



On Mon, Mar 10, 2014 at 11:55:15PM -0700, Darrick J. Wong wrote:
> When expanding an inline data inode, it's possible that the reduction
> in the size of the EA structures causes the freeing of the EA block,
> which changes the inode.  If this happens, the local version of the
> inode that ext2fs_inline_data_expand was modifying will be out of sync
> with what's on the disk.  This local copy gets written out to disk
> after a block allocation, at which point it's possible that the inode
> EA block and logical block zero point to the same physical block,
> which is bad news.
> 
> Therefore, write the local copy to disk before removing the inline
> data EA, and reread it afterwards.
> 
> 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