[syzbot] WARNING in usbtmc_ioctl_request/usb_submit_urb

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: b229b6ca5abb Merge tag 'perf-tools-fixes-for-v6.1-2022-10-..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1111f646880000
kernel config: https://syzkaller.appspot.com/x/.config?x=701f2aae1cb0470e
dashboard link: https://syzkaller.appspot.com/bug?extid=588a3c76a3b2f453a909
compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, 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/d9d974225814/disk-b229b6ca.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a71771368ee9/vmlinux-b229b6ca.xz
kernel image: https://storage.googleapis.com/syzbot-assets/2f6c9e8f9713/bzImage-b229b6ca.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+588a3c...@syzkaller.appspotmail.com

------------[ cut here ]------------
usb 5-1: BOGUS control dir, pipe 80005f80 doesn't match bRequestType ff
WARNING: CPU: 1 PID: 25513 at drivers/usb/core/urb.c:413 usb_submit_urb+0x12f4/0x1920 drivers/usb/core/urb.c:411
Modules linked in:
CPU: 1 PID: 25513 Comm: syz-executor.2 Not tainted 6.1.0-rc2-syzkaller-00105-gb229b6ca5abb #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/11/2022
RIP: 0010:usb_submit_urb+0x12f4/0x1920 drivers/usb/core/urb.c:411
Code: 20 84 c0 0f 85 a3 05 00 00 48 8b 44 24 18 44 0f b6 00 48 c7 c7 20 ff 53 8b 48 8b 74 24 60 48 89 da 89 e9 31 c0 e8 9c ed 38 fb <0f> 0b 4d 89 e6 44 8b 64 24 48 4c 8b 7c 24 58 e9 c5 f2 ff ff 89 d9
RSP: 0018:ffffc90015a67a90 EFLAGS: 00010246
RAX: 47ea9dc414312400 RBX: ffff88807e3da410 RCX: 0000000000040000
RDX: ffffc9000d9ea000 RSI: 0000000000005526 RDI: 0000000000005527
RBP: 0000000080005f80 R08: ffffffff816ced5d R09: fffff52002b4cf0d
R10: fffff52002b4cf0d R11: 1ffff92002b4cf0c R12: dffffc0000000000
R13: ffff8880565d4b00 R14: dffffc0000000000 R15: ffff88806bd570a8
FS: 00007f4059244700(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f96fa5a7110 CR3: 0000000021e2b000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
usb_start_wait_urb+0x10e/0x510 drivers/usb/core/message.c:58
usb_internal_control_msg drivers/usb/core/message.c:102 [inline]
usb_control_msg+0x2a5/0x4b0 drivers/usb/core/message.c:153
usbtmc_ioctl_request+0x421/0x920 drivers/usb/class/usbtmc.c:1954
usbtmc_ioctl+0x63f/0x800 drivers/usb/class/usbtmc.c:2097
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:870 [inline]
__se_sys_ioctl+0xfb/0x170 fs/ioctl.c:856
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x2b/0x70 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f405848b5a9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f4059244168 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f40585ac050 RCX: 00007f405848b5a9
RDX: 0000000020000280 RSI: 00000000c0105b08 RDI: 0000000000000004
RBP: 00007f40584e67b0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffd78225cef R14: 00007f4059244300 R15: 0000000000022000
</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 syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.