From: syzbot <syzbot+193dae06b6680599fbab@syzkaller.appspotmail.com>
To: davem@davemloft.net, eadavis@qq.com, edumazet@google.com,
idosch@nvidia.com, jiri@nvidia.com, kuba@kernel.org,
leon@kernel.org, linux-kernel@vger.kernel.org,
linux-rdma@vger.kernel.org, linux-usb@vger.kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com, petrm@nvidia.com,
saeedm@nvidia.com, syzkaller-bugs@googlegroups.com,
tariqt@nvidia.com
Subject: Re: [syzbot] [net?] [usb?] INFO: rcu detected stall in nsim_dev_trap_report_work (2)
Date: Thu, 02 Nov 2023 03:55:03 -0700 [thread overview]
Message-ID: <0000000000004d3e3d0609293891@google.com> (raw)
In-Reply-To: <0000000000009ee19a0609135c34@google.com>
syzbot has bisected this issue to:
commit 644a66c60f02f302d82c3008ae2ffe67cf495383
Author: Jiri Pirko <jiri@nvidia.com>
Date: Fri Jul 29 07:10:36 2022 +0000
net: devlink: convert reload command to take implicit devlink->lock
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13c76cf3680000
start commit: 66f1e1ea3548 Add linux-next specific files for 20231027
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=10276cf3680000
console output: https://syzkaller.appspot.com/x/log.txt?x=17c76cf3680000
kernel config: https://syzkaller.appspot.com/x/.config?x=2911330219149de4
dashboard link: https://syzkaller.appspot.com/bug?extid=193dae06b6680599fbab
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10b8e977680000
Reported-by: syzbot+193dae06b6680599fbab@syzkaller.appspotmail.com
Fixes: 644a66c60f02 ("net: devlink: convert reload command to take implicit devlink->lock")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-11-02 10:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 8:50 [syzbot] [net?] [usb?] INFO: rcu detected stall in nsim_dev_trap_report_work (2) syzbot
2023-11-02 10:55 ` 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=0000000000004d3e3d0609293891@google.com \
--to=syzbot+193dae06b6680599fbab@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=eadavis@qq.com \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=saeedm@nvidia.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tariqt@nvidia.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;
as well as URLs for NNTP newsgroup(s).