From: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
To: <senjin@hatchling.org>, <ntfs3@lists.linux.dev>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fs/ntfs3: load ATTR_BITMAP run extents from $MFT extension records
Date: Wed, 15 Jul 2026 19:02:37 +0200 [thread overview]
Message-ID: <8ae7b6fe-bb13-4019-9e13-c60a5bb2f3f8@paragon-software.com> (raw)
In-Reply-To: <6a28fa14873307c15d283e52@mailersend.net>
On 6/10/26 07:45, Senjin wrote:
> 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.
>
> Signed-off-by: Senjin <senjin@hatchling.org>
> ---
> fs/ntfs3/inode.c | 10 +++++++---
> 1 file changed, 7 insertions(+), 3 deletions(-)
>
> diff --git a/fs/ntfs3/inode.c b/fs/ntfs3/inode.c
> index XXXXXXX..XXXXXXX 100644
> --- a/fs/ntfs3/inode.c
> +++ b/fs/ntfs3/inode.c
> @@ -128,11 +128,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
Hello,
Very sorry for the delay.
Your patch is applied, thanks.
Regards,
Konstantin
next parent reply other threads:[~2026-07-15 17:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6a28fa14873307c15d283e52@mailersend.net>
2026-07-15 17:02 ` Konstantin Komarov [this message]
2026-06-10 5:45 Senjin
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=8ae7b6fe-bb13-4019-9e13-c60a5bb2f3f8@paragon-software.com \
--to=almaz.alexandrovich@paragon-software.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--cc=senjin@hatchling.org \
/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