[v6.1] INFO: task hung in ip_tunnel_delete_nets (4)
0 views
Skip to first unread message
syzbot
May 27, 2026, 5:28:21 PM (3 days ago) May 27
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: dcbcab9d7079 Linux 6.1.174
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=137309a6580000
kernel config: https://syzkaller.appspot.com/x/.config?x=4dd3c1715f0a309b
dashboard link: https://syzkaller.appspot.com/bug?extid=c9db75f28a515dceba61
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0f3e0db767ff/disk-dcbcab9d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d14e7b82c164/vmlinux-dcbcab9d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/52745da582ab/bzImage-dcbcab9d.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+c9db75...@syzkaller.appspotmail.com
INFO: task kworker/u4:2:16752 blocked for more than 165 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/u4:2 state:D stack:26736 pid:16752 ppid:2 flags:0x00004000
Workqueue: netns cleanup_net
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0x11d1/0x40e0 kernel/sched/core.c:6562
schedule+0xb9/0x180 kernel/sched/core.c:6638
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6697
__mutex_lock_common kernel/locking/mutex.c:679 [inline]
__mutex_lock+0x562/0xaf0 kernel/locking/mutex.c:747
ip_tunnel_delete_nets+0xd0/0x370 net/ipv4/ip_tunnel.c:1152
ops_exit_list net/core/net_namespace.c:177 [inline]
cleanup_net+0x791/0xba0 net/core/net_namespace.c:640
process_one_work+0x8a2/0x1160 kernel/workqueue.c:2292
worker_thread+0xaa2/0x1270 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:
5 locks held by kworker/u4:1/11:
1 lock held by rcu_tasks_kthre/12:
#0: ffffffff8cb2e770 (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: ffffffff8cb2ef90 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x33/0xf00 kernel/rcu/tasks.h:517
1 lock held by khungtaskd/27:
#0: ffffffff8cb2dde0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:350 [inline]
#0: ffffffff8cb2dde0 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:791 [inline]
#0: ffffffff8cb2dde0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x51/0x290 kernel/locking/lockdep.c:6513
2 locks held by getty/4029:
#0: ffff88814d206098 (&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+0x429/0x1390 drivers/tty/n_tty.c:2198
2 locks held by syz-executor/4262:
3 locks held by kworker/0:4/4277:
#0: ffff88802f1cc138 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#1: ffffc90003ea7d00 ((work_completion)(&(&net->ipv6.addr_chk_work)->work)){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#2: ffffffff8dd49768 (rtnl_mutex){+.+.}-{3:3}, at: addrconf_verify_work+0x15/0x30 net/ipv6/addrconf.c:4672
3 locks held by kworker/1:4/4317:
3 locks held by kworker/0:5/4318:
#0: ffff888017471938 ((wq_completion)events_power_efficient){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#1: ffffc900043e7d00 ((reg_check_chans).work){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#2: ffffffff8dd49768 (rtnl_mutex){+.+.}-{3:3}, at: reg_check_chans_work+0x8e/0xda0 net/wireless/reg.c:2499
2 locks held by kworker/1:5/4320:
#0: ffff888017470938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#1: ffffc90004417d00 (free_ipc_work){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
4 locks held by kworker/u5:1/9128:
3 locks held by kworker/1:13/11491:
#0: ffff88802f1cc138 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#1: ffffc90003427d00 ((work_completion)(&(&net->ipv6.addr_chk_work)->work)){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#2: ffffffff8dd49768 (rtnl_mutex){+.+.}-{3:3}, at: addrconf_verify_work+0x15/0x30 net/ipv6/addrconf.c:4672
3 locks held by kworker/0:11/11493:
4 locks held by kworker/u4:2/16752:
#0: ffff888017616938 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#1: ffffc90004567d00 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#2: ffffffff8dd3c890 (pernet_ops_rwsem){++++}-{3:3}, at: cleanup_net+0x148/0xba0 net/core/net_namespace.c:594
#3: ffffffff8dd49768 (rtnl_mutex){+.+.}-{3:3}, at: ip_tunnel_delete_nets+0xd0/0x370 net/ipv4/ip_tunnel.c:1152
1 lock held by dhcpcd-run-hook/16965:
1 lock held by syz.6.2558/16985:
#0: ffffffff8dd49768 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:74 [inline]
#0: ffffffff8dd49768 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x824/0xfc0 net/core/rtnetlink.c:6154
1 lock held by syz.8.2565/17006:
#0: ffffffff8cb33ab8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:323 [inline]
#0: ffffffff8cb33ab8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x3c0/0x890 kernel/rcu/tree_exp.h:962
1 lock held by syz.2.2569/17017:
#0: ffffffff8dd49768 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:74 [inline]
#0: ffffffff8dd49768 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x824/0xfc0 net/core/rtnetlink.c:6154
3 locks held by syz-executor/17019:
1 lock held by syz-executor/17023:
#0: ffffffff8dd49768 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:74 [inline]
#0: ffffffff8dd49768 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x824/0xfc0 net/core/rtnetlink.c:6154
1 lock held by syz-executor/17027:
1 lock held by syz-executor/17029:
#0: ffff88804da8d468 (&hdev->req_lock){+.+.}-{3:3}, at: hci_dev_do_open net/bluetooth/hci_core.c:455 [inline]
#0: ffff88804da8d468 (&hdev->req_lock){+.+.}-{3:3}, at: hci_dev_open+0x1ef/0x2f0 net/bluetooth/hci_core.c:513
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 27 Comm: khungtaskd Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026
Call Trace:
<TASK>
dump_stack_lvl+0x188/0x24e lib/dump_stack.c:106
nmi_cpu_backtrace+0x3e6/0x460 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 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 9128 Comm: kworker/u5:1 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026
Workqueue: hci8 hci_rx_work
RIP: 0010:rcu_is_watching+0x70/0xa0 kernel/rcu/tree.c:723
Code: 00 49 03 1e 48 89 d8 48 c1 e8 03 42 0f b6 04 38 84 c0 75 2f 8b 03 65 ff 0d c5 ed 95 7e 74 0c 83 e0 04 c1 e8 02 5b 41 5e 41 5f <c3> e8 22 02 94 ff eb ed 48 c7 c7 80 3c b3 8c 48 89 de e8 39 a7 cc
RSP: 0018:ffffc900001e0b78 EFLAGS: 00000002
RAX: 0000000000000001 RBX: 0000000000000000 RCX: de54ee3bc120a700
RDX: 0000000000000000 RSI: ffffffff8adf1b40 RDI: ffffffff8adf1b00
RBP: ffffc900001e0c90 R08: ffffffff8e200c2f R09: 1ffffffff1c40185
R10: dffffc0000000000 R11: fffffbfff1c40186 R12: dffffc0000000000
R13: dffffc0000000000 R14: 0000000000000001 R15: 1ffff9200003c17c
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f0fc8782e80 CR3: 00000000591b4000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
trace_lock_release include/trace/events/lock.h:69 [inline]
lock_release+0xcf/0x920 kernel/locking/lockdep.c:5673
__raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:149 [inline]
_raw_spin_unlock_irqrestore+0x6d/0x120 kernel/locking/spinlock.c:194
debug_hrtimer_deactivate kernel/time/hrtimer.c:453 [inline]
__run_hrtimer kernel/time/hrtimer.c:1715 [inline]
__hrtimer_run_queues+0x2d5/0xd50 kernel/time/hrtimer.c:1811
hrtimer_interrupt+0x3c5/0x9c0 kernel/time/hrtimer.c:1873
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1107 [inline]
__sysvec_apic_timer_interrupt+0x153/0x5a0 arch/x86/kernel/apic/apic.c:1124
instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1118 [inline]
sysvec_apic_timer_interrupt+0x9b/0xc0 arch/x86/kernel/apic/apic.c:1118
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:691
RIP: 0010:console_emit_next_record+0x970/0xba0 kernel/printk/printk.c:2786
Code: 0f 85 a7 00 00 00 e8 0f ac 1a 00 0f b6 5c 24 0f 4d 85 e4 75 07 e8 00 ac 1a 00 eb 06 e8 f9 ab 1a 00 fb 66 43 c7 44 3d 24 f8 f8 <43> c6 44 3d 26 f8 49 81 c6 00 06 06 06 4f 89 74 3d 14 66 43 c7 44
RSP: 0018:ffffc9000cd1f400 EFLAGS: 00000287
RAX: ffffffff8167dab7 RBX: 0000000000000001 RCX: 0000000000100000
RDX: ffffc9001b965000 RSI: 0000000000002381 RDI: 0000000000002382
RBP: ffffc9000cd1f620 R08: ffffffff90afd247 R09: 1ffffffff215fa48
R10: dffffc0000000000 R11: fffffbfff215fa49 R12: 0000000000000200
R13: 1ffff920019a3e8c R14: f8f8f8f8f2f2f2f8 R15: dffffc0000000000
console_flush_all kernel/printk/printk.c:-1 [inline]
console_unlock+0x223/0x630 kernel/printk/printk.c:2906
vprintk_emit+0x4b3/0x6a0 kernel/printk/printk.c:2303
_printk+0xda/0x130 kernel/printk/printk.c:2328
bt_warn+0x11e/0x180 net/bluetooth/lib.c:235
hci_cc_func net/bluetooth/hci_event.c:4197 [inline]
hci_cmd_complete_evt+0x399/0x930 net/bluetooth/hci_event.c:4221
hci_event_func net/bluetooth/hci_event.c:7419 [inline]
hci_event_packet+0x7b9/0x1280 net/bluetooth/hci_event.c:7474
hci_rx_work+0x3eb/0xd40 net/bluetooth/hci_core.c:4109
process_one_work+0x8a2/0x1160 kernel/workqueue.c:2292
worker_thread+0xaa2/0x1270 kernel/workqueue.c:2439
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: dcbcab9d7079 Linux 6.1.174
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=137309a6580000
kernel config: https://syzkaller.appspot.com/x/.config?x=4dd3c1715f0a309b
dashboard link: https://syzkaller.appspot.com/bug?extid=c9db75f28a515dceba61
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/0f3e0db767ff/disk-dcbcab9d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d14e7b82c164/vmlinux-dcbcab9d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/52745da582ab/bzImage-dcbcab9d.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+c9db75...@syzkaller.appspotmail.com
INFO: task kworker/u4:2:16752 blocked for more than 165 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/u4:2 state:D stack:26736 pid:16752 ppid:2 flags:0x00004000
Workqueue: netns cleanup_net
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0x11d1/0x40e0 kernel/sched/core.c:6562
schedule+0xb9/0x180 kernel/sched/core.c:6638
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:6697
__mutex_lock_common kernel/locking/mutex.c:679 [inline]
__mutex_lock+0x562/0xaf0 kernel/locking/mutex.c:747
ip_tunnel_delete_nets+0xd0/0x370 net/ipv4/ip_tunnel.c:1152
ops_exit_list net/core/net_namespace.c:177 [inline]
cleanup_net+0x791/0xba0 net/core/net_namespace.c:640
process_one_work+0x8a2/0x1160 kernel/workqueue.c:2292
worker_thread+0xaa2/0x1270 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:
5 locks held by kworker/u4:1/11:
1 lock held by rcu_tasks_kthre/12:
#0: ffffffff8cb2e770 (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: ffffffff8cb2ef90 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x33/0xf00 kernel/rcu/tasks.h:517
1 lock held by khungtaskd/27:
#0: ffffffff8cb2dde0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:350 [inline]
#0: ffffffff8cb2dde0 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:791 [inline]
#0: ffffffff8cb2dde0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x51/0x290 kernel/locking/lockdep.c:6513
2 locks held by getty/4029:
#0: ffff88814d206098 (&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+0x429/0x1390 drivers/tty/n_tty.c:2198
2 locks held by syz-executor/4262:
3 locks held by kworker/0:4/4277:
#0: ffff88802f1cc138 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#1: ffffc90003ea7d00 ((work_completion)(&(&net->ipv6.addr_chk_work)->work)){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#2: ffffffff8dd49768 (rtnl_mutex){+.+.}-{3:3}, at: addrconf_verify_work+0x15/0x30 net/ipv6/addrconf.c:4672
3 locks held by kworker/1:4/4317:
3 locks held by kworker/0:5/4318:
#0: ffff888017471938 ((wq_completion)events_power_efficient){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#1: ffffc900043e7d00 ((reg_check_chans).work){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#2: ffffffff8dd49768 (rtnl_mutex){+.+.}-{3:3}, at: reg_check_chans_work+0x8e/0xda0 net/wireless/reg.c:2499
2 locks held by kworker/1:5/4320:
#0: ffff888017470938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#1: ffffc90004417d00 (free_ipc_work){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
4 locks held by kworker/u5:1/9128:
3 locks held by kworker/1:13/11491:
#0: ffff88802f1cc138 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#1: ffffc90003427d00 ((work_completion)(&(&net->ipv6.addr_chk_work)->work)){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#2: ffffffff8dd49768 (rtnl_mutex){+.+.}-{3:3}, at: addrconf_verify_work+0x15/0x30 net/ipv6/addrconf.c:4672
3 locks held by kworker/0:11/11493:
4 locks held by kworker/u4:2/16752:
#0: ffff888017616938 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#1: ffffc90004567d00 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work+0x7b0/0x1160 kernel/workqueue.c:2267
#2: ffffffff8dd3c890 (pernet_ops_rwsem){++++}-{3:3}, at: cleanup_net+0x148/0xba0 net/core/net_namespace.c:594
#3: ffffffff8dd49768 (rtnl_mutex){+.+.}-{3:3}, at: ip_tunnel_delete_nets+0xd0/0x370 net/ipv4/ip_tunnel.c:1152
1 lock held by dhcpcd-run-hook/16965:
1 lock held by syz.6.2558/16985:
#0: ffffffff8dd49768 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:74 [inline]
#0: ffffffff8dd49768 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x824/0xfc0 net/core/rtnetlink.c:6154
1 lock held by syz.8.2565/17006:
#0: ffffffff8cb33ab8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:323 [inline]
#0: ffffffff8cb33ab8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x3c0/0x890 kernel/rcu/tree_exp.h:962
1 lock held by syz.2.2569/17017:
#0: ffffffff8dd49768 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:74 [inline]
#0: ffffffff8dd49768 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x824/0xfc0 net/core/rtnetlink.c:6154
3 locks held by syz-executor/17019:
1 lock held by syz-executor/17023:
#0: ffffffff8dd49768 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:74 [inline]
#0: ffffffff8dd49768 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x824/0xfc0 net/core/rtnetlink.c:6154
1 lock held by syz-executor/17027:
1 lock held by syz-executor/17029:
#0: ffff88804da8d468 (&hdev->req_lock){+.+.}-{3:3}, at: hci_dev_do_open net/bluetooth/hci_core.c:455 [inline]
#0: ffff88804da8d468 (&hdev->req_lock){+.+.}-{3:3}, at: hci_dev_open+0x1ef/0x2f0 net/bluetooth/hci_core.c:513
=============================================
NMI backtrace for cpu 0
CPU: 0 PID: 27 Comm: khungtaskd Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026
Call Trace:
<TASK>
dump_stack_lvl+0x188/0x24e lib/dump_stack.c:106
nmi_cpu_backtrace+0x3e6/0x460 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 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 9128 Comm: kworker/u5:1 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026
Workqueue: hci8 hci_rx_work
RIP: 0010:rcu_is_watching+0x70/0xa0 kernel/rcu/tree.c:723
Code: 00 49 03 1e 48 89 d8 48 c1 e8 03 42 0f b6 04 38 84 c0 75 2f 8b 03 65 ff 0d c5 ed 95 7e 74 0c 83 e0 04 c1 e8 02 5b 41 5e 41 5f <c3> e8 22 02 94 ff eb ed 48 c7 c7 80 3c b3 8c 48 89 de e8 39 a7 cc
RSP: 0018:ffffc900001e0b78 EFLAGS: 00000002
RAX: 0000000000000001 RBX: 0000000000000000 RCX: de54ee3bc120a700
RDX: 0000000000000000 RSI: ffffffff8adf1b40 RDI: ffffffff8adf1b00
RBP: ffffc900001e0c90 R08: ffffffff8e200c2f R09: 1ffffffff1c40185
R10: dffffc0000000000 R11: fffffbfff1c40186 R12: dffffc0000000000
R13: dffffc0000000000 R14: 0000000000000001 R15: 1ffff9200003c17c
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f0fc8782e80 CR3: 00000000591b4000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<IRQ>
trace_lock_release include/trace/events/lock.h:69 [inline]
lock_release+0xcf/0x920 kernel/locking/lockdep.c:5673
__raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:149 [inline]
_raw_spin_unlock_irqrestore+0x6d/0x120 kernel/locking/spinlock.c:194
debug_hrtimer_deactivate kernel/time/hrtimer.c:453 [inline]
__run_hrtimer kernel/time/hrtimer.c:1715 [inline]
__hrtimer_run_queues+0x2d5/0xd50 kernel/time/hrtimer.c:1811
hrtimer_interrupt+0x3c5/0x9c0 kernel/time/hrtimer.c:1873
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1107 [inline]
__sysvec_apic_timer_interrupt+0x153/0x5a0 arch/x86/kernel/apic/apic.c:1124
instr_sysvec_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1118 [inline]
sysvec_apic_timer_interrupt+0x9b/0xc0 arch/x86/kernel/apic/apic.c:1118
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x16/0x20 arch/x86/include/asm/idtentry.h:691
RIP: 0010:console_emit_next_record+0x970/0xba0 kernel/printk/printk.c:2786
Code: 0f 85 a7 00 00 00 e8 0f ac 1a 00 0f b6 5c 24 0f 4d 85 e4 75 07 e8 00 ac 1a 00 eb 06 e8 f9 ab 1a 00 fb 66 43 c7 44 3d 24 f8 f8 <43> c6 44 3d 26 f8 49 81 c6 00 06 06 06 4f 89 74 3d 14 66 43 c7 44
RSP: 0018:ffffc9000cd1f400 EFLAGS: 00000287
RAX: ffffffff8167dab7 RBX: 0000000000000001 RCX: 0000000000100000
RDX: ffffc9001b965000 RSI: 0000000000002381 RDI: 0000000000002382
RBP: ffffc9000cd1f620 R08: ffffffff90afd247 R09: 1ffffffff215fa48
R10: dffffc0000000000 R11: fffffbfff215fa49 R12: 0000000000000200
R13: 1ffff920019a3e8c R14: f8f8f8f8f2f2f2f8 R15: dffffc0000000000
console_flush_all kernel/printk/printk.c:-1 [inline]
console_unlock+0x223/0x630 kernel/printk/printk.c:2906
vprintk_emit+0x4b3/0x6a0 kernel/printk/printk.c:2303
_printk+0xda/0x130 kernel/printk/printk.c:2328
bt_warn+0x11e/0x180 net/bluetooth/lib.c:235
hci_cc_func net/bluetooth/hci_event.c:4197 [inline]
hci_cmd_complete_evt+0x399/0x930 net/bluetooth/hci_event.c:4221
hci_event_func net/bluetooth/hci_event.c:7419 [inline]
hci_event_packet+0x7b9/0x1280 net/bluetooth/hci_event.c:7474
hci_rx_work+0x3eb/0xd40 net/bluetooth/hci_core.c:4109
process_one_work+0x8a2/0x1160 kernel/workqueue.c:2292
worker_thread+0xaa2/0x1270 kernel/workqueue.c:2439
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