From: syzbot <syzbot+83c9dd5c0dcf6184fdbf@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, nirbhay.lkd@gmail.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ntfs3?] KMSAN: uninit-value in attr_set_size
Date: Mon, 06 Oct 2025 09:22:03 -0700 [thread overview]
Message-ID: <68e3ecab.a00a0220.298cc0.0464.GAE@google.com> (raw)
In-Reply-To: <CABGqKE12ATMeEx-EasTDyV-pQK9sLKKwBjhus7bMUNgRM64o_Q@mail.gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+83c9dd5c0dcf6184fdbf@syzkaller.appspotmail.com
Tested-by: syzbot+83c9dd5c0dcf6184fdbf@syzkaller.appspotmail.com
Tested on:
commit: 4a715314 Add linux-next specific files for 20251006
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=15612304580000
kernel config: https://syzkaller.appspot.com/x/.config?x=78e3a0444ed8b621
dashboard link: https://syzkaller.appspot.com/bug?extid=83c9dd5c0dcf6184fdbf
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=16e395cd980000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2025-10-06 16:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABGqKE12ATMeEx-EasTDyV-pQK9sLKKwBjhus7bMUNgRM64o_Q@mail.gmail.com>
2025-10-06 16:22 ` syzbot [this message]
2025-10-06 22:38 [PATCH] fs/ntfs3: fix KMSAN uninit-value in ni_create_attr_list Nirbhay Sharma
2025-10-07 0:47 ` [syzbot] [ntfs3?] KMSAN: uninit-value in attr_set_size syzbot
[not found] <CABGqKE03duCVamFHSXsyCrWj_esqHswu4vfb3v8uEGrUTDep2Q@mail.gmail.com>
2025-10-06 17:15 ` syzbot
[not found] <CABGqKE0FCWJ0EjzV5irNWtnLe5n9SGeqfmMEHPzWtsXhfUXXvg@mail.gmail.com>
2025-10-06 14:39 ` syzbot
-- strict thread matches above, loose matches on Subject: below --
2025-10-05 23: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=68e3ecab.a00a0220.298cc0.0464.GAE@google.com \
--to=syzbot+83c9dd5c0dcf6184fdbf@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nirbhay.lkd@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