From: syzbot <syzbot+1e6e0b916b211bee1bd6@syzkaller.appspotmail.com>
To: axboe@kernel.dk, gregkh@linuxfoundation.org, hdanton@sina.com,
justin@coraid.com, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
loberman@redhat.com, marcello.bauer@9elements.com,
rafael@kernel.org, stern@rowland.harvard.edu, sylv@sylv.io,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [block?] [usb?] INFO: rcu detected stall in aoecmd_cfg (2)
Date: Sun, 12 May 2024 04:05:03 -0700 [thread overview]
Message-ID: <0000000000009966ab06183fbd83@google.com> (raw)
In-Reply-To: <0000000000008de5720617f64aae@google.com>
syzbot has bisected this issue to:
commit a7f3813e589fd8e2834720829a47b5eb914a9afe
Author: Marcello Sylvester Bauer <sylv@sylv.io>
Date: Thu Apr 11 14:51:28 2024 +0000
usb: gadget: dummy_hcd: Switch to hrtimer transfer scheduler
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12415cd0980000
start commit: 9221b2819b8a Add linux-next specific files for 20240503
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=11415cd0980000
console output: https://syzkaller.appspot.com/x/log.txt?x=16415cd0980000
kernel config: https://syzkaller.appspot.com/x/.config?x=8ab537f51a6a0d98
dashboard link: https://syzkaller.appspot.com/bug?extid=1e6e0b916b211bee1bd6
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15661898980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=161a5d1f180000
Reported-by: syzbot+1e6e0b916b211bee1bd6@syzkaller.appspotmail.com
Fixes: a7f3813e589f ("usb: gadget: dummy_hcd: Switch to hrtimer transfer scheduler")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-05-12 11:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 19:27 [syzbot] [block?] [usb?] INFO: rcu detected stall in aoecmd_cfg (2) syzbot
2024-05-08 19:33 ` Laurence Oberman
2024-05-08 23:40 ` Hillf Danton
2024-05-09 0:24 ` syzbot
2024-05-12 11:05 ` syzbot [this message]
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=0000000000009966ab06183fbd83@google.com \
--to=syzbot+1e6e0b916b211bee1bd6@syzkaller.appspotmail.com \
--cc=axboe@kernel.dk \
--cc=gregkh@linuxfoundation.org \
--cc=hdanton@sina.com \
--cc=justin@coraid.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=loberman@redhat.com \
--cc=marcello.bauer@9elements.com \
--cc=rafael@kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=sylv@sylv.io \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.