On Wed, Feb 22, 2017 at 01:22:46PM -0800, Eric Biggers wrote: > From: Eric Biggers <ebiggers@xxxxxxxxxx> > > If ext4_convert_inline_data() was called on a directory with inline > data, the filesystem was left in an inconsistent state (as considered by > e2fsck) because the file size was not increased to cover the new block. > This happened because the inode was not marked dirty after i_disksize > was updated. Fix this by marking the inode dirty at the end of > ext4_finish_convert_inline_dir(). > > This bug was probably not noticed before because most users mark the > inode dirty afterwards for other reasons. But if userspace executed > FS_IOC_SET_ENCRYPTION_POLICY with invalid parameters, as exercised by > 'kvm-xfstests -c adv generic/396', then the inode was never marked dirty > after updating i_disksize. > > Cc: stable@xxxxxxxxxxxxxxx > Signed-off-by: Eric Biggers <ebiggers@xxxxxxxxxx> Applied, thanks. - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-fscrypt" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|