From: syzbot <syzbot+bc71245e56f06e3127b7@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bluetooth?] KASAN: slab-use-after-free Read in force_devcd_write
Date: Fri, 04 Jul 2025 08:16:04 -0700 [thread overview]
Message-ID: <6867f034.a70a0220.29cf51.0020.GAE@google.com> (raw)
In-Reply-To: <20250704145211.2487-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+bc71245e56f06e3127b7@syzkaller.appspotmail.com
Tested-by: syzbot+bc71245e56f06e3127b7@syzkaller.appspotmail.com
Tested on:
commit: 4c06e63b Merge tag 'for-6.16-rc4-tag' of git://git.ker..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13cf4c8c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=9887aa986c36cc50
dashboard link: https://syzkaller.appspot.com/bug?extid=bc71245e56f06e3127b7
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=16888f70580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2025-07-04 15:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-25 2:26 [syzbot] [bluetooth?] KASAN: slab-use-after-free Read in force_devcd_write syzbot
2024-12-25 7:10 ` Edward Adam Davis
2024-12-25 7:25 ` syzbot
2024-12-26 3:43 ` [syzbot] syzbot
2025-07-04 9:39 ` [syzbot] [bluetooth?] KASAN: slab-use-after-free Read in force_devcd_write syzbot
2025-07-04 13:51 ` Hillf Danton
2025-07-04 14:08 ` syzbot
2025-07-04 14:29 ` Hillf Danton
2025-07-04 14:46 ` syzbot
2025-07-04 14:52 ` Hillf Danton
2025-07-04 15:16 ` syzbot [this message]
[not found] <D6LBL8ROHULS.TMYHX3Z1WN0R@getstate.dev>
2024-12-26 4:03 ` 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=6867f034.a70a0220.29cf51.0020.GAE@google.com \
--to=syzbot+bc71245e56f06e3127b7@syzkaller.appspotmail.com \
--cc=hdanton@sina.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