From: Senjin <senjin@hatchling.org>
To: ntfs3@lists.linux.dev
Cc: almaz.alexandrovich@paragon-software.com, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] fs/ntfs3: two fixes for large NTFS volumes
Date: 13 Jun 2026 20:16:13 -0000 [thread overview]
Message-ID: <6a2dba8dc035b44a31894af2@mailersend.net> (raw)
Both patches were found on a 16 TB NTFS volume with 0xFFFFFEFF total
clusters, compiled with CONFIG_NTFS3_64BIT_CLUSTER=y.
Patch 1 is v2 of the previously submitted MFT bitmap fix, correcting
a malformed hunk header in the diff. No code change from v1.
Patch 2 is a new fix: sbi->maxbytes_sparse is assigned -1 in the
CONFIG_NTFS3_64BIT_CLUSTER path. As a signed loff_t, -1 is the most
negative value, causing vfs_setpos() to return -EINVAL for every seek
on sparse or compressed files on such a volume. Sequential reads work
correctly; random access does not. Fix assigns MAX_LFS_FILESIZE
instead, consistent with the other two limits in the same block.
Senjin (2):
fs/ntfs3: load ATTR_BITMAP run extents from $MFT extension records
fs/ntfs3: fix lseek EINVAL on sparse/compressed files with 64-bit clusters
fs/ntfs3/inode.c | 10 +++++++---
fs/ntfs3/super.c | 2 +-
2 files changed, 8 insertions(+), 4 deletions(-)
reply other threads:[~2026-06-13 20:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6a2dba8dc035b44a31894af2@mailersend.net \
--to=senjin@hatchling.org \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome