From: syzbot <syzbot+e3ae1e7f4b88f3e696f5@syzkaller.appspotmail.com>
To: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, linux-usb@vger.kernel.org,
mchehab@kernel.org, oneukum@suse.com, sean@mess.org,
stern@rowland.harvard.edu, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [media?] [usb?] WARNING in iguanair_get_features/usb_submit_urb
Date: Wed, 20 Nov 2024 19:06:02 -0800 [thread overview]
Message-ID: <673ea39a.050a0220.363a1b.0083.GAE@google.com> (raw)
In-Reply-To: <673de7f9.050a0220.363a1b.0011.GAE@google.com>
syzbot has bisected this issue to:
commit b3e40fc85735b787ce65909619fcd173107113c2
Author: Oliver Neukum <oneukum@suse.com>
Date: Thu May 2 11:51:40 2024 +0000
USB: usb_parse_endpoint: ignore reserved bits
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13907ae8580000
start commit: f868cd251776 Merge tag 'drm-fixes-2024-11-16' of https://g..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=10507ae8580000
console output: https://syzkaller.appspot.com/x/log.txt?x=17907ae8580000
kernel config: https://syzkaller.appspot.com/x/.config?x=d2aeec8c0b2e420c
dashboard link: https://syzkaller.appspot.com/bug?extid=e3ae1e7f4b88f3e696f5
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10edf1a7980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10d892c0580000
Reported-by: syzbot+e3ae1e7f4b88f3e696f5@syzkaller.appspotmail.com
Fixes: b3e40fc85735 ("USB: usb_parse_endpoint: ignore reserved bits")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-11-21 3:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-20 13:45 [syzbot] [media?] [usb?] WARNING in iguanair_get_features/usb_submit_urb syzbot
2024-11-21 3:06 ` syzbot [this message]
2025-02-15 19:59 ` [syzbot] [media?] " syzbot
2025-02-20 12:58 ` [syzbot] [media?] [usb?] " Nikita Zhandarovich
2025-02-20 12:58 ` 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=673ea39a.050a0220.363a1b.0083.GAE@google.com \
--to=syzbot+e3ae1e7f4b88f3e696f5@syzkaller.appspotmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=oneukum@suse.com \
--cc=sean@mess.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