mirror of https://github.com/vitalif/e2fsprogs
libext2fs: strict inline data overwrite should not return ENOSPC
If we're doing a strict overwrite (same data size) of data in an inline data file, we should be able to skip the size check. If the in-core EA representation is fine but the on-disk EA is slightly corrupt (this happens when fixing minor errors in an inline dir), the ext2fs_xattr_inode_max_size() call, which reads the disk EA, can lead us to think that there's no space when in reality there is no issue with doing a strict overwrite. Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com> Signed-off-by: Theodore Ts'o <tytso@mit.edu>crypto
parent
cd971869d7
commit
cffe0221eb
|
@ -574,7 +574,8 @@ errcode_t ext2fs_inline_data_set(ext2_filsys fs, ext2_ino_t ino,
|
|||
else
|
||||
free_inode_size = 0;
|
||||
|
||||
if (size > existing_size + free_ea_size + free_inode_size)
|
||||
if (size != existing_size &&
|
||||
size > existing_size + free_ea_size + free_inode_size)
|
||||
return EXT2_ET_INLINE_DATA_NO_SPACE;
|
||||
|
||||
memcpy((void *)inode->i_block, buf, EXT4_MIN_INLINE_DATA_SIZE);
|
||||
|
|
Loading…
Reference in New Issue