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: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00000000000022a23c061604edb3@google.com>
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 19:58 ` [syzbot] [kasan?] [mm?] INFO: rcu detected stall in __run_timer_base 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$(echo .)appspotmail.com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=brauner@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=dvyukov@google$(echo .)com \
--cc=elver@google$(echo .)com \
--cc=glider@google$(echo .)com \
--cc=gregkh@linuxfoundation$(echo .)org \
--cc=hdanton@sina$(echo .)com \
--cc=jhs@mojatatu$(echo .)com \
--cc=kasan-dev@googlegroups$(echo .)com \
--cc=keescook@chromium$(echo .)org \
--cc=kuba@kernel$(echo .)org \
--cc=linux-fsdevel@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-mm@kvack$(echo .)org \
--cc=linux-usb@vger$(echo .)kernel.org \
--cc=luyun@kylinos$(echo .)cn \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pctammela@mojatatu$(echo .)com \
--cc=rafael@kernel$(echo .)org \
--cc=stern@rowland$(echo .)harvard.edu \
--cc=syzkaller-bugs@googlegroups$(echo .)com \
--cc=victor@mojatatu$(echo .)com \
--cc=vinicius.gomes@intel$(echo .)com \
--cc=viro@zeniv$(echo .)linux.org.uk \
--cc=vladimir.oltean@nxp$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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