All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+ffba8e636870dac0e0c0@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?] WARNING in iguanair_probe/usb_submit_urb (2)
Date: Sat, 23 Nov 2024 22:15:02 -0800	[thread overview]
Message-ID: <6742c466.050a0220.1cc393.0035.GAE@google.com> (raw)
In-Reply-To: <66f5cc9a.050a0220.46d20.0004.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=135d0530580000
start commit:   43fb83c17ba2 Merge tag 'soc-arm-6.13' of git://git.kernel...
git tree:       upstream
final oops:     https://syzkaller.appspot.com/x/report.txt?x=10dd0530580000
console output: https://syzkaller.appspot.com/x/log.txt?x=175d0530580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=58b000b917043826
dashboard link: https://syzkaller.appspot.com/bug?extid=ffba8e636870dac0e0c0
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=12515930580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=11ca8ec0580000

Reported-by: syzbot+ffba8e636870dac0e0c0@syzkaller.appspotmail.com
Fixes: b3e40fc85735 ("USB: usb_parse_endpoint: ignore reserved bits")

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

      parent reply	other threads:[~2024-11-24  6:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-26 21:05 [syzbot] [media?] WARNING in iguanair_probe/usb_submit_urb (2) syzbot
2024-11-21 17:55 ` syzbot
2024-11-25 14:27   ` Oliver Neukum
2024-11-25 16:00     ` syzbot
2024-11-24  6:15 ` 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=6742c466.050a0220.1cc393.0035.GAE@google.com \
    --to=syzbot+ffba8e636870dac0e0c0@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.