From: syzbot <syzbot+2a0e7abd24f1eb90ce25@syzkaller.appspotmail.com>
To: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, mailhol.vincent@wanadoo.fr,
mkl@pengutronix.de, syzkaller-bugs@googlegroups.com
Subject: [syzbot] WARNING in __usbnet_read_cmd/usb_submit_urb
Date: Fri, 06 Jan 2023 06:52:45 -0800 [thread overview]
Message-ID: <00000000000008f1d405f1999228@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 1b929c02afd3 Linux 6.2-rc1
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
console output: https://syzkaller.appspot.com/x/log.txt?x=128acc94480000
kernel config: https://syzkaller.appspot.com/x/.config?x=19062640e84d2e8f
dashboard link: https://syzkaller.appspot.com/bug?extid=2a0e7abd24f1eb90ce25
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/22dc9b4a71a2/disk-1b929c02.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/3a88668bf3ce/vmlinux-1b929c02.xz
kernel image: https://storage.googleapis.com/syzbot-assets/3ff0c2e45492/bzImage-1b929c02.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+2a0e7abd24f1eb90ce25@syzkaller.appspotmail.com
------------[ cut here ]------------
usb 3-1: BOGUS control dir, pipe 80003d80 doesn't match bRequestType c0
WARNING: CPU: 1 PID: 2386 at drivers/usb/core/urb.c:411 usb_submit_urb+0x14a3/0x1880 drivers/usb/core/urb.c:411
Modules linked in:
CPU: 1 PID: 2386 Comm: dhcpcd Not tainted 6.2.0-rc1-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
RIP: 0010:usb_submit_urb+0x14a3/0x1880 drivers/usb/core/urb.c:411
Code: 7c 24 40 e8 8f af 8b fd 48 8b 7c 24 40 e8 e5 2c 19 ff 45 89 e8 44 89 f1 4c 89 e2 48 89 c6 48 c7 c7 00 df aa 86 e8 5b e6 15 02 <0f> 0b e9 9f ee ff ff e8 61 af 8b fd 0f b6 1d 89 5f 18 05 31 ff 41
RSP: 0018:ffffc9000147f598 EFLAGS: 00010286
RAX: 0000000000000000 RBX: ffff888118cdc058 RCX: 0000000000000000
RDX: ffff888116045400 RSI: ffffffff812d3e48 RDI: fffff5200028fea5
RBP: ffff888108e1cf78 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: ffff88810dcc37a8
R13: 00000000000000c0 R14: 0000000080003d80 R15: ffff88810b3e5600
FS: 00007f22d5f1d740(0000) GS:ffff8881f6900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f54a3e45440 CR3: 0000000112062000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
usb_start_wait_urb+0x101/0x4b0 drivers/usb/core/message.c:58
usb_internal_control_msg drivers/usb/core/message.c:102 [inline]
usb_control_msg+0x31c/0x4a0 drivers/usb/core/message.c:153
__usbnet_read_cmd+0xb9/0x390 drivers/net/usb/usbnet.c:2010
usbnet_read_cmd+0x92/0xf0 drivers/net/usb/usbnet.c:2068
pl_vendor_req drivers/net/usb/plusb.c:60 [inline]
pl_set_QuickLink_features drivers/net/usb/plusb.c:75 [inline]
pl_reset+0x2b/0xf0 drivers/net/usb/plusb.c:85
usbnet_open+0xc8/0x5d0 drivers/net/usb/usbnet.c:889
__dev_open+0x297/0x4d0 net/core/dev.c:1417
__dev_change_flags+0x583/0x750 net/core/dev.c:8530
dev_change_flags+0x93/0x170 net/core/dev.c:8602
devinet_ioctl+0x1601/0x1ce0 net/ipv4/devinet.c:1147
inet_ioctl+0x1e6/0x320 net/ipv4/af_inet.c:979
sock_do_ioctl+0xcc/0x230 net/socket.c:1169
sock_ioctl+0x2f1/0x640 net/socket.c:1286
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:870 [inline]
__se_sys_ioctl fs/ioctl.c:856 [inline]
__x64_sys_ioctl+0x193/0x200 fs/ioctl.c:856
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f22d600b0e7
Code: 3c 1c e8 1c ff ff ff 85 c0 79 87 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 61 9d 0c 00 f7 d8 64 89 01 48
RSP: 002b:00007ffc78c609f8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f22d5f1d6c8 RCX: 00007f22d600b0e7
RDX: 00007ffc78c70be8 RSI: 0000000000008914 RDI: 0000000000000005
RBP: 00007ffc78c80d98 R08: 00007ffc78c70ba8 R09: 00007ffc78c70b58
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffc78c70be8 R14: 0000000000000028 R15: 0000000000008914
</TASK>
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
next reply other threads:[~2023-01-06 14:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 14:52 syzbot [this message]
2023-01-06 17:33 ` [syzbot] WARNING in __usbnet_read_cmd/usb_submit_urb Alan Stern
2023-02-02 9:06 ` syzbot
2023-02-02 20:49 ` Alan Stern
2023-02-02 21:16 ` syzbot
2023-02-03 19:32 ` [PATCH] net: USB: Fix wrong-direction WARNING in plusb.c Alan Stern
2023-02-06 10:10 ` patchwork-bot+netdevbpf
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=00000000000008f1d405f1999228@google.com \
--to=syzbot+2a0e7abd24f1eb90ce25@syzkaller.appspotmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mailhol.vincent@wanadoo.fr \
--cc=mkl@pengutronix.de \
--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