From: syzbot <syzbot+5127feb52165f8ab165b@syzkaller.appspotmail.com>
To: davem@davemloft.net, edumazet@google.com,
gregkh@linuxfoundation.org, kuba@kernel.org,
linux-kernel@vger.kernel.org, marcello.bauer@9elements.com,
netdev@vger.kernel.org, pabeni@redhat.com,
stern@rowland.harvard.edu, sylv@sylv.io,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] INFO: rcu detected stall in neigh_timer_handler (8)
Date: Thu, 12 Sep 2024 19:47:05 -0700 [thread overview]
Message-ID: <00000000000011b0080621f73dd2@google.com> (raw)
In-Reply-To: <0000000000005348f9061ab8df82@google.com>
syzbot suspects this issue was fixed by commit:
commit 22f00812862564b314784167a89f27b444f82a46
Author: Alan Stern <stern@rowland.harvard.edu>
Date: Fri Jun 14 01:30:43 2024 +0000
USB: class: cdc-wdm: Fix CPU lockup caused by excessive log messages
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17eae0a9980000
start commit: dc772f8237f9 Merge tag 'mm-hotfixes-stable-2024-06-07-15-2..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=333ebe38d43c42e2
dashboard link: https://syzkaller.appspot.com/bug?extid=5127feb52165f8ab165b
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17398dce980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=112fa5ac980000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: USB: class: cdc-wdm: Fix CPU lockup caused by excessive log messages
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-09-13 2:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 22:26 [syzbot] [net?] INFO: rcu detected stall in neigh_timer_handler (8) syzbot
2024-09-13 2:47 ` syzbot [this message]
2024-09-13 9:08 ` Eric Dumazet
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=00000000000011b0080621f73dd2@google.com \
--to=syzbot+5127feb52165f8ab165b@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcello.bauer@9elements.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox