From: syzbot <syzbot+1db88381b64aaa929ef6@syzkaller.appspotmail.com>
To: andreyknvl@google.com, benjamin.tissoires@redhat.com,
gregkh@linuxfoundation.org, hdanton@sina.com,
herbert@gondor.apana.org.au, jikos@kernel.org, jkosina@suse.cz,
linux-crypto@vger.kernel.org, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
mpm@selenic.com, mst@redhat.com, rafael@kernel.org,
rikard.falkeborn@gmail.com, sammko@sammserver.com,
syzkaller-bugs@googlegroups.com
Subject: Re: INFO: task hung in virtio_cleanup
Date: Fri, 26 Feb 2021 09:40:05 -0800 [thread overview]
Message-ID: <0000000000002ce0d905bc40c2df@google.com> (raw)
In-Reply-To: <000000000000b2d35705b7f31599@google.com>
syzbot has bisected this issue to:
commit 77a36a3ab4ff17fad23831192e3694a3c5a1750d
Author: Samuel Čavoj <sammko@sammserver.com>
Date: Fri Mar 13 02:12:38 2020 +0000
HID: Add driver fixing Glorious PC Gaming Race mouse report descriptor
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=129959ccd00000
start commit: f40ddce8 Linux 5.11
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=119959ccd00000
console output: https://syzkaller.appspot.com/x/log.txt?x=169959ccd00000
kernel config: https://syzkaller.appspot.com/x/.config?x=e53d04227c52a0df
dashboard link: https://syzkaller.appspot.com/bug?extid=1db88381b64aaa929ef6
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12277728d00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1135e198d00000
Reported-by: syzbot+1db88381b64aaa929ef6@syzkaller.appspotmail.com
Fixes: 77a36a3ab4ff ("HID: Add driver fixing Glorious PC Gaming Race mouse report descriptor")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
parent reply other threads:[~2021-02-26 17:41 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <000000000000b2d35705b7f31599@google.com>]
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=0000000000002ce0d905bc40c2df@google.com \
--to=syzbot+1db88381b64aaa929ef6@syzkaller.appspotmail.com \
--cc=andreyknvl@google.com \
--cc=benjamin.tissoires@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdanton@sina.com \
--cc=herbert@gondor.apana.org.au \
--cc=jikos@kernel.org \
--cc=jkosina@suse.cz \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=mst@redhat.com \
--cc=rafael@kernel.org \
--cc=rikard.falkeborn@gmail.com \
--cc=sammko@sammserver.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).