fs/ntfs3: fix lseek EINVAL on sparse/compressed files with 64-bit clusters
A message that is not in the archive (sent off-list or not yet received): [email protected]
PATCH v2 1/2 fs/ntfs3: load ATTR_BITMAP run extents from $MFT extension records
v2: fix malformed hunk header in patch (no code change)
When $MFT's ATTR_BITMAP attribute is heavily fragmented, its run list can span multiple MFT extension records (attribute list entries with vcn > 0). The non-primary segment handler in ntfs_read_mft() only processed ATTR_DATA extension segments for MFT_REC_MFT, silently skipping any ATTR_BITMAP segments. This left sbi->mft.bitmap.run incomplete, causing wnd_init() to fail with -ENOENT when wnd_rescan() tried to look up a VCN not covered by the truncated run list.
Observed on a 16 TB NTFS volume (0xFFFFFEFF total clusters) whose MFT bitmap run list was split across 97 extents in extension records. wnd_rescan() successfully looked up VCNs 0-122 from the runs loaded from the base record, then failed at VCN 123 (the last cluster of the bitmap) whose run was only present in an extension record.
Fix by extending the MFT_REC_MFT special case to also handle ATTR_BITMAP extension segments, storing their runs into sbi->mft.bitmap.run the same way the primary segment does.
--- fs/ntfs3/inode.c | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-)
fs/ntfs3/inode.c +8 -2
@@ -127,10 +127,16 @@ static struct inode *ntfs_read_mft(struct inode *inode,if (le && le->vcn) {/* This is non primary attribute segment. Ignore if not MFT. */ -if (ino !=MFT_REC_MFT || attr->type !=ATTR_DATA ) +if (ino !=MFT_REC_MFT ) goto next_attr; - run = &ni->file.run; +if (attr->type ==ATTR_DATA ) + run = &ni->file.run; +else if (attr->type ==ATTR_BITMAP ) + run = &sbi->mft.bitmap.run; +else + goto next_attr; + asize =le32_to_cpu (attr->size); goto attr_unpack_run; }
--
2.x
PATCH v2 1/2 fs/ntfs3: load ATTR_BITMAP run extents from $MFT extension records
In reply to a message not in the archivev2: fix malformed hunk header in patch (no code change)
When $MFT's ATTR_BITMAP attribute is heavily fragmented, its run list can span multiple MFT extension records (attribute list entries with vcn > 0). The non-primary segment handler in ntfs_read_mft() only processed ATTR_DATA extension segments for MFT_REC_MFT, silently skipping any ATTR_BITMAP segments. This left sbi->mft.bitmap.run incomplete, causing wnd_init() to fail with -ENOENT when wnd_rescan() tried to look up a VCN not covered by the truncated run list.
Observed on a 16 TB NTFS volume (0xFFFFFEFF total clusters) whose MFT bitmap run list was split across 97 extents in extension records. wnd_rescan() successfully looked up VCNs 0-122 from the runs loaded from the base record, then failed at VCN 123 (the last cluster of the bitmap) whose run was only present in an extension record.
Fix by extending the MFT_REC_MFT special case to also handle ATTR_BITMAP extension segments, storing their runs into sbi->mft.bitmap.run the same way the primary segment does.
--- fs/ntfs3/inode.c | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-)
fs/ntfs3/inode.c +8 -2
@@ -127,10 +127,16 @@ static struct inode *ntfs_read_mft(struct inode *inode,if (le && le->vcn) {/* This is non primary attribute segment. Ignore if not MFT. */ -if (ino !=MFT_REC_MFT || attr->type !=ATTR_DATA ) +if (ino !=MFT_REC_MFT ) goto next_attr; - run = &ni->file.run; +if (attr->type ==ATTR_DATA ) + run = &ni->file.run; +else if (attr->type ==ATTR_BITMAP ) + run = &sbi->mft.bitmap.run; +else + goto next_attr; + asize =le32_to_cpu (attr->size); goto attr_unpack_run; }
--
2.x
PATCH v2 2/2 fs/ntfs3: fix lseek EINVAL on sparse/compressed files with 64-bit clusters
In reply to a message not in the archiveWhen 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.
--- fs/ntfs3/super.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
fs/ntfs3/super.c +1 -1
@@ -1193,7 +1193,7 @@ static int ntfs_fill_super(struct super_block *sb, struct fs_context *fc)#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. */
--
2.x
PATCH v2 2/2 fs/ntfs3: fix lseek EINVAL on sparse/compressed files with 64-bit clusters
In reply to a message not in the archiveWhen 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.
--- fs/ntfs3/super.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
fs/ntfs3/super.c +1 -1
@@ -1193,7 +1193,7 @@ static int ntfs_fill_super(struct super_block *sb, struct fs_context *fc)#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. */
--
2.x
A message that is not in the archive (sent off-list or not yet received): [email protected]
Re: [PATCH v2 1/2] fs/ntfs3: load ATTR_BITMAP run extents from $MFT extension records
Gentle ping on this two-patch series (v2, sent 2026-06-13). Any feedback welcome.
Signature · 1 line
Senjin
Re: [PATCH v2 1/2] fs/ntfs3: load ATTR_BITMAP run extents from $MFT extension records
In reply to a message not in the archiveGentle ping on this two-patch series (v2, sent 2026-06-13). Any feedback welcome.
Signature · 1 line
Senjin
A message that is not in the archive (sent off-list or not yet received): [email protected]
Konstantin Komarov
maintainerQuoted 41 lines · Senjin
When
CONFIG_NTFS3_64BIT_CLUSTERis enabled,sbi->maxbytes_sparseis set to -1. As a signedloff_tthis is -1LL, the most negative value. Any lseek on a sparse or compressed file passes this as maxsize tovfs_setpos(), which returns-EINVALwhenever offset > maxsize, and since -1LL is less than any non-negative offset, every seek fails, includinglseek(fd, 0, SEEK_SET).The intent of -1 here appears to be "no limit" (matching the spirit of
MAX_LFS_FILESIZEassigned tosbi->maxbytesandsb->s_maxbytesin the same block), but the signed type makes it the minimum instead of the maximum.Fix by assigning
MAX_LFS_FILESIZEtosbi->maxbytes_sparsein the 64-bit cluster path, consistent with the other two limits set there.Observed on a 16 TB NTFS volume with
0xFFFFFEFFtotal clusters compiled withCONFIG_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 setsmaxbytes_sparseto (1ull << (cluster_bits+ 32)) - 1, a large positive value.Signed-off-by Senjin <[email protected]>--- fs/ntfs3/super.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)fs/ntfs3/super.c +1
-2@@ -1193,7 +1193,7 @@ static int ntfs_fill_super(struct super_block *sb, struct fs_context *fc)#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. */ --
Quoted 1 line
2.x
Hello,
Sorry for the delay.
Your patch is applied, thank you.
Regards,
Konstantin