From: syzbot <syzbot+92340f7b2b4789907fdb@syzkaller.appspotmail.com>
To: andreyknvl@google.com, ebiggers@kernel.org,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, rafael@kernel.org,
stern@rowland.harvard.edu, syzkaller-bugs@googlegroups.com
Subject: Re: WARNING in input_register_device
Date: Sun, 17 Jan 2021 17:41:12 -0800 [thread overview]
Message-ID: <00000000000024a0ec05b922d186@google.com> (raw)
In-Reply-To: <000000000000872b5405b36f8e31@google.com>
syzbot suspects this issue was fixed by commit:
commit c318840fb2a42ce25febc95c4c19357acf1ae5ca
Author: Alan Stern <stern@rowland.harvard.edu>
Date: Wed Dec 30 16:20:44 2020 +0000
USB: Gadget: dummy-hcd: Fix shift-out-of-bounds bug
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10be15d7500000
start commit: 2c85ebc5 Linux 5.10
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=8aff533d6c635e6
dashboard link: https://syzkaller.appspot.com/bug?extid=92340f7b2b4789907fdb
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1763d433500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13ef12cb500000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: USB: Gadget: dummy-hcd: Fix shift-out-of-bounds bug
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2021-01-18 1:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 12:43 WARNING in input_register_device syzbot
2020-11-06 14:03 ` Greg KH
2020-11-06 17:01 ` Alan Stern
2020-11-06 17:03 ` Eric Biggers
2020-11-07 8:22 ` Greg KH
2021-01-18 1:41 ` 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=00000000000024a0ec05b922d186@google.com \
--to=syzbot+92340f7b2b4789907fdb@syzkaller.appspotmail.com \
--cc=andreyknvl@google.com \
--cc=ebiggers@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=stern@rowland.harvard.edu \
--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).