linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+ec5f884c4a135aa0dbb9@syzkaller.appspotmail.com>
To: andreyknvl@google.com, balbi@kernel.org,
	benjamin.tissoires@redhat.com, fweisbec@gmail.com,
	gregkh@linuxfoundation.org, jikos@kernel.org,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-usb@vger.kernel.org, mingo@kernel.org,
	quic_mrana@quicinc.com, rafael@kernel.org,
	stern@rowland.harvard.edu, syzkaller-bugs@googlegroups.com,
	tglx@linutronix.de
Subject: Re: [syzbot] INFO: rcu detected stall in hub_event
Date: Sat, 30 Jul 2022 03:27:10 -0700	[thread overview]
Message-ID: <0000000000009bd74d05e5033509@google.com> (raw)
In-Reply-To: <000000000000109c040597dc5843@google.com>

syzbot has bisected this issue to:

commit 859bdc359567f5fa8e8dc780d7b5e53ea43d9ce9
Author: Mayank Rana <quic_mrana@quicinc.com>
Date:   Wed May 18 18:12:52 2022 +0000

    usb: dwc3: core: Add error log when core soft reset failed

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=144812f2080000
start commit:   6e2c0490769e Merge tag 'drm-fixes-2022-07-29' of git://ano..
git tree:       upstream
final oops:     https://syzkaller.appspot.com/x/report.txt?x=164812f2080000
console output: https://syzkaller.appspot.com/x/log.txt?x=124812f2080000
kernel config:  https://syzkaller.appspot.com/x/.config?x=26034e6fe0075dad
dashboard link: https://syzkaller.appspot.com/bug?extid=ec5f884c4a135aa0dbb9
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=119bc436080000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=16c3c0f2080000

Reported-by: syzbot+ec5f884c4a135aa0dbb9@syzkaller.appspotmail.com
Fixes: 859bdc359567 ("usb: dwc3: core: Add error log when core soft reset failed")

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

      parent reply	other threads:[~2022-07-30 10:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-21 14:45 INFO: rcu detected stall in hub_event syzbot
2019-11-22 16:51 ` Alan Stern
2019-11-22 21:31   ` Andrey Konovalov
2019-11-25 17:30     ` Alan Stern
2019-12-09 18:26       ` Alan Stern
2019-12-10 21:26         ` [PATCH] HID: Fix slab-out-of-bounds read in hid_field_extract Alan Stern
2019-12-11 14:18           ` Jiri Kosina
2019-12-11 15:10             ` Alan Stern
2019-12-13  8:44               ` Jiri Kosina
2024-04-08 16:55         ` INFO: rcu detected stall in hub_event Alan Stern
2019-11-23 20:20   ` syzbot
2019-11-24 16:17     ` Alan Stern
2019-11-25  9:38       ` syzbot
2019-11-25 21:24         ` Alan Stern
2019-11-26  7:48           ` Jiri Kosina
2019-11-26 15:18             ` Alan Stern
2019-11-26 20:21           ` syzbot
2022-07-30 10:27 ` 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=0000000000009bd74d05e5033509@google.com \
    --to=syzbot+ec5f884c4a135aa0dbb9@syzkaller.appspotmail.com \
    --cc=andreyknvl@google.com \
    --cc=balbi@kernel.org \
    --cc=benjamin.tissoires@redhat.com \
    --cc=fweisbec@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=quic_mrana@quicinc.com \
    --cc=rafael@kernel.org \
    --cc=stern@rowland.harvard.edu \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tglx@linutronix.de \
    /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).