From: syzbot <syzbot+332bd4e9d148f11a87dc@syzkaller.appspotmail.com>
To: kubik.bartlomiej@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ntfs3?] KMSAN: uninit-value in ntfs_read_hdr (3)
Date: Wed, 05 Nov 2025 00:42:02 -0800 [thread overview]
Message-ID: <690b0dda.050a0220.2e3c35.0002.GAE@google.com> (raw)
In-Reply-To: <CAPqLRf36qEgmaLxkGfURAQ549Em_==asxBSuy6PcoKYpXi05ag@mail.gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+332bd4e9d148f11a87dc@syzkaller.appspotmail.com
Tested-by: syzbot+332bd4e9d148f11a87dc@syzkaller.appspotmail.com
Tested on:
commit: 84d39fb9 Add linux-next specific files for 20251105
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=1782a114580000
kernel config: https://syzkaller.appspot.com/x/.config?x=d1fcb9bd985db1e7
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=10d8a532580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2025-11-05 8:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPqLRf36qEgmaLxkGfURAQ549Em_==asxBSuy6PcoKYpXi05ag@mail.gmail.com>
2025-11-05 8:42 ` syzbot [this message]
[not found] <CAPqLRf1_Y=mCBQKKHoSZJ3BxxsfMWYd+asreyGLofV+ge2UySg@mail.gmail.com>
2025-10-29 20:50 ` [syzbot] [ntfs3?] KMSAN: uninit-value in ntfs_read_hdr (3) 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
[not found] <20250918193455.115481-1-sidharthseela@gmail.com>
2025-09-18 19:56 ` 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=690b0dda.050a0220.2e3c35.0002.GAE@google.com \
--to=syzbot+332bd4e9d148f11a87dc@syzkaller.appspotmail.com \
--cc=kubik.bartlomiej@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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