From: syzbot <syzbot+d693c07c6f647e0388d3@syzkaller.appspotmail.com>
To: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
netdev@vger.kernel.org, oneukum@suse.com, pabeni@redhat.com,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] [usb?] WARNING in usbnet_start_xmit/usb_submit_urb (2)
Date: Sun, 17 Mar 2024 07:43:21 -0700 [thread overview]
Message-ID: <000000000000346bbd0613dc4396@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: d99e42ce6b83 Merge tag 'usb-serial-6.9-rc1' of https://git..
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=111aa901180000
kernel config: https://syzkaller.appspot.com/x/.config?x=dd8c589043bc2b49
dashboard link: https://syzkaller.appspot.com/bug?extid=d693c07c6f647e0388d3
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1248049e180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14bbf9fa180000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/69f01028417d/disk-d99e42ce.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/b4624715c637/vmlinux-d99e42ce.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0a940dfca61e/bzImage-d99e42ce.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+d693c07c6f647e0388d3@syzkaller.appspotmail.com
------------[ cut here ]------------
usb 3-1: BOGUS urb xfer, pipe 3 != type 1
WARNING: CPU: 1 PID: 2507 at drivers/usb/core/urb.c:503 usb_submit_urb+0xe47/0x1730 drivers/usb/core/urb.c:503
Modules linked in:
CPU: 1 PID: 2507 Comm: kworker/1:5 Not tainted 6.8.0-rc6-syzkaller-00189-gd99e42ce6b83 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024
Workqueue: mld mld_ifc_work
RIP: 0010:usb_submit_urb+0xe47/0x1730 drivers/usb/core/urb.c:503
Code: 84 3c 02 00 00 e8 59 ba 43 fd 4c 89 ef e8 61 16 07 ff 45 89 e0 89 e9 4c 89 f2 48 89 c6 48 c7 c7 a0 37 f0 86 e8 0a 46 0d fd 90 <0f> 0b 90 90 e9 ed f8 ff ff e8 2b ba 43 fd 49 81 c4 b8 05 00 00 e9
RSP: 0018:ffffc9000157f308 EFLAGS: 00010082
RAX: 0000000000000000 RBX: ffff8881123c3000 RCX: ffffffff81177339
RDX: ffff888115e8d700 RSI: ffffffff81177346 RDI: 0000000000000001
RBP: 0000000000000003 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000000001
R13: ffff888120fb00a8 R14: ffff888103eeb240 R15: ffff8881123c307c
FS: 0000000000000000(0000) GS:ffff8881f6700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f4293372238 CR3: 00000001227c5000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
usbnet_start_xmit+0x693/0x2440 drivers/net/usb/usbnet.c:1453
__netdev_start_xmit include/linux/netdevice.h:4989 [inline]
netdev_start_xmit include/linux/netdevice.h:5003 [inline]
xmit_one net/core/dev.c:3547 [inline]
dev_hard_start_xmit+0x137/0x6d0 net/core/dev.c:3563
sch_direct_xmit+0x18e/0x830 net/sched/sch_generic.c:342
__dev_xmit_skb net/core/dev.c:3776 [inline]
__dev_queue_xmit+0x12b2/0x3ed0 net/core/dev.c:4317
dev_queue_xmit include/linux/netdevice.h:3171 [inline]
neigh_resolve_output net/core/neighbour.c:1563 [inline]
neigh_resolve_output+0x582/0x8f0 net/core/neighbour.c:1543
neigh_output include/net/neighbour.h:542 [inline]
ip6_finish_output2+0xad9/0x22b0 net/ipv6/ip6_output.c:137
__ip6_finish_output+0x3a5/0xbc0 net/ipv6/ip6_output.c:211
ip6_finish_output net/ipv6/ip6_output.c:222 [inline]
NF_HOOK_COND include/linux/netfilter.h:303 [inline]
ip6_output+0x23a/0x8c0 net/ipv6/ip6_output.c:243
dst_output include/net/dst.h:451 [inline]
NF_HOOK.constprop.0+0xff/0x570 include/linux/netfilter.h:314
mld_sendpack+0x6e6/0xd10 net/ipv6/mcast.c:1818
mld_send_cr net/ipv6/mcast.c:2119 [inline]
mld_ifc_work+0x756/0xcd0 net/ipv6/mcast.c:2650
process_one_work+0x886/0x15d0 kernel/workqueue.c:2633
process_scheduled_works kernel/workqueue.c:2706 [inline]
worker_thread+0x8b9/0x1290 kernel/workqueue.c:2787
kthread+0x2c6/0x3a0 kernel/kthread.c:388
ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:243
</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.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
next reply other threads:[~2024-03-17 14:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-17 14:43 syzbot [this message]
2024-04-15 14:41 ` [syzbot] Re: [syzbot] [usb?] WARNING in usbnet_start_xmit/usb_submit_urb (2) syzbot
2025-02-18 16:29 ` Nikita Zhandarovich
2025-02-18 16:43 ` syzbot
2025-02-18 16:55 ` Nikita Zhandarovich
2025-02-18 17:10 ` syzbot
2025-02-18 17:11 ` Nikita Zhandarovich
2025-02-18 17:25 ` syzbot
2025-02-24 15:30 ` Nikita Zhandarovich
2025-02-24 16:01 ` syzbot
[not found] <20240415144101.44907-1-n.zhandarovich@fintech.ru>
2024-04-15 15:03 ` 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=000000000000346bbd0613dc4396@google.com \
--to=syzbot+d693c07c6f647e0388d3@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oneukum@suse.com \
--cc=pabeni@redhat.com \
--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.