[v5.15] INFO: task hung in cleanup_net (2)

0 views
Skip to first unread message

syzbot

unread,
5:26 AM (12 hours ago) 5:26 AM
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 68efe5a6c16a Linux 5.15.197
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=132c8dfa580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7e6ed99963d6ee1d
dashboard link: https://syzkaller.appspot.com/bug?extid=408bf2b6b8ef5a4d11fe
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=156b5052580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/900f9b9bd850/disk-68efe5a6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1e089a5019a6/vmlinux-68efe5a6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b319f477b907/bzImage-68efe5a6.xz

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

INFO: task kworker/u4:2:154 blocked for more than 144 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/u4:2 state:D stack:23232 pid: 154 ppid: 2 flags:0x00004000
Workqueue: netns cleanup_net
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5049 [inline]
__schedule+0x11bb/0x4390 kernel/sched/core.c:6395
schedule+0x11b/0x1e0 kernel/sched/core.c:6478
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6537
__mutex_lock_common+0xc71/0x2390 kernel/locking/mutex.c:669
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
rcu_barrier+0xa1/0x4b0 kernel/rcu/tree.c:4043
cleanup_net+0x813/0xb80 net/core/net_namespace.c:646
process_one_work+0x863/0x1000 kernel/workqueue.c:2310
worker_thread+0xaa8/0x12a0 kernel/workqueue.c:2457
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
INFO: task kworker/1:6:4373 blocked for more than 144 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/1:6 state:D stack:25152 pid: 4373 ppid: 2 flags:0x00004000
Workqueue: events fqdir_free_fn
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5049 [inline]
__schedule+0x11bb/0x4390 kernel/sched/core.c:6395
schedule+0x11b/0x1e0 kernel/sched/core.c:6478
schedule_timeout+0x97/0x280 kernel/time/timer.c:1890
do_wait_for_common+0x29a/0x440 kernel/sched/completion.c:85
__wait_for_common kernel/sched/completion.c:106 [inline]
wait_for_common kernel/sched/completion.c:117 [inline]
wait_for_completion+0x48/0x60 kernel/sched/completion.c:138
rcu_barrier+0x3f5/0x4b0 kernel/rcu/tree.c:4108
fqdir_free_fn+0x2f/0x130 net/ipv4/inet_fragment.c:166
process_one_work+0x863/0x1000 kernel/workqueue.c:2310
process_scheduled_works kernel/workqueue.c:2373 [inline]
worker_thread+0xdca/0x12a0 kernel/workqueue.c:2459
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/27:
#0: ffffffff8c11c720 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
3 locks held by kworker/u4:2/154:
#0: ffff8880169cd938 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc90002007d00 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
#2: ffffffff8c1210b0 (rcu_state.barrier_mutex){+.+.}-{3:3}, at: rcu_barrier+0xa1/0x4b0 kernel/rcu/tree.c:4043
2 locks held by getty/3949:
#0: ffff88814ce13098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffffc90002d032e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x5ba/0x1a30 drivers/tty/n_tty.c:2158
6 locks held by kworker/0:7/4363:
3 locks held by kworker/1:6/4373:
#0: ffff888016870938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc9000358fd00 (fqdir_free_work){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
#2: ffffffff8c1210b0 (rcu_state.barrier_mutex){+.+.}-{3:3}, at: rcu_barrier+0xa1/0x4b0 kernel/rcu/tree.c:4043
2 locks held by kworker/1:7/4376:
#0: ffff888016872138 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc900035bfd00 ((work_completion)(&rew.rew_work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
3 locks held by kworker/1:9/4381:
#0: ffff888016870938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc90004a3fd00 (free_ipc_work){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
#2: ffffffff8c1211a8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:322 [inline]
#2: ffffffff8c1211a8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x320/0x6b0 kernel/rcu/tree_exp.h:845
4 locks held by kworker/u4:6/4437:
#0: ffff888024be5138 ((wq_completion)phy14){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc90004c8fd00 ((work_completion)(&sdata->work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
#2: ffff88801ee20d40 (&wdev->mtx){+.+.}-{3:3}, at: sdata_lock net/mac80211/ieee80211_i.h:1036 [inline]
#2: ffff88801ee20d40 (&wdev->mtx){+.+.}-{3:3}, at: ieee80211_ibss_work+0xa0/0x10b0 net/mac80211/ibss.c:1685
#3: ffff8880251397b0 (&local->sta_mtx){+.+.}-{3:3}, at: ieee80211_ibss_sta_expire net/mac80211/ibss.c:1259 [inline]
#3: ffff8880251397b0 (&local->sta_mtx){+.+.}-{3:3}, at: ieee80211_sta_merge_ibss net/mac80211/ibss.c:1302 [inline]
#3: ffff8880251397b0 (&local->sta_mtx){+.+.}-{3:3}, at: ieee80211_ibss_work+0x569/0x10b0 net/mac80211/ibss.c:1713
4 locks held by kworker/u4:7/4445:
#0: ffff888078d19938 ((wq_completion)phy12){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc90004cbfd00 ((work_completion)(&sdata->work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
#2: ffff88801eb64d40 (&wdev->mtx){+.+.}-{3:3}, at: sdata_lock net/mac80211/ieee80211_i.h:1036 [inline]
#2: ffff88801eb64d40 (&wdev->mtx){+.+.}-{3:3}, at: ieee80211_ibss_work+0xa0/0x10b0 net/mac80211/ibss.c:1685
#3: ffff888024bc17b0 (&local->sta_mtx){+.+.}-{3:3}, at: ieee80211_ibss_sta_expire net/mac80211/ibss.c:1259 [inline]
#3: ffff888024bc17b0 (&local->sta_mtx){+.+.}-{3:3}, at: ieee80211_sta_merge_ibss net/mac80211/ibss.c:1302 [inline]
#3: ffff888024bc17b0 (&local->sta_mtx){+.+.}-{3:3}, at: ieee80211_ibss_work+0x569/0x10b0 net/mac80211/ibss.c:1713
3 locks held by kworker/u4:8/4468:
#0: ffff888016879138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc90002fafd00 ((linkwatch_work).work){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
#2: ffffffff8d232788 (rtnl_mutex){+.+.}-{3:3}, at: linkwatch_event+0xa/0x50 net/core/link_watch.c:251
1 lock held by syz.1.273/4717:
#0: ffffffff8c1210b0 (rcu_state.barrier_mutex){+.+.}-{3:3}, at: rcu_barrier+0xa1/0x4b0 kernel/rcu/tree.c:4043
1 lock held by syz.0.271/4719:
#0: ffffffff8c1210b0 (rcu_state.barrier_mutex){+.+.}-{3:3}, at: rcu_barrier+0xa1/0x4b0 kernel/rcu/tree.c:4043
1 lock held by syz.2.275/4720:
#0: ffffffff8c1210b0 (rcu_state.barrier_mutex){+.+.}-{3:3}, at: rcu_barrier+0xa1/0x4b0 kernel/rcu/tree.c:4043
1 lock held by syz.3.274/4721:
#0: ffffffff8c1210b0 (rcu_state.barrier_mutex){+.+.}-{3:3}, at: rcu_barrier+0xa1/0x4b0 kernel/rcu/tree.c:4043
3 locks held by syz-executor/4726:
#0: ffff888026524ff0 (&hdev->req_lock){+.+.}-{3:3}, at: hci_dev_do_close+0x5f/0x1030 net/bluetooth/hci_core.c:1737
#1: ffff888026524078 (&hdev->lock){+.+.}-{3:3}, at: hci_dev_do_close+0x3f4/0x1030 net/bluetooth/hci_core.c:1782
#2: ffffffff8d378768 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_disconn_cfm include/net/bluetooth/hci_core.h:1517 [inline]
#2: ffffffff8d378768 (hci_cb_list_lock){+.+.}-{3:3}, at: hci_conn_hash_flush+0xa4/0x220 net/bluetooth/hci_conn.c:1622
2 locks held by syz-executor/4731:
#0: ffffffff8d226b10 (pernet_ops_rwsem){++++}-{3:3}, at: copy_net_ns+0x32e/0x5b0 net/core/net_namespace.c:499
#1: ffffffff8c1210b0 (rcu_state.barrier_mutex){+.+.}-{3:3}, at: rcu_barrier+0xa1/0x4b0 kernel/rcu/tree.c:4043
2 locks held by syz-executor/4735:
#0: ffffffff8d226b10 (pernet_ops_rwsem){++++}-{3:3}, at: copy_net_ns+0x32e/0x5b0 net/core/net_namespace.c:499
#1: ffffffff8c1210b0 (rcu_state.barrier_mutex){+.+.}-{3:3}, at: rcu_barrier+0xa1/0x4b0 kernel/rcu/tree.c:4043
2 locks held by syz-executor/4737:
#0: ffffffff8d226b10 (pernet_ops_rwsem){++++}-{3:3}, at: copy_net_ns+0x32e/0x5b0 net/core/net_namespace.c:499
#1: ffffffff8c1210b0 (rcu_state.barrier_mutex){+.+.}-{3:3}, at: rcu_barrier+0xa1/0x4b0 kernel/rcu/tree.c:4043
1 lock held by syz.4.282/4739:
#0: ffffffff8c1210b0 (rcu_state.barrier_mutex){+.+.}-{3:3}, at: rcu_barrier+0xa1/0x4b0 kernel/rcu/tree.c:4043
1 lock held by syz-executor/4753:
#0: ffffffff8d232788 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:72 [inline]
#0: ffffffff8d232788 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x7a5/0xe90 net/core/rtnetlink.c:5681
2 locks held by syz-executor/4761:
#0: ffffffff8d232788 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:72 [inline]
#0: ffffffff8d232788 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x7a5/0xe90 net/core/rtnetlink.c:5681
#1: ffffffff8c1211a8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:322 [inline]
#1: ffffffff8c1211a8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x320/0x6b0 kernel/rcu/tree_exp.h:845
1 lock held by syz-executor/4762:
#0: ffffffff8d232788 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:72 [inline]
#0: ffffffff8d232788 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x7a5/0xe90 net/core/rtnetlink.c:5681
1 lock held by syz-executor/4764:
#0: ffffffff8d232788 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:72 [inline]
#0: ffffffff8d232788 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x7a5/0xe90 net/core/rtnetlink.c:5681
1 lock held by syz-executor/4768:
#0: ffffffff8d232788 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:72 [inline]
#0: ffffffff8d232788 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x7a5/0xe90 net/core/rtnetlink.c:5681
1 lock held by dhcpcd/4786:
#0: ffff88807347c120 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1731 [inline]
#0: ffff88807347c120 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: packet_do_bind+0x35/0xce0 net/packet/af_packet.c:3212
1 lock held by dhcpcd/4788:
#0: ffff88805a5fc120 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1731 [inline]
#0: ffff88805a5fc120 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: packet_do_bind+0x35/0xce0 net/packet/af_packet.c:3212
1 lock held by dhcpcd/4789:
#0: ffff8880255cc120 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1731 [inline]
#0: ffff8880255cc120 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: packet_do_bind+0x35/0xce0 net/packet/af_packet.c:3212
1 lock held by dhcpcd/4791:
#0: ffff8880550ca120 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1731 [inline]
#0: ffff8880550ca120 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: packet_do_bind+0x35/0xce0 net/packet/af_packet.c:3212

