From: syzbot <syzbot+d693c07c6f647e0388d3@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, n.zhandarovich@fintech.ru,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [usb?] WARNING in usbnet_start_xmit/usb_submit_urb (2)
Date: Mon, 15 Apr 2024 08:03:03 -0700 [thread overview]
Message-ID: <0000000000000d41d2061623ebed@google.com> (raw)
In-Reply-To: <20240415144101.44907-1-n.zhandarovich@fintech.ru>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING in usbnet_start_xmit/usb_submit_urb
------------[ cut here ]------------
usb 2-1: BOGUS urb xfer, pipe 3 != type 1
WARNING: CPU: 0 PID: 726 at drivers/usb/core/urb.c:503 usb_submit_urb+0xe4b/0x1730 drivers/usb/core/urb.c:503
Modules linked in:
CPU: 0 PID: 726 Comm: kworker/0:2 Not tainted 6.8.0-syzkaller-08951-gfe46a7dd189e #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
Workqueue: mld mld_ifc_work
RIP: 0010:usb_submit_urb+0xe4b/0x1730 drivers/usb/core/urb.c:503
Code: 84 3c 02 00 00 e8 35 48 30 fd 4c 89 ef e8 1d 24 01 ff 45 89 e0 89 e9 4c 89 f2 48 89 c6 48 c7 c7 c0 49 30 87 e8 46 b1 f6 fc 90 <0f> 0b 90 90 e9 e9 f8 ff ff e8 07 48 30 fd 49 81 c4 b8 05 00 00 e9
RSP: 0000:ffffc90001bef2e0 EFLAGS: 00010082
RAX: 0000000000000000 RBX: ffff8881026a1e00 RCX: ffffffff8118b029
RDX: ffff88810b350000 RSI: ffffffff8118b036 RDI: 0000000000000001
RBP: 0000000000000003 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000000 R11: 000000000000000c R12: 0000000000000001
R13: ffff888101f760a8 R14: ffff888105ee9040 R15: ffff8881026a1e7c
FS: 0000000000000000(0000) GS:ffff8881f6400000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f13260e9870 CR3: 000000010dbd0000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
usbnet_start_xmit+0x696/0x2440 drivers/net/usb/usbnet.c:1453
__netdev_start_xmit include/linux/netdevice.h:4903 [inline]
netdev_start_xmit include/linux/netdevice.h:4917 [inline]
xmit_one net/core/dev.c:3531 [inline]
dev_hard_start_xmit+0x143/0x720 net/core/dev.c:3547
sch_direct_xmit+0x18e/0x840 net/sched/sch_generic.c:343
__dev_xmit_skb net/core/dev.c:3760 [inline]
__dev_queue_xmit+0x12c5/0x3ef0 net/core/dev.c:4301
dev_queue_xmit include/linux/netdevice.h:3091 [inline]
neigh_resolve_output net/core/neighbour.c:1563 [inline]
neigh_resolve_output+0x5ba/0x950 net/core/neighbour.c:1543
neigh_output include/net/neighbour.h:542 [inline]
ip6_finish_output2+0xad9/0x2300 net/ipv6/ip6_output.c:137
__ip6_finish_output+0x3d8/0xf10 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:450 [inline]
NF_HOOK.constprop.0+0x118/0x8b0 include/linux/netfilter.h:314
mld_sendpack+0x6e6/0xd20 net/ipv6/mcast.c:1818
mld_send_cr net/ipv6/mcast.c:2119 [inline]
mld_ifc_work+0x756/0xce0 net/ipv6/mcast.c:2650
process_one_work+0x9a9/0x1a60 kernel/workqueue.c:3254
process_scheduled_works kernel/workqueue.c:3335 [inline]
worker_thread+0x6c8/0xf70 kernel/workqueue.c:3416
kthread+0x2c1/0x3a0 kernel/kthread.c:388
ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:243
</TASK>
Tested on:
commit: fe46a7dd Merge tag 'sound-6.9-rc1' of git://git.kernel..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=15b90f43180000
kernel config: https://syzkaller.appspot.com/x/.config?x=811ce8e010ac6afc
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
Note: no patches were applied.
next parent reply other threads:[~2024-04-15 15:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240415144101.44907-1-n.zhandarovich@fintech.ru>
2024-04-15 15:03 ` syzbot [this message]
2024-03-17 14:43 [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
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=0000000000000d41d2061623ebed@google.com \
--to=syzbot+d693c07c6f647e0388d3@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=n.zhandarovich@fintech.ru \
--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.