From: syzbot <syzbot+a9a4bedfca6aa9d7fa24@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, rpthibeault@gmail.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bluetooth?] KMSAN: uninit-value in hci_cmd_complete_evt
Date: Fri, 24 Oct 2025 09:11:04 -0700 [thread overview]
Message-ID: <68fba518.a70a0220.3bf6c6.01a5.GAE@google.com> (raw)
In-Reply-To: <aPueHB4AaBdRL9hL@rpthibeault-XPS-13-9305>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+a9a4bedfca6aa9d7fa24@syzkaller.appspotmail.com
Tested-by: syzbot+a9a4bedfca6aa9d7fa24@syzkaller.appspotmail.com
Tested on:
commit: 6fab32bb MAINTAINERS: add Mark Brown as a linux-next m..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17292d2f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=ed2b1ae1fa9a0fdc
dashboard link: https://syzkaller.appspot.com/bug?extid=a9a4bedfca6aa9d7fa24
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=15957734580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2025-10-24 16:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <aPueHB4AaBdRL9hL@rpthibeault-XPS-13-9305>
2025-10-24 16:11 ` syzbot [this message]
[not found] <aPgEdIAnSTBroJuS@rpthibeault-XPS-13-9305>
2025-10-22 5:22 ` [syzbot] [bluetooth?] KMSAN: uninit-value in hci_cmd_complete_evt syzbot
[not found] <CAOeBcHMF2n1Bf5Tdx1kd9kPOAg-nCofANxY_RfV7VmObdvCgeQ@mail.gmail.com>
2025-10-02 17:29 ` syzbot
[not found] <ank5qnbeu55cd7vktzjd2iagozehy62m4v7bbapnmsbxcks5zv@xb6nlrhtsk6x>
2025-07-22 6:03 ` syzbot
2024-11-16 13:13 syzbot
2025-02-24 7:19 ` 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=68fba518.a70a0220.3bf6c6.01a5.GAE@google.com \
--to=syzbot+a9a4bedfca6aa9d7fa24@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rpthibeault@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