public inbox for ntfs3@lists.linux.dev
 help / color / mirror / Atom feed
From: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
To: Deepanshu Kartikey <kartikey406@gmail.com>
Cc: <ntfs3@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
	<syzbot+c1e9aedbd913fadad617@syzkaller.appspotmail.com>
Subject: Re: [PATCH] fs/ntfs3: fix missing run load for vcn0 in attr_data_get_block_locked()
Date: Tue, 24 Mar 2026 18:55:43 +0100	[thread overview]
Message-ID: <bb8b3fed-141e-4aa3-86a9-3628e052d5a2@paragon-software.com> (raw)
In-Reply-To: <20260319074546.1085187-1-kartikey406@gmail.com>

On 3/19/26 08:45, Deepanshu Kartikey wrote:

> When a compressed or sparse attribute has its clusters frame-aligned,
> vcn is rounded down to the frame start using cmask, which can result
> in vcn != vcn0. In this case, vcn and vcn0 may reside in different
> attribute segments.
>
> The code already handles the case where vcn is in a different segment
> by loading its runs before allocation. However, it fails to load runs
> for vcn0 when vcn0 resides in a different segment than vcn. This causes
> run_lookup_entry() to return SPARSE_LCN for vcn0 since its segment was
> never loaded into the in-memory run list, triggering the WARN_ON(1).
>
> Fix this by adding a missing check for vcn0 after the existing vcn
> segment check. If vcn0 falls outside the current segment range
> [svcn, evcn1), find and load the attribute segment containing vcn0
> before performing the run lookup.
>
> The following scenario triggers the bug:
>    attr_data_get_block_locked()
>      vcn = vcn0 & cmask        <- vcn != vcn0 after frame alignment
>      load runs for vcn segment <- vcn0 segment not loaded!
>      attr_allocate_clusters()  <- allocation succeeds
>      run_lookup_entry(vcn0)    <- vcn0 not in run -> SPARSE_LCN
>      WARN_ON(1)                <- bug fires here!
>
> Reported-by: syzbot+c1e9aedbd913fadad617@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=c1e9aedbd913fadad617
> Fixes: c380b52f6c57 ("fs/ntfs3: Change new sparse cluster processing")
> Signed-off-by: Deepanshu Kartikey <Kartikey406@gmail.com>
> ---
>   fs/ntfs3/attrib.c | 14 ++++++++++++++
>   1 file changed, 14 insertions(+)
>
> diff --git a/fs/ntfs3/attrib.c b/fs/ntfs3/attrib.c
> index 6cb9bc5d605c..6ef7db82a35d 100644
> --- a/fs/ntfs3/attrib.c
> +++ b/fs/ntfs3/attrib.c
> @@ -1152,6 +1152,21 @@ int attr_data_get_block_locked(struct ntfs_inode *ni, CLST vcn, CLST clen,
>   			if (err)
>   				goto out;
>   		}
> +
> +		if (vcn0 < svcn || evcn1 <= vcn0) {
> +			struct ATTRIB *attr2;
> +
> +			attr2 = ni_find_attr(ni, attr_b, &le_b, ATTR_DATA, NULL,
> +					       0, &vcn0, &mi);
> +			if (!attr2) {
> +				err = -EINVAL;
> +				goto out;
> +			}
> +			err = attr_load_runs(attr2, ni, run, NULL);
> +			if (err)
> +				goto out;
> +		}
> +
>   		da = false; /* no delalloc for compressed file. */
>   	}
>   

Hello,

Queued for the next merge window, thank you.

Regards,
Konstantin


      reply	other threads:[~2026-03-24 17:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-19  7:45 [PATCH] fs/ntfs3: fix missing run load for vcn0 in attr_data_get_block_locked() Deepanshu Kartikey
2026-03-24 17:55 ` Konstantin Komarov [this message]

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=bb8b3fed-141e-4aa3-86a9-3628e052d5a2@paragon-software.com \
    --to=almaz.alexandrovich@paragon-software.com \
    --cc=kartikey406@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ntfs3@lists.linux.dev \
    --cc=syzbot+c1e9aedbd913fadad617@syzkaller.appspotmail.com \
    /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