From: syzbot <syzbot+1acbadd9f48eeeacda29@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, brauner@kernel.org,
davem@davemloft.net, dvyukov@google.com, elver@google.com,
glider@google.com, gregkh@linuxfoundation.org, hdanton@sina.com,
jhs@mojatatu.com, kasan-dev@googlegroups.com,
keescook@chromium.org, kuba@kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-usb@vger.kernel.org, luyun@kylinos.cn,
netdev@vger.kernel.org, pctammela@mojatatu.com,
rafael@kernel.org, stern@rowland.harvard.edu,
syzkaller-bugs@googlegroups.com, victor@mojatatu.com,
vinicius.gomes@intel.com, viro@zeniv.linux.org.uk,
vladimir.oltean@nxp.com
Subject: Re: [syzbot] [usb?] INFO: rcu detected stall in __run_timer_base
Date: Wed, 31 Jul 2024 04:57:02 -0700 [thread overview]
Message-ID: <000000000000d61bb8061e89caa5@google.com> (raw)
In-Reply-To: <00000000000022a23c061604edb3@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=14f906bd980000
start commit: 89be4025b0db Merge tag '6.10-rc1-smb3-client-fixes' of git..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=b9016f104992d69c
dashboard link: https://syzkaller.appspot.com/bug?extid=1acbadd9f48eeeacda29
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=145ed3fc980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11c1541c980000
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-07-31 11:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-14 2:04 [syzbot] [kasan?] [mm?] INFO: rcu detected stall in __run_timer_base syzbot
2024-04-14 2:53 ` Hillf Danton
2024-04-14 3:26 ` syzbot
2024-05-07 3:32 ` Yun Lu
2024-05-03 8:53 ` [PATCH] net/sched: taprio: fix CPU stuck due to the taprio hrtimer Yun Lu
2024-05-03 9:18 ` Yun Lu
2024-05-03 12:03 ` [syzbot] [kasan?] [mm?] INFO: rcu detected stall in __run_timer_base syzbot
2024-05-03 21:34 ` [PATCH] net/sched: taprio: fix CPU stuck due to the taprio hrtimer Jakub Kicinski
2024-05-03 9:20 ` [syzbot] " syzbot
2024-05-03 19:58 ` [syzbot] [kasan?] [mm?] INFO: rcu detected stall in __run_timer_base syzbot
2024-05-06 2:36 ` fix CPU stuck due to the taprio hrtimer Yun Lu
2024-05-06 2:56 ` [syzbot] [kasan?] [mm?] INFO: rcu detected stall in __run_timer_base syzbot
2024-05-31 11:02 ` Hillf Danton
2024-05-31 18:08 ` syzbot
2024-07-31 11:57 ` syzbot [this message]
2024-07-31 14:08 ` [syzbot] [usb?] " Alan Stern
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=000000000000d61bb8061e89caa5@google.com \
--to=syzbot+1acbadd9f48eeeacda29@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdanton@sina.com \
--cc=jhs@mojatatu.com \
--cc=kasan-dev@googlegroups.com \
--cc=keescook@chromium.org \
--cc=kuba@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-usb@vger.kernel.org \
--cc=luyun@kylinos.cn \
--cc=netdev@vger.kernel.org \
--cc=pctammela@mojatatu.com \
--cc=rafael@kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=syzkaller-bugs@googlegroups.com \
--cc=victor@mojatatu.com \
--cc=vinicius.gomes@intel.com \
--cc=viro@zeniv.linux.org.uk \
--cc=vladimir.oltean@nxp.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.