[v6.1] INFO: task hung in hub_event (4)
0 views
Skip to first unread message
syzbot
Oct 27, 2025, 5:24:40 PM (3 days ago) Oct 27
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 8e6e2188d949 Linux 6.1.157
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=111ea7e2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7eb38bd5021fec61
dashboard link: https://syzkaller.appspot.com/bug?extid=f5ff5c7164a0f46a848c
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/dcc01324de1b/disk-8e6e2188.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a93dd5469c70/vmlinux-8e6e2188.xz
kernel image: https://storage.googleapis.com/syzbot-assets/04635e384401/bzImage-8e6e2188.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+f5ff5c...@syzkaller.appspotmail.com
INFO: task kworker/1:0:22 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/1:0 state:D stack:25936 pid:22 ppid:2 flags:0x00004000
Workqueue: usb_hub_wq hub_event
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5244 [inline]
__schedule+0x10ec/0x40b0 kernel/sched/core.c:6561
schedule+0xb9/0x180 kernel/sched/core.c:6637
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6696
__mutex_lock_common kernel/locking/mutex.c:679 [inline]
__mutex_lock+0x555/0xaf0 kernel/locking/mutex.c:747
hub_port_connect drivers/usb/core/hub.c:5414 [inline]
hub_port_connect_change drivers/usb/core/hub.c:5657 [inline]
port_event drivers/usb/core/hub.c:5817 [inline]
hub_event+0x21ee/0x54e0 drivers/usb/core/hub.c:5899
process_one_work+0x898/0x1160 kernel/workqueue.c:2292
worker_thread+0xaa2/0x1250 kernel/workqueue.c:2439
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</TASK>
Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
#0: ffffffff8cb2b630 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x33/0xf00 kernel/rcu/tasks.h:517
1 lock held by rcu_tasks_trace/13:
#0: ffffffff8cb2be50 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x33/0xf00 kernel/rcu/tasks.h:517
5 locks held by kworker/1:0/22:
#0: ffff888143ea5538 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x7a1/0x1160 kernel/workqueue.c:2267
#1: ffffc900001c7d00 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x7a1/0x1160 kernel/workqueue.c:2267
#2: ffff888028c5c190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:840 [inline]
#2: ffff888028c5c190 (&dev->mutex){....}-{3:3}, at: hub_event+0x1a7/0x54e0 drivers/usb/core/hub.c:5845
#3: ffff888028c5f4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: usb_lock_port drivers/usb/core/hub.c:3200 [inline]
#3: ffff888028c5f4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_port_connect drivers/usb/core/hub.c:5413 [inline]
#3: ffff888028c5f4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_port_connect_change drivers/usb/core/hub.c:5657 [inline]
#3: ffff888028c5f4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: port_event drivers/usb/core/hub.c:5817 [inline]
#3: ffff888028c5f4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_event+0x21bd/0x54e0 drivers/usb/core/hub.c:5899
#4: ffff8880286fca68 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_port_connect drivers/usb/core/hub.c:5414 [inline]
#4: ffff8880286fca68 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_port_connect_change drivers/usb/core/hub.c:5657 [inline]
#4: ffff8880286fca68 (hcd->address0_mutex){+.+.}-{3:3}, at: port_event drivers/usb/core/hub.c:5817 [inline]
#4: ffff8880286fca68 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_event+0x21ee/0x54e0 drivers/usb/core/hub.c:5899
1 lock held by khungtaskd/27:
#0: ffffffff8cb2aca0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:350 [inline]
#0: ffffffff8cb2aca0 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:791 [inline]
#0: ffffffff8cb2aca0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x51/0x290 kernel/locking/lockdep.c:6513
5 locks held by kworker/1:2/125:
#0: ffff888143ea5538 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x7a1/0x1160 kernel/workqueue.c:2267
#1: ffffc90002dc7d00 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x7a1/0x1160 kernel/workqueue.c:2267
#2: ffff888028c8a190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:840 [inline]
#2: ffff888028c8a190 (&dev->mutex){....}-{3:3}, at: hub_event+0x1a7/0x54e0 drivers/usb/core/hub.c:5845
#3: ffff888028c8d4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: usb_lock_port drivers/usb/core/hub.c:3200 [inline]
#3: ffff888028c8d4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_port_connect drivers/usb/core/hub.c:5413 [inline]
#3: ffff888028c8d4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_port_connect_change drivers/usb/core/hub.c:5657 [inline]
#3: ffff888028c8d4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: port_event drivers/usb/core/hub.c:5817 [inline]
#3: ffff888028c8d4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_event+0x21bd/0x54e0 drivers/usb/core/hub.c:5899
#4: ffff8880286fca68 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_port_connect drivers/usb/core/hub.c:5414 [inline]
#4: ffff8880286fca68 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_port_connect_change drivers/usb/core/hub.c:5657 [inline]
#4: ffff8880286fca68 (hcd->address0_mutex){+.+.}-{3:3}, at: port_event drivers/usb/core/hub.c:5817 [inline]
#4: ffff8880286fca68 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_event+0x21ee/0x54e0 drivers/usb/core/hub.c:5899
2 locks held by getty/4031:
#0: ffff88814d2c4098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:244
#1: ffffc9000327b2f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x41b/0x1380 drivers/tty/n_tty.c:2198
4 locks held by kworker/u4:18/5013:
3 locks held by syz.0.738/6966:
#0: ffff88802807f098 (&tty->ldisc_sem){++++}-{0:0}, at: __tty_ldisc_lock drivers/tty/tty_ldisc.c:290 [inline]
#0: ffff88802807f098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_lock_pair_timeout drivers/tty/tty_ldisc.c:336 [inline]
#0: ffff88802807f098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_lock_pair drivers/tty/tty_ldisc.c:367 [inline]
#0: ffff88802807f098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_release+0x58/0x200 drivers/tty/tty_ldisc.c:781
#1: ffff8880557b3098 (&tty->ldisc_sem/1){+.+.}-{0:0}, at: __tty_ldisc_lock_nested drivers/tty/tty_ldisc.c:296 [inline]
#1: ffff8880557b3098 (&tty->ldisc_sem/1){+.+.}-{0:0}, at: tty_ldisc_lock_pair_timeout drivers/tty/tty_ldisc.c:338 [inline]
#1: ffff8880557b3098 (&tty->ldisc_sem/1){+.+.}-{0:0}, at: tty_ldisc_lock_pair drivers/tty/tty_ldisc.c:367 [inline]
#1: ffff8880557b3098 (&tty->ldisc_sem/1){+.+.}-{0:0}, at: tty_ldisc_release+0x7c/0x200 drivers/tty/tty_ldisc.c:781
#2: ffffffff8cb30840 (rcu_state.barrier_mutex){+.+.}-{3:3}, at: rcu_barrier+0x48/0x600 kernel/rcu/tree.c:4023
=============================================
NMI backtrace for cpu 1
CPU: 1 PID: 27 Comm: khungtaskd Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
Call Trace:
<TASK>
dump_stack_lvl+0x168/0x22e lib/dump_stack.c:106
nmi_cpu_backtrace+0x3f4/0x470 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x1d4/0x450 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:220 [inline]
watchdog+0xeee/0xf30 kernel/hung_task.c:377
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 15 Comm: ksoftirqd/0 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
RIP: 0010:skb_release_head_state+0x0/0x240 net/core/skbuff.c:839
Code: 89 f1 80 e1 07 80 c1 03 38 c1 0f 8c 69 ff ff ff 4c 89 f7 e8 02 a1 b4 f9 e9 5c ff ff ff 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 <55> 41 57 41 56 41 55 41 54 53 48 89 fb 49 bc 00 00 00 00 00 fc ff
RSP: 0018:ffffc90000147980 EFLAGS: 00000246
RAX: ffffffff881c81dc RBX: ffff88807e46edc0 RCX: ffff88813fef3b80
RDX: 0000000000000100 RSI: ffffffff8adef380 RDI: ffff88807e46edc0
RBP: 0000000000000001 R08: dffffc0000000000 R09: fffffbfff1c3ed96
R10: fffffbfff1c3ed96 R11: 1ffffffff1c3ed95 R12: ffff8880765eeae0
R13: ffff88801da68358 R14: ffff88807e46eea4 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffff446b000 CR3: 000000000c88e000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
skb_release_all net/core/skbuff.c:854 [inline]
__kfree_skb net/core/skbuff.c:870 [inline]
consume_skb+0x72/0x100 net/core/skbuff.c:1035
mac80211_hwsim_beacon_tx+0x61e/0xae0 drivers/net/wireless/mac80211_hwsim.c:2121
__iterate_interfaces+0x243/0x500 net/mac80211/util.c:788
ieee80211_iterate_active_interfaces_atomic+0xd7/0x170 net/mac80211/util.c:824
mac80211_hwsim_beacon+0xb7/0x1b0 drivers/net/wireless/mac80211_hwsim.c:2147
__run_hrtimer kernel/time/hrtimer.c:1747 [inline]
__hrtimer_run_queues+0x554/0xd60 kernel/time/hrtimer.c:1811
hrtimer_run_softirq+0x183/0x2a0 kernel/time/hrtimer.c:1828
handle_softirqs+0x2a1/0x920 kernel/softirq.c:596
run_ksoftirqd+0x98/0xf0 kernel/softirq.c:963
smpboot_thread_fn+0x64a/0xa40 kernel/smpboot.c:164
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</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.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
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
syzbot found the following issue on:
HEAD commit: 8e6e2188d949 Linux 6.1.157
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=111ea7e2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7eb38bd5021fec61
dashboard link: https://syzkaller.appspot.com/bug?extid=f5ff5c7164a0f46a848c
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/dcc01324de1b/disk-8e6e2188.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a93dd5469c70/vmlinux-8e6e2188.xz
kernel image: https://storage.googleapis.com/syzbot-assets/04635e384401/bzImage-8e6e2188.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+f5ff5c...@syzkaller.appspotmail.com
INFO: task kworker/1:0:22 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/1:0 state:D stack:25936 pid:22 ppid:2 flags:0x00004000
Workqueue: usb_hub_wq hub_event
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5244 [inline]
__schedule+0x10ec/0x40b0 kernel/sched/core.c:6561
schedule+0xb9/0x180 kernel/sched/core.c:6637
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6696
__mutex_lock_common kernel/locking/mutex.c:679 [inline]
__mutex_lock+0x555/0xaf0 kernel/locking/mutex.c:747
hub_port_connect drivers/usb/core/hub.c:5414 [inline]
hub_port_connect_change drivers/usb/core/hub.c:5657 [inline]
port_event drivers/usb/core/hub.c:5817 [inline]
hub_event+0x21ee/0x54e0 drivers/usb/core/hub.c:5899
process_one_work+0x898/0x1160 kernel/workqueue.c:2292
worker_thread+0xaa2/0x1250 kernel/workqueue.c:2439
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</TASK>
Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
#0: ffffffff8cb2b630 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x33/0xf00 kernel/rcu/tasks.h:517
1 lock held by rcu_tasks_trace/13:
#0: ffffffff8cb2be50 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x33/0xf00 kernel/rcu/tasks.h:517
5 locks held by kworker/1:0/22:
#0: ffff888143ea5538 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x7a1/0x1160 kernel/workqueue.c:2267
#1: ffffc900001c7d00 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x7a1/0x1160 kernel/workqueue.c:2267
#2: ffff888028c5c190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:840 [inline]
#2: ffff888028c5c190 (&dev->mutex){....}-{3:3}, at: hub_event+0x1a7/0x54e0 drivers/usb/core/hub.c:5845
#3: ffff888028c5f4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: usb_lock_port drivers/usb/core/hub.c:3200 [inline]
#3: ffff888028c5f4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_port_connect drivers/usb/core/hub.c:5413 [inline]
#3: ffff888028c5f4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_port_connect_change drivers/usb/core/hub.c:5657 [inline]
#3: ffff888028c5f4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: port_event drivers/usb/core/hub.c:5817 [inline]
#3: ffff888028c5f4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_event+0x21bd/0x54e0 drivers/usb/core/hub.c:5899
#4: ffff8880286fca68 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_port_connect drivers/usb/core/hub.c:5414 [inline]
#4: ffff8880286fca68 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_port_connect_change drivers/usb/core/hub.c:5657 [inline]
#4: ffff8880286fca68 (hcd->address0_mutex){+.+.}-{3:3}, at: port_event drivers/usb/core/hub.c:5817 [inline]
#4: ffff8880286fca68 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_event+0x21ee/0x54e0 drivers/usb/core/hub.c:5899
1 lock held by khungtaskd/27:
#0: ffffffff8cb2aca0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:350 [inline]
#0: ffffffff8cb2aca0 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:791 [inline]
#0: ffffffff8cb2aca0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x51/0x290 kernel/locking/lockdep.c:6513
5 locks held by kworker/1:2/125:
#0: ffff888143ea5538 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work+0x7a1/0x1160 kernel/workqueue.c:2267
#1: ffffc90002dc7d00 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work+0x7a1/0x1160 kernel/workqueue.c:2267
#2: ffff888028c8a190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:840 [inline]
#2: ffff888028c8a190 (&dev->mutex){....}-{3:3}, at: hub_event+0x1a7/0x54e0 drivers/usb/core/hub.c:5845
#3: ffff888028c8d4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: usb_lock_port drivers/usb/core/hub.c:3200 [inline]
#3: ffff888028c8d4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_port_connect drivers/usb/core/hub.c:5413 [inline]
#3: ffff888028c8d4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_port_connect_change drivers/usb/core/hub.c:5657 [inline]
#3: ffff888028c8d4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: port_event drivers/usb/core/hub.c:5817 [inline]
#3: ffff888028c8d4f8 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_event+0x21bd/0x54e0 drivers/usb/core/hub.c:5899
#4: ffff8880286fca68 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_port_connect drivers/usb/core/hub.c:5414 [inline]
#4: ffff8880286fca68 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_port_connect_change drivers/usb/core/hub.c:5657 [inline]
#4: ffff8880286fca68 (hcd->address0_mutex){+.+.}-{3:3}, at: port_event drivers/usb/core/hub.c:5817 [inline]
#4: ffff8880286fca68 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_event+0x21ee/0x54e0 drivers/usb/core/hub.c:5899
2 locks held by getty/4031:
#0: ffff88814d2c4098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:244
#1: ffffc9000327b2f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x41b/0x1380 drivers/tty/n_tty.c:2198
4 locks held by kworker/u4:18/5013:
3 locks held by syz.0.738/6966:
#0: ffff88802807f098 (&tty->ldisc_sem){++++}-{0:0}, at: __tty_ldisc_lock drivers/tty/tty_ldisc.c:290 [inline]
#0: ffff88802807f098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_lock_pair_timeout drivers/tty/tty_ldisc.c:336 [inline]
#0: ffff88802807f098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_lock_pair drivers/tty/tty_ldisc.c:367 [inline]
#0: ffff88802807f098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_release+0x58/0x200 drivers/tty/tty_ldisc.c:781
#1: ffff8880557b3098 (&tty->ldisc_sem/1){+.+.}-{0:0}, at: __tty_ldisc_lock_nested drivers/tty/tty_ldisc.c:296 [inline]
#1: ffff8880557b3098 (&tty->ldisc_sem/1){+.+.}-{0:0}, at: tty_ldisc_lock_pair_timeout drivers/tty/tty_ldisc.c:338 [inline]
#1: ffff8880557b3098 (&tty->ldisc_sem/1){+.+.}-{0:0}, at: tty_ldisc_lock_pair drivers/tty/tty_ldisc.c:367 [inline]
#1: ffff8880557b3098 (&tty->ldisc_sem/1){+.+.}-{0:0}, at: tty_ldisc_release+0x7c/0x200 drivers/tty/tty_ldisc.c:781
#2: ffffffff8cb30840 (rcu_state.barrier_mutex){+.+.}-{3:3}, at: rcu_barrier+0x48/0x600 kernel/rcu/tree.c:4023
=============================================
NMI backtrace for cpu 1
CPU: 1 PID: 27 Comm: khungtaskd Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
Call Trace:
<TASK>
dump_stack_lvl+0x168/0x22e lib/dump_stack.c:106
nmi_cpu_backtrace+0x3f4/0x470 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x1d4/0x450 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:220 [inline]
watchdog+0xeee/0xf30 kernel/hung_task.c:377
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 15 Comm: ksoftirqd/0 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/02/2025
RIP: 0010:skb_release_head_state+0x0/0x240 net/core/skbuff.c:839
Code: 89 f1 80 e1 07 80 c1 03 38 c1 0f 8c 69 ff ff ff 4c 89 f7 e8 02 a1 b4 f9 e9 5c ff ff ff 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 <55> 41 57 41 56 41 55 41 54 53 48 89 fb 49 bc 00 00 00 00 00 fc ff
RSP: 0018:ffffc90000147980 EFLAGS: 00000246
RAX: ffffffff881c81dc RBX: ffff88807e46edc0 RCX: ffff88813fef3b80
RDX: 0000000000000100 RSI: ffffffff8adef380 RDI: ffff88807e46edc0
RBP: 0000000000000001 R08: dffffc0000000000 R09: fffffbfff1c3ed96
R10: fffffbfff1c3ed96 R11: 1ffffffff1c3ed95 R12: ffff8880765eeae0
R13: ffff88801da68358 R14: ffff88807e46eea4 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffff446b000 CR3: 000000000c88e000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
skb_release_all net/core/skbuff.c:854 [inline]
__kfree_skb net/core/skbuff.c:870 [inline]
consume_skb+0x72/0x100 net/core/skbuff.c:1035
mac80211_hwsim_beacon_tx+0x61e/0xae0 drivers/net/wireless/mac80211_hwsim.c:2121
__iterate_interfaces+0x243/0x500 net/mac80211/util.c:788
ieee80211_iterate_active_interfaces_atomic+0xd7/0x170 net/mac80211/util.c:824
mac80211_hwsim_beacon+0xb7/0x1b0 drivers/net/wireless/mac80211_hwsim.c:2147
__run_hrtimer kernel/time/hrtimer.c:1747 [inline]
__hrtimer_run_queues+0x554/0xd60 kernel/time/hrtimer.c:1811
hrtimer_run_softirq+0x183/0x2a0 kernel/time/hrtimer.c:1828
handle_softirqs+0x2a1/0x920 kernel/softirq.c:596
run_ksoftirqd+0x98/0xf0 kernel/softirq.c:963
smpboot_thread_fn+0x64a/0xa40 kernel/smpboot.c:164
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</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.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
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
Reply all
Reply to author
Forward
0 new messages