From: Alan Stern <stern@rowland.harvard.edu>
To: syzbot <syzbot+b24d736f18a1541ad550@syzkaller.appspotmail.com>
Cc: andreyknvl@google.com, <balbi@kernel.org>,
<chunfeng.yun@mediatek.com>, <gregkh@linuxfoundation.org>,
<linux-kernel@vger.kernel.org>, <linux-usb@vger.kernel.org>,
<syzkaller-bugs@googlegroups.com>
Subject: Re: INFO: rcu detected stall in dummy_timer
Date: Fri, 13 Sep 2019 16:35:57 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44L0.1909131629230.1466-100000@iolanthe.rowland.org> (raw)
In-Reply-To: <0000000000004fb020059274a5ff@google.com>
On Fri, 13 Sep 2019, syzbot wrote:
> syzbot has found a reproducer for the following crash on:
>
> HEAD commit: f0df5c1b usb-fuzzer: main usb gadget fuzzer driver
> git tree: https://github.com/google/kasan.git usb-fuzzer
> console output: https://syzkaller.appspot.com/x/log.txt?x=1146550d600000
> kernel config: https://syzkaller.appspot.com/x/.config?x=5c6633fa4ed00be5
> dashboard link: https://syzkaller.appspot.com/bug?extid=b24d736f18a1541ad550
> compiler: gcc (GCC) 9.0.0 20181231 (experimental)
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11203fa5600000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=162cd335600000
>
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by: syzbot+b24d736f18a1541ad550@syzkaller.appspotmail.com
>
> yurex 3-1:0.101: yurex_interrupt - unknown status received: -71
> yurex 5-1:0.101: yurex_interrupt - unknown status received: -71
> yurex 6-1:0.101: yurex_interrupt - unknown status received: -71
> rcu: INFO: rcu_sched self-detected stall on CPU
Andrey:
This problem may be a result of overloading dummy_timer. The kernel
config you are using has CONFIG_HZ=100, but dummy-hcd needs
CONFIG_HZ=1000 (see the comment on line 1789). That is, lower values
of HZ will occasionally lead to trouble, and this may be an example.
Can you change the config value for HZ and see if the bug still
reproduces?
Alan Stern
next prev parent reply other threads:[~2019-09-13 20:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-09 13:18 INFO: rcu detected stall in dummy_timer syzbot
2019-09-13 19:56 ` syzbot
2019-09-13 20:35 ` Alan Stern [this message]
2019-09-16 15:29 ` Andrey Konovalov
2019-09-16 16:32 ` Alan Stern
2019-09-16 18:59 ` Greg Kroah-Hartman
2019-09-16 19:48 ` Alan Stern
2019-09-18 11:22 ` Andrey Konovalov
2019-09-18 14:16 ` Alan Stern
2019-09-16 19:53 ` Alan Stern
2019-09-16 20:13 ` syzbot
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=Pine.LNX.4.44L0.1909131629230.1466-100000@iolanthe.rowland.org \
--to=stern@rowland.harvard.edu \
--cc=andreyknvl@google.com \
--cc=balbi@kernel.org \
--cc=chunfeng.yun@mediatek.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=syzbot+b24d736f18a1541ad550@syzkaller.appspotmail.com \
--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;
as well as URLs for NNTP newsgroup(s).