From: syzbot <syzbot+78cae3f37c62ad092caa@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
viswanathiyyappan@gmail.com
Subject: Re: [syzbot] [net?] [usb?] WARNING in rtl8150_start_xmit/usb_submit_urb
Date: Fri, 12 Sep 2025 01:32:04 -0700 [thread overview]
Message-ID: <68c3da84.050a0220.2ff435.0356.GAE@google.com> (raw)
In-Reply-To: <CAPrAcgMXXKyOCec=SXF6_MD4csgODiO41d0hQ_KsBsRmzoxk+w@mail.gmail.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING in rtl8150_start_xmit/usb_submit_urb
------------[ cut here ]------------
URB ffff888024e5b900 submitted while active
WARNING: drivers/usb/core/urb.c:380 at usb_submit_urb+0xf8c/0x18b0 drivers/usb/core/urb.c:380, CPU#1: kworker/u8:8/3539
Modules linked in:
CPU: 1 UID: 0 PID: 3539 Comm: kworker/u8:8 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
Workqueue: ipv6_addrconf addrconf_dad_work
RIP: 0010:usb_submit_urb+0xf8c/0x18b0 drivers/usb/core/urb.c:380
Code: 00 00 00 e8 36 e0 85 fa e9 25 f1 ff ff e8 2c e0 85 fa c6 05 35 0c 95 08 01 90 48 c7 c7 a0 aa 56 8c 48 89 de e8 65 6f 49 fa 90 <0f> 0b 90 90 e9 ec f0 ff ff e8 06 e0 85 fa c6 05 77 61 ab 08 01 41
RSP: 0018:ffffc90000a08a20 EFLAGS: 00010246
RAX: e78eb3a935e39000 RBX: ffff888024e5b900 RCX: ffff888030b43c80
RDX: 0000000000000100 RSI: 0000000000000000 RDI: 0000000000000002
RBP: dffffc0000000000 R08: 0000000000000003 R09: 0000000000000004
R10: dffffc0000000000 R11: fffffbfff1c7a6c8 R12: 0000000000000820
R13: ffff888074fffa82 R14: ffff888024e5b908 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8881258a7000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055c81342b078 CR3: 000000007e68c000 CR4: 00000000003526f0
Call Trace:
<IRQ>
rtl8150_start_xmit+0x2cb/0x5f0 drivers/net/usb/rtl8150.c:696
__netdev_start_xmit include/linux/netdevice.h:5222 [inline]
netdev_start_xmit include/linux/netdevice.h:5231 [inline]
xmit_one net/core/dev.c:3839 [inline]
dev_hard_start_xmit+0x2d7/0x830 net/core/dev.c:3855
sch_direct_xmit+0x241/0x4b0 net/sched/sch_generic.c:344
qdisc_restart net/sched/sch_generic.c:409 [inline]
__qdisc_run+0xb16/0x15f0 net/sched/sch_generic.c:417
qdisc_run+0xc2/0x230 include/net/pkt_sched.h:126
net_tx_action+0x7c9/0x980 net/core/dev.c:5685
handle_softirqs+0x286/0x870 kernel/softirq.c:579
do_softirq+0xec/0x180 kernel/softirq.c:480
</IRQ>
<TASK>
__local_bh_enable_ip+0x17d/0x1c0 kernel/softirq.c:407
spin_unlock_bh include/linux/spinlock.h:396 [inline]
netif_addr_unlock_bh include/linux/netdevice.h:4823 [inline]
__dev_mc_add net/core/dev_addr_lists.c:873 [inline]
dev_mc_add+0xd0/0x120 net/core/dev_addr_lists.c:886
igmp6_group_added+0x225/0x800 net/ipv6/mcast.c:681
__ipv6_dev_mc_inc+0x897/0xa50 net/ipv6/mcast.c:972
addrconf_join_solict net/ipv6/addrconf.c:2246 [inline]
addrconf_dad_begin net/ipv6/addrconf.c:4099 [inline]
addrconf_dad_work+0x3d0/0x14b0 net/ipv6/addrconf.c:4227
process_one_work kernel/workqueue.c:3263 [inline]
process_scheduled_works+0xae1/0x17b0 kernel/workqueue.c:3346
worker_thread+0x8a0/0xda0 kernel/workqueue.c:3427
kthread+0x711/0x8a0 kernel/kthread.c:463
ret_from_fork+0x4bc/0x870 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
</TASK>
Tested on:
commit: 590b221e Add linux-next specific files for 20250912
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1668b362580000
kernel config: https://syzkaller.appspot.com/x/.config?x=9134e501f17b95a4
dashboard link: https://syzkaller.appspot.com/bug?extid=78cae3f37c62ad092caa
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=152a6362580000
next parent reply other threads:[~2025-09-12 8:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPrAcgMXXKyOCec=SXF6_MD4csgODiO41d0hQ_KsBsRmzoxk+w@mail.gmail.com>
2025-09-12 8:32 ` syzbot [this message]
[not found] <CAPrAcgNhZmR4Z323aHXC-Vfwk8LBHFe9=mtR-CKQ3iADO5uoJg@mail.gmail.com>
2025-09-19 18:45 ` [syzbot] [net?] [usb?] WARNING in rtl8150_start_xmit/usb_submit_urb syzbot
[not found] <CAPrAcgNtStXdajzsDgWqyLVAMok5gpKtmt=zU2vWNr93hhzGPg@mail.gmail.com>
2025-09-17 10:26 ` syzbot
[not found] <CAPrAcgP7f7rGNKKvHYe72jHMjo2D_8wRzoPt61stAiM0fccOhg@mail.gmail.com>
2025-09-15 17:52 ` syzbot
2025-08-29 18:38 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=68c3da84.050a0220.2ff435.0356.GAE@google.com \
--to=syzbot+78cae3f37c62ad092caa@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viswanathiyyappan@gmail.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.