From: syzbot <syzbot+332bd4e9d148f11a87dc@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, sidharthseela@gmail.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ntfs3?] KMSAN: uninit-value in ntfs_read_hdr (3)
Date: Thu, 18 Sep 2025 12:56:02 -0700 [thread overview]
Message-ID: <68cc63d2.a00a0220.37dadf.0005.GAE@google.com> (raw)
In-Reply-To: <20250918193455.115481-1-sidharthseela@gmail.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
KMSAN: uninit-value in ntfs_read_hdr
=====================================================
BUG: KMSAN: uninit-value in ntfs_dir_emit fs/ntfs3/dir.c:335 [inline]
BUG: KMSAN: uninit-value in ntfs_read_hdr+0xfcc/0x13e0 fs/ntfs3/dir.c:385
ntfs_dir_emit fs/ntfs3/dir.c:335 [inline]
ntfs_read_hdr+0xfcc/0x13e0 fs/ntfs3/dir.c:385
ntfs_readdir+0xf21/0x1a30 fs/ntfs3/dir.c:496
iterate_dir+0x452/0x620 fs/readdir.c:108
__do_sys_getdents64 fs/readdir.c:410 [inline]
__se_sys_getdents64+0x17e/0x550 fs/readdir.c:396
__x64_sys_getdents64+0x97/0xe0 fs/readdir.c:396
x64_sys_call+0x3a14/0x3e20 arch/x86/include/generated/asm/syscalls_64.h:218
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xd9/0x210 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
Uninit was created at:
slab_post_alloc_hook mm/slub.c:4197 [inline]
slab_alloc_node mm/slub.c:4240 [inline]
kmem_cache_alloc_noprof+0x81b/0xec0 mm/slub.c:4247
ntfs_lookup+0x60/0x410 fs/ntfs3/namei.c:71
lookup_one_qstr_excl+0x23f/0x7a0 fs/namei.c:1697
filename_create+0x2cb/0x590 fs/namei.c:4140
do_linkat+0x1fb/0x1040 fs/namei.c:4908
__do_sys_link fs/namei.c:4958 [inline]
__se_sys_link fs/namei.c:4956 [inline]
__x64_sys_link+0xd7/0x140 fs/namei.c:4956
x64_sys_call+0x162f/0x3e20 arch/x86/include/generated/asm/syscalls_64.h:87
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xd9/0x210 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
CPU: 1 UID: 0 PID: 6379 Comm: syz-executor Not tainted syzkaller #0 PREEMPT(none)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
=====================================================
Tested on:
commit: cbf658dd Merge tag 'net-6.17-rc7' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1430c0e2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=1b093ccee5a9e08c
dashboard link: https://syzkaller.appspot.com/bug?extid=332bd4e9d148f11a87dc
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=11383f62580000
next parent reply other threads:[~2025-09-18 19:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250918193455.115481-1-sidharthseela@gmail.com>
2025-09-18 19:56 ` syzbot [this message]
[not found] <CAPqLRf36qEgmaLxkGfURAQ549Em_==asxBSuy6PcoKYpXi05ag@mail.gmail.com>
2025-11-05 8:42 ` [syzbot] [ntfs3?] KMSAN: uninit-value in ntfs_read_hdr (3) syzbot
[not found] <CAPqLRf1_Y=mCBQKKHoSZJ3BxxsfMWYd+asreyGLofV+ge2UySg@mail.gmail.com>
2025-10-29 20:50 ` syzbot
[not found] <CAPqLRf3LgEErOjV3V2A6XsaBL=fvhGPFooXWSv4Vt2Q6juWGXQ@mail.gmail.com>
2025-10-26 16:26 ` syzbot
[not found] <20250922180305.163051-2-sidharthseela@gmail.com>
2025-09-22 19:42 ` syzbot
2025-09-17 22:55 syzbot
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=68cc63d2.a00a0220.37dadf.0005.GAE@google.com \
--to=syzbot+332bd4e9d148f11a87dc@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sidharthseela@gmail.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