From: syzbot <syzbot+d6b0b0ea0781c14b2ecf@syzkaller.appspotmail.com>
To: arnd@arndb.de, christian.brauner@ubuntu.com,
gregkh@linuxfoundation.org, hdanton@sina.com,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
mpe@ellerman.id.au, oleg@redhat.com,
syzkaller-bugs@googlegroups.com, web@syzkaller.appspotmail.com
Subject: Re: [syzbot] [usb?] KASAN: slab-use-after-free Write in usb_anchor_suspend_wakeups
Date: Sat, 12 Aug 2023 02:51:30 -0700 [thread overview]
Message-ID: <00000000000014678c0602b6c643@google.com> (raw)
In-Reply-To: <0000000000007c27e105faa4aa99@google.com>
syzbot has bisected this issue to:
commit 9b4feb630e8e9801603f3cab3a36369e3c1cf88d
Author: Christian Brauner <christian.brauner@ubuntu.com>
Date: Fri May 24 09:31:44 2019 +0000
arch: wire-up close_range()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1323329ba80000
start commit: 89d77f71f493 Merge tag 'riscv-for-linus-6.4-mw1' of git://..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=10a3329ba80000
console output: https://syzkaller.appspot.com/x/log.txt?x=1723329ba80000
kernel config: https://syzkaller.appspot.com/x/.config?x=d963e7536cbe545e
dashboard link: https://syzkaller.appspot.com/bug?extid=d6b0b0ea0781c14b2ecf
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11471b84280000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10b98e2c280000
Reported-by: syzbot+d6b0b0ea0781c14b2ecf@syzkaller.appspotmail.com
Fixes: 9b4feb630e8e ("arch: wire-up close_range()")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-08-12 9:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-01 16:53 [syzbot] [usb?] KASAN: slab-use-after-free Write in usb_anchor_suspend_wakeups syzbot
2023-08-12 9:51 ` syzbot [this message]
2023-08-12 15:56 ` Alan Stern
2023-08-17 12:16 ` Oliver Neukum
2023-08-17 14:12 ` Alan Stern
[not found] <20230502040924.3458-1-hdanton@sina.com>
2023-05-02 4:30 ` syzbot
[not found] <20230502070029.3525-1-hdanton@sina.com>
2023-05-02 7:22 ` 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=00000000000014678c0602b6c643@google.com \
--to=syzbot+d6b0b0ea0781c14b2ecf@syzkaller.appspotmail.com \
--cc=arnd@arndb.de \
--cc=christian.brauner@ubuntu.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mpe@ellerman.id.au \
--cc=oleg@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=web@syzkaller.appspotmail.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