From: syzbot <syzbot+ce77725b89b7bd52425c@syzkaller.appspotmail.com>
To: gregkh@linuxfoundation.org, johan@kernel.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
stern@rowland.harvard.edu, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [usb?] WARNING in usbtmc_ioctl/usb_submit_urb (2)
Date: Tue, 02 May 2023 15:35:21 -0700 [thread overview]
Message-ID: <000000000000fd74ec05fabd8d49@google.com> (raw)
In-Reply-To: <000000000000716a3705f9adb8ee@google.com>
syzbot has bisected this issue to:
commit 5cc59c418fde9d02859996707b9d5dfd2941c50b
Author: Alan Stern <stern@rowland.harvard.edu>
Date: Sat May 22 02:16:23 2021 +0000
USB: core: WARN if pipe direction != setup packet direction
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=140bee54280000
start commit: 58390c8ce1bd Merge tag 'iommu-updates-v6.4' of git://git.k..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=160bee54280000
console output: https://syzkaller.appspot.com/x/log.txt?x=120bee54280000
kernel config: https://syzkaller.appspot.com/x/.config?x=d56ffc213bf6bf4a
dashboard link: https://syzkaller.appspot.com/bug?extid=ce77725b89b7bd52425c
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15027ef7c80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16d7550c280000
Reported-by: syzbot+ce77725b89b7bd52425c@syzkaller.appspotmail.com
Fixes: 5cc59c418fde ("USB: core: WARN if pipe direction != setup packet direction")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-05-02 22:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 10:16 [syzbot] [usb?] WARNING in usbtmc_ioctl/usb_submit_urb (2) syzbot
2023-05-01 11:59 ` syzbot
2023-05-01 15:19 ` Alan Stern
2023-05-01 15:42 ` syzbot
2023-05-01 18:22 ` [PATCH] USB: usbtmc: Fix direction for 0-length ioctl control messages Alan Stern
2023-05-02 22:35 ` 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=000000000000fd74ec05fabd8d49@google.com \
--to=syzbot+ce77725b89b7bd52425c@syzkaller.appspotmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.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).