From: syzbot <syzbot+0399100e525dd9696764@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 bcmp (3)
Date: Tue, 04 Nov 2025 15:37:04 -0800 [thread overview]
Message-ID: <690a8e20.050a0220.3d0d33.0019.GAE@google.com> (raw)
In-Reply-To: <CAPqLRf157uvgANx62xnz=Q0ouDp0oXM2fyFA8BRGs6+Vu45XOQ@mail.gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+0399100e525dd9696764@syzkaller.appspotmail.com
Tested-by: syzbot+0399100e525dd9696764@syzkaller.appspotmail.com
Tested on:
commit: 17490bd0 Add linux-next specific files for 20251104
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=14692114580000
kernel config: https://syzkaller.appspot.com/x/.config?x=22305ece5c093e2a
dashboard link: https://syzkaller.appspot.com/bug?extid=0399100e525dd9696764
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=11b12532580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2025-11-04 23:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPqLRf157uvgANx62xnz=Q0ouDp0oXM2fyFA8BRGs6+Vu45XOQ@mail.gmail.com>
2025-11-04 23:37 ` syzbot [this message]
[not found] <CAPqLRf0faZTieiVe_6XuJdhR7A02Uv6xjO2adVRUqwRLaWK29Q@mail.gmail.com>
2025-10-29 17:12 ` [syzbot] [ntfs3?] KMSAN: uninit-value in bcmp (3) syzbot
[not found] <CAPqLRf1xv2B+qfrR3Qq5L-AhD7Gn9tZ98M=LBo-B+DbOkn05uw@mail.gmail.com>
2025-10-26 13:31 ` 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=690a8e20.050a0220.3d0d33.0019.GAE@google.com \
--to=syzbot+0399100e525dd9696764@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