=============================================

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/25/2025
Call Trace:
<TASK>
dump_stack_lvl+0x168/0x230 lib/dump_stack.c:106
nmi_cpu_backtrace+0x397/0x3d0 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x163/0x280 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:212 [inline]
watchdog+0xe0f/0xe50 kernel/hung_task.c:369
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 4363 Comm: kworker/0:7 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
Workqueue: events nsim_dev_trap_report_work
RIP: 0010:__sanitizer_cov_trace_pc+0x0/0x60 kernel/kcov.c:202
Code: 66 2e 0f 1f 84 00 00 00 00 00 53 48 89 fb e8 17 00 00 00 48 8b 3d d0 6b f1 0b 48 89 de 5b e9 d7 9e 43 00 00 00 cc cc 00 00 cc <48> 8b 04 24 65 48 8b 0d a4 a3 8a 7e 65 8b 15 a5 a3 8a 7e 81 e2 00
RSP: 0018:ffffc90000007b50 EFLAGS: 00000246
RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffff8880215b5940
RDX: 0000000000000100 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: 0000000000000004 R09: 0000000000000003
R10: fffff52000000f6c R11: 1ffff92000000f6c R12: ffff8880572ee4d8
R13: ffff8880572ee4d0 R14: dffffc0000000000 R15: ffff88807b299b1a
FS: 0000000000000000(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f9dd0813000 CR3: 000000007f476000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
pie_calculate_probability+0xdd/0x7d0 net/sched/sch_pie.c:321
fq_pie_timer+0x169/0x3a0 net/sched/sch_fq_pie.c:393
call_timer_fn+0x16c/0x530 kernel/time/timer.c:1451
expire_timers kernel/time/timer.c:1496 [inline]
__run_timers+0x525/0x7c0 kernel/time/timer.c:1767
run_timer_softirq+0x63/0xf0 kernel/time/timer.c:1780
handle_softirqs+0x328/0x820 kernel/softirq.c:576
do_softirq+0x13b/0x200 kernel/softirq.c:477
</IRQ>
<TASK>
__local_bh_enable_ip+0x174/0x1b0 kernel/softirq.c:401
spin_unlock_bh include/linux/spinlock.h:409 [inline]
nsim_dev_trap_report drivers/net/netdevsim/dev.c:736 [inline]
nsim_dev_trap_report_work+0x7c3/0xb40 drivers/net/netdevsim/dev.c:762
process_one_work+0x863/0x1000 kernel/workqueue.c:2310
worker_thread+0xaa8/0x12a0 kernel/workqueue.c:2457
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</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 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
Reply all
Reply to author
Forward
0 new messages