From: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
To: Edward Adam Davis <eadavis@qq.com>,
<syzbot+7be88937363ac7ab7bb0@syzkaller.appspotmail.com>
Cc: <linux-kernel@vger.kernel.org>, <ntfs3@lists.linux.dev>,
<syzkaller-bugs@googlegroups.com>
Subject: Re: [PATCH] fs/ntfs3: prevent uninitialized lcn caused by zero len
Date: Mon, 2 Mar 2026 14:51:02 +0100 [thread overview]
Message-ID: <36ef9f6c-2d0f-4469-ac24-59a8aec2607c@paragon-software.com> (raw)
In-Reply-To: <tencent_24B18DF3926D5DB85DAA195F4FBD0D8E2507@qq.com>
On 2/23/26 09:01, Edward Adam Davis wrote:
> syzbot reported a uninit-value in ntfs_iomap_begin [1].
>
> Since runs was not touched yet, run_lookup_entry() immediately fails
> and returns false, which makes the value of "*len" 0.
> Simultaneously, the new value and err value are also 0, causing the
> logic in attr_data_get_block_locked() to jump directly to ok, ultimately
> resulting in *lcn being triggered before it is set [1].
>
> In ntfs_iomap_begin(), the check for a 0 value in clen is moved forward
> to before updating lcn to avoid this [1].
>
> [1]
> BUG: KMSAN: uninit-value in ntfs_iomap_begin+0x8c0/0x1460 fs/ntfs3/inode.c:825
> ntfs_iomap_begin+0x8c0/0x1460 fs/ntfs3/inode.c:825
> iomap_iter+0x9b7/0x1540 fs/iomap/iter.c:110
>
> Local variable lcn created at:
> ntfs_iomap_begin+0x15d/0x1460 fs/ntfs3/inode.c:786
>
> Fixes: 10d7c95af043 ("fs/ntfs3: add delayed-allocation (delalloc) support")
> Reported-by: syzbot+7be88937363ac7ab7bb0@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=7be88937363ac7ab7bb0
> Tested-by: syzbot+7be88937363ac7ab7bb0@syzkaller.appspotmail.com
> Signed-off-by: Edward Adam Davis <eadavis@qq.com>
> ---
> fs/ntfs3/inode.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/fs/ntfs3/inode.c b/fs/ntfs3/inode.c
> index 6e65066ebcc1..eac421cf98a8 100644
> --- a/fs/ntfs3/inode.c
> +++ b/fs/ntfs3/inode.c
> @@ -822,6 +822,11 @@ static int ntfs_iomap_begin(struct inode *inode, loff_t offset, loff_t length,
> return err;
> }
>
> + if (!clen) {
> + /* broken file? */
> + return -EINVAL;
> + }
> +
> if (lcn == EOF_LCN) {
> /* request out of file. */
> if (flags & IOMAP_REPORT) {
> @@ -855,11 +860,6 @@ static int ntfs_iomap_begin(struct inode *inode, loff_t offset, loff_t length,
> return 0;
> }
>
> - if (!clen) {
> - /* broken file? */
> - return -EINVAL;
> - }
> -
> iomap->bdev = inode->i_sb->s_bdev;
> iomap->offset = offset;
> iomap->length = ((loff_t)clen << cluster_bits) - off;
Hello,
Your patch is applied. Thanks.
Regards,
Konstantin
prev parent reply other threads:[~2026-03-02 13:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-22 11:33 [syzbot] [ntfs3?] KMSAN: uninit-value in ntfs_iomap_begin syzbot
2026-02-23 7:23 ` Edward Adam Davis
2026-02-23 7:53 ` syzbot
2026-02-23 8:01 ` [PATCH] fs/ntfs3: prevent uninitialized lcn caused by zero len Edward Adam Davis
2026-03-02 13:51 ` 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=36ef9f6c-2d0f-4469-ac24-59a8aec2607c@paragon-software.com \
--to=almaz.alexandrovich@paragon-software.com \
--cc=eadavis@qq.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--cc=syzbot+7be88937363ac7ab7bb0@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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
all inboxes | Powered by JetHome®