From: syzbot <syzbot+3e563d99e70973c0755c@syzkaller.appspotmail.com>
To: linux-kernel.vger.kernel.org@gmail.com,
linux-kernel@vger.kernel.org, marcus.yu.56@gmail.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [usb?] KASAN: invalid-free in dev_free
Date: Tue, 29 Oct 2024 23:56:02 -0700 [thread overview]
Message-ID: <6721d882.050a0220.3c8d68.00af.GAE@google.com> (raw)
In-Reply-To: <ZyHUlDvkl0Umhs-y@gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+3e563d99e70973c0755c@syzkaller.appspotmail.com
Tested-by: syzbot+3e563d99e70973c0755c@syzkaller.appspotmail.com
Tested on:
commit: c67e9601 usb: core: use sysfs_emit() instead of sprint..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
console output: https://syzkaller.appspot.com/x/log.txt?x=1758e2a7980000
kernel config: https://syzkaller.appspot.com/x/.config?x=4a2bb21f91d75c65
dashboard link: https://syzkaller.appspot.com/bug?extid=3e563d99e70973c0755c
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=11056540580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2024-10-30 6:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ZyHUlDvkl0Umhs-y@gmail.com>
2024-10-30 6:56 ` syzbot [this message]
2024-11-06 4:43 [PATCH] usb: raw_gadget: Add debug logs to a troubleshoot a double-free bug in raw_release Chang Yu
2024-11-06 5:08 ` [syzbot] [usb?] KASAN: invalid-free in dev_free syzbot
[not found] <ZyahFyrgAUtMODEq@gmail.com>
2024-11-02 22:28 ` syzbot
-- strict thread matches above, loose matches on Subject: below --
2024-08-16 20:25 syzbot
2024-09-16 1:24 ` syzbot
2024-11-01 23:26 ` Andrey Konovalov
2024-11-01 23:44 ` Chang Yu
2024-11-24 20:29 ` Andrey Konovalov
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=6721d882.050a0220.3c8d68.00af.GAE@google.com \
--to=syzbot+3e563d99e70973c0755c@syzkaller.appspotmail.com \
--cc=linux-kernel.vger.kernel.org@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcus.yu.56@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