From: syzbot <syzbot+b064b5599f18f7ebb1e1@syzkaller.appspotmail.com>
To: dmitry.torokhov@gmail.com, gregkh@linuxfoundation.org,
javier.carrasco@wolfvision.net, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
mukattreyee@gmail.com, oneukum@suse.com, rydberg@bitmath.org,
stern@rowland.harvard.edu, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [usb?] [input?] WARNING in bcm5974_start_traffic/usb_submit_urb (2)
Date: Fri, 12 Sep 2025 22:52:02 -0700 [thread overview]
Message-ID: <68c50682.050a0220.2ff435.036c.GAE@google.com> (raw)
In-Reply-To: <0000000000008acb1e061618e68e@google.com>
syzbot suspects this issue was fixed by commit:
commit 503bbde34cc3dd2acd231f277ba70c3f9ed22e59
Author: Oliver Neukum <oneukum@suse.com>
Date: Thu Jun 12 12:20:25 2025 +0000
usb: core: usb_submit_urb: downgrade type check
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16c6eb62580000
start commit: e8ab83e34bdc Merge tag 'arm64-fixes' of git://git.kernel.o..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=a9a25b7a36123454
dashboard link: https://syzkaller.appspot.com/bug?extid=b064b5599f18f7ebb1e1
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1514f0f4580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11699a70580000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: usb: core: usb_submit_urb: downgrade type check
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-09-13 5:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 1:54 [syzbot] [input?] WARNING in bcm5974_start_traffic/usb_submit_urb (2) syzbot
2024-04-15 6:32 ` Javier Carrasco
2025-09-13 5:52 ` 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=68c50682.050a0220.2ff435.036c.GAE@google.com \
--to=syzbot+b064b5599f18f7ebb1e1@syzkaller.appspotmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=javier.carrasco@wolfvision.net \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mukattreyee@gmail.com \
--cc=oneukum@suse.com \
--cc=rydberg@bitmath.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).