mirror of
https://github.com/torvalds/linux.git
synced 2026-09-24 06:24:02 +02:00
fs/ntfs3: fix lseek EINVAL on sparse/compressed files with 64-bit clusters
When CONFIG_NTFS3_64BIT_CLUSTER is enabled, sbi->maxbytes_sparse is set to -1. As a signed loff_t this is -1LL, the most negative value. Any lseek on a sparse or compressed file passes this as maxsize to vfs_setpos(), which returns -EINVAL whenever offset > maxsize, and since -1LL is less than any non-negative offset, every seek fails, including lseek(fd, 0, SEEK_SET). The intent of -1 here appears to be "no limit" (matching the spirit of MAX_LFS_FILESIZE assigned to sbi->maxbytes and sb->s_maxbytes in the same block), but the signed type makes it the minimum instead of the maximum. Fix by assigning MAX_LFS_FILESIZE to sbi->maxbytes_sparse in the 64-bit cluster path, consistent with the other two limits set there. Observed on a 16 TB NTFS volume with 0xFFFFFEFF total clusters compiled with CONFIG_NTFS3_64BIT_CLUSTER=y. Sequential reads via dd/cp worked correctly; any lseek call on sparse files returned EINVAL, preventing archive managers and other tools from random-accessing files on the volume. The non-64-bit-cluster path correctly sets maxbytes_sparse to (1ull << (cluster_bits + 32)) - 1, a large positive value. Signed-off-by: Senjin <senjin@hatchling.org> Signed-off-by: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
This commit is contained in:
parent
e31886cb6e
commit
789af83e41
|
|
@ -1189,7 +1189,7 @@ static int ntfs_init_from_boot(struct super_block *sb, u32 sector_size,
|
|||
#ifdef CONFIG_NTFS3_64BIT_CLUSTER
|
||||
if (clusters >= (1ull << (64 - cluster_bits)))
|
||||
sbi->maxbytes = -1;
|
||||
sbi->maxbytes_sparse = -1;
|
||||
sbi->maxbytes_sparse = MAX_LFS_FILESIZE;
|
||||
sb->s_maxbytes = MAX_LFS_FILESIZE;
|
||||
#else
|
||||
/* Maximum size for sparse file. */
|
||||
|
|
|
|||
Loading…
Reference in New Issue
Block a user