[v5.15] INFO: task hung in con_install

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 674f684f7c61 Linux 5.15.212
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1476109e580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f161cbc9aef65db0
dashboard link: https://syzkaller.appspot.com/bug?extid=e606af51f0c2a8f3978c
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f55be2937b89/disk-674f684f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a19fb0ffc049/vmlinux-674f684f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/365d4529a007/bzImage-674f684f.xz

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

INFO: task syz.1.213:5224 blocked for more than 144 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.1.213 state:D stack:26000 pid: 5224 ppid: 4187 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5049 [inline]
__schedule+0x11c3/0x4350 kernel/sched/core.c:6395
schedule+0x11b/0x1e0 kernel/sched/core.c:6478
schedule_timeout+0xbd/0x2d0 kernel/time/timer.c:2093
__down_common+0x289/0x3b0 kernel/locking/semaphore.c:228
down+0x7e/0xd0 kernel/locking/semaphore.c:63
console_lock+0x29/0x70 kernel/printk/printk.c:2557
con_install+0x94/0x720 drivers/tty/vt/vt.c:3381
tty_driver_install_tty drivers/tty/tty_io.c:1317 [inline]
tty_init_dev+0xbb/0x470 drivers/tty/tty_io.c:1431
tty_open_by_driver drivers/tty/tty_io.c:2100 [inline]
tty_open+0x7e8/0xcd0 drivers/tty/tty_io.c:2148
chrdev_open+0x585/0x5f0 fs/char_dev.c:414
do_dentry_open+0x7f7/0xf90 fs/open.c:826
do_open fs/namei.c:3616 [inline]
path_openat+0x2718/0x2fb0 fs/namei.c:3750
do_filp_open+0x1df/0x400 fs/namei.c:3777
do_sys_openat2+0x14b/0x500 fs/open.c:1255
do_sys_open fs/open.c:1271 [inline]
__do_sys_openat fs/open.c:1287 [inline]
__se_sys_openat fs/open.c:1282 [inline]
__x64_sys_openat+0x135/0x160 fs/open.c:1282
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f204e7096ce
RSP: 002b:00007f204c9a0b28 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007f204c9a16c0 RCX: 00007f204e7096ce
RDX: 0000000000000002 RSI: 00007f204c9a0c00 RDI: ffffffffffffff9c
RBP: 00007f204e7deeaf R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f204e9d1038 R14: 00007f204e9d0fa0 R15: 00007ffdf3bf5798
</TASK>
INFO: task syz.6.208:5236 blocked for more than 144 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.6.208 state:D stack:27888 pid: 5236 ppid: 4818 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5049 [inline]
__schedule+0x11c3/0x4350 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+0xdf5/0x2400 kernel/locking/mutex.c:669
__mutex_lock kernel/locking/mutex.c:729 [inline]
mutex_lock_nested+0x17/0x20 kernel/locking/mutex.c:743
tty_open_by_driver drivers/tty/tty_io.c:2064 [inline]
tty_open+0x20a/0xcd0 drivers/tty/tty_io.c:2148
chrdev_open+0x585/0x5f0 fs/char_dev.c:414
do_dentry_open+0x7f7/0xf90 fs/open.c:826
do_open fs/namei.c:3616 [inline]
path_openat+0x2718/0x2fb0 fs/namei.c:3750
do_filp_open+0x1df/0x400 fs/namei.c:3777
do_sys_openat2+0x14b/0x500 fs/open.c:1255
do_sys_open fs/open.c:1271 [inline]
__do_sys_openat fs/open.c:1287 [inline]
__se_sys_openat fs/open.c:1282 [inline]
__x64_sys_openat+0x135/0x160 fs/open.c:1282
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7effed7af6ce
RSP: 002b:00007effeba04b28 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007effeba056c0 RCX: 00007effed7af6ce
RDX: 0000000000000002 RSI: 00007effeba04c00 RDI: ffffffffffffff9c
RBP: 00007effed884eaf R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007effeda77218 R14: 00007effeda77180 R15: 00007fff35424898
</TASK>

Showing all locks held in the system:
2 locks held by kworker/0:0/7:
2 locks held by kworker/0:1/13:
#0: ffff888016c72138 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x75c/0xff0 kernel/workqueue.c:-1
#1: ffffc90000d27d00 ((work_completion)(&rew.rew_work)){+.+.}-{0:0}, at: process_one_work+0x79e/0xff0 kernel/workqueue.c:2285
1 lock held by khungtaskd/27:
#0: ffffffff8c31ef60 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by kworker/u4:3/155:
#0: ffff888016c79138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x75c/0xff0 kernel/workqueue.c:-1
#1: ffffc90002017d00 ((work_completion)(&sub_info->work)){+.+.}-{0:0}, at: process_one_work+0x79e/0xff0 kernel/workqueue.c:2285
3 locks held by kworker/0:2/1111:
#0: ffff888016c70938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x75c/0xff0 kernel/workqueue.c:-1
#1: ffffc9000476fd00 ((work_completion)(&data->fib_event_work)){+.+.}-{0:0}, at: process_one_work+0x79e/0xff0 kernel/workqueue.c:2285
#2: ffff888074fff240 (&data->fib_lock){+.+.}-{3:3}, at: nsim_fib_event_work+0x283/0x3380 drivers/net/netdevsim/fib.c:1480
2 locks held by udevd/3560:
1 lock held by dhcpcd/3853:
2 locks held by getty/3945:
#0: ffff88802c145098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffffc900025e62e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x594/0x1a50 drivers/tty/n_tty.c:2158
3 locks held by kworker/u4:9/4481:
5 locks held by syz.3.147/4909:
2 locks held by syz.1.213/5224:
#0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2064 [inline]
#0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x20a/0xcd0 drivers/tty/tty_io.c:2148
#1: ffff8880629e71c0 (&tty->legacy_mutex){+.+.}-{3:3}, at: tty_init_dev+0x6f/0x470 drivers/tty/tty_io.c:1430
1 lock held by syz.6.208/5236:
#0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2064 [inline]
#0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x20a/0xcd0 drivers/tty/tty_io.c:2148
1 lock held by syz.0.229/5345:
#0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2064 [inline]
#0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x20a/0xcd0 drivers/tty/tty_io.c:2148
1 lock held by syz.7.244/5449:
#0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: ptmx_open+0xd2/0x2c0 drivers/tty/pty.c:823
1 lock held by syz.8.262/5547:
#0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2064 [inline]
#0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x20a/0xcd0 drivers/tty/tty_io.c:2148
1 lock held by syz.3.272/5867:
#0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2064 [inline]
#0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x20a/0xcd0 drivers/tty/tty_io.c:2148
1 lock held by syz.6.328/5992:
#0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2064 [inline]
#0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x20a/0xcd0 drivers/tty/tty_io.c:2148
3 locks held by kworker/0:11/6349:
1 lock held by syz.9.395/6360:
#0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2064 [inline]
#0: ffffffff8c9f62e8 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x20a/0xcd0 drivers/tty/tty_io.c:2148
1 lock held by udevd/6392:
2 locks held by udevd/6393:
2 locks held by syz.0.467/6711:
#0: ffff88807568be10 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
#0: ffff88807568be10 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: __sock_release net/socket.c:650 [inline]
#0: ffff88807568be10 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: sock_close+0x82/0x210 net/socket.c:1346
#1: ffffffff8c3239e8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:322 [inline]
#1: ffffffff8c3239e8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x3a5/0x750 kernel/rcu/tree_exp.h:845

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

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 07/16/2026
Call Trace:
<TASK>
dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106
nmi_cpu_backtrace+0x3a2/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+0xe1b/0xe60 kernel/hung_task.c:369
kthread+0x42e/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 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]

Hello,

syzbot found the following issue on:

HEAD commit: fb28aa725e05 Linux 6.1.180
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=151678c6580000
kernel config: https://syzkaller.appspot.com/x/.config?x=31dfefc4a14efea3
dashboard link: https://syzkaller.appspot.com/bug?extid=2aa6ad378b756ba27c7f

compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:

disk image: https://storage.googleapis.com/syzbot-assets/9a6fe2a54d0f/disk-fb28aa72.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/742b23a1d931/vmlinux-fb28aa72.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b3f257c16d2e/bzImage-fb28aa72.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:

Reported-by: syzbot+2aa6ad...@syzkaller.appspotmail.com

INFO: task syz.8.609:6919 blocked for more than 143 seconds.

Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

task:syz.8.609 state:D stack:27760 pid:6919 ppid:6196 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5246 [inline]
__schedule+0x107f/0x4030 kernel/sched/core.c:6563
schedule+0xb9/0x180 kernel/sched/core.c:6639
schedule_timeout+0xbd/0x2d0 kernel/time/timer.c:2144
___down_common kernel/locking/semaphore.c:229 [inline]
__down_common+0x30c/0x740 kernel/locking/semaphore.c:250
down+0x7c/0xd0 kernel/locking/semaphore.c:64
console_lock+0x141/0x1c0 kernel/printk/printk.c:2629
con_install+0x94/0x720 drivers/tty/vt/vt.c:3381
tty_driver_install_tty drivers/tty/tty_io.c:1303 [inline]
tty_init_dev+0xcf/0x4c0 drivers/tty/tty_io.c:1415
tty_open_by_driver drivers/tty/tty_io.c:2081 [inline]
tty_open+0x7d3/0xcb0 drivers/tty/tty_io.c:2128
chrdev_open+0x585/0x5f0 fs/char_dev.c:414
do_dentry_open+0x7dd/0x10b0 fs/open.c:882
do_open fs/namei.c:3634 [inline]
path_openat+0x2674/0x2f10 fs/namei.c:3791
do_filp_open+0x1ee/0x420 fs/namei.c:3818
do_sys_openat2+0x14b/0x4f0 fs/open.c:1320
do_sys_open fs/open.c:1336 [inline]
__do_sys_openat fs/open.c:1352 [inline]
__se_sys_openat fs/open.c:1347 [inline]
__x64_sys_openat+0x135/0x160 fs/open.c:1347
do_syscall_x64 arch/x86/entry/common.c:46 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:76
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f0d15f5e84e
RSP: 002b:00007f0d16f1cb28 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007f0d16f1d6c0 RCX: 00007f0d15f5e84e
RDX: 0000000000000002 RSI: 00007f0d16f1cc00 RDI: ffffffffffffff9c
RBP: 00007f0d1603500c R08: 0000000000000000 R09: 0000000000000000

R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000

R13: 00007f0d16226038 R14: 00007f0d16225fa0 R15: 00007fff4d532ce8

</TASK>

Showing all locks held in the system:

3 locks held by kworker/0:0/7:
#0: ffff888017470938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
#1: ffffc900000c7d00 ((work_completion)(&data->fib_event_work)){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
#2: ffff888026877240 (&data->fib_lock){+.+.}-{3:3}, at: nsim_fib_event_work+0x283/0x3320 drivers/net/netdevsim/fib.c:1491
2 locks held by kworker/u4:1/11:
#0: ffff888017479138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
#1: ffffc90000107d00 ((work_completion)(&ctx->exit_work)){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
1 lock held by rcu_tasks_kthre/12:
#0: ffffffff8cb2e4f0 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x33/0xef0 kernel/rcu/tasks.h:517
1 lock held by rcu_tasks_trace/13:
#0: ffffffff8cb2ed10 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x33/0xef0 kernel/rcu/tasks.h:517
1 lock held by khungtaskd/28:
#0: ffffffff8cb2db60 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:350 [inline]
#0: ffffffff8cb2db60 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:791 [inline]
#0: ffffffff8cb2db60 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x51/0x290 kernel/locking/lockdep.c:6527
3 locks held by kworker/u4:2/30:
2 locks held by getty/4029:
#0: ffff88807e278098 (&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+0x41e/0x1360 drivers/tty/n_tty.c:2198
3 locks held by kworker/0:6/4322:
#0: ffff88802f2a9d38 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
#1: ffffc900047d7d00 ((work_completion)(&(&ifa->dad_work)->work)){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
#2: ffffffff8dd5b968 (rtnl_mutex){+.+.}-{3:3}, at: addrconf_dad_work+0xc4/0x1500 net/ipv6/addrconf.c:4138
5 locks held by syz.5.491/6481:
2 locks held by syz.8.609/6919:
#0: ffffffff8d290808 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2045 [inline]
#0: ffffffff8d290808 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x204/0xcb0 drivers/tty/tty_io.c:2128
#1: ffff888056c031c0 (&tty->legacy_mutex){+.+.}-{3:3}, at: tty_init_dev+0x70/0x4c0 drivers/tty/tty_io.c:1414
1 lock held by syz.1.633/6997:
#0: ffffffff8d290808 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2045 [inline]
#0: ffffffff8d290808 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x204/0xcb0 drivers/tty/tty_io.c:2128
1 lock held by syz.9.691/7190:
#0: ffffffff8d290808 (tty_mutex){+.+.}-{3:3}, at: ptmx_open+0xcc/0x2c0 drivers/tty/pty.c:823
1 lock held by syz.0.710/7277:
#0: ffffffff8d290808 (tty_mutex){+.+.}-{3:3}, at: ptmx_open+0xcc/0x2c0 drivers/tty/pty.c:823
1 lock held by syz.3.778/7612:
#0: ffffffff8d290808 (tty_mutex){+.+.}-{3:3}, at: ptmx_open+0xcc/0x2c0 drivers/tty/pty.c:823
1 lock held by syz.6.822/7770:
#0: ffffffff8d290808 (tty_mutex){+.+.}-{3:3}, at: ptmx_open+0xcc/0x2c0 drivers/tty/pty.c:823
1 lock held by syz.6.822/7774:
#0: ffffffff8d290808 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2045 [inline]
#0: ffffffff8d290808 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x204/0xcb0 drivers/tty/tty_io.c:2128

1 lock held by syz.2.844/7860:

#0: ffffffff8d290808 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2045 [inline]
#0: ffffffff8d290808 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x204/0xcb0 drivers/tty/tty_io.c:2128
1 lock held by syz.4.850/7882:
#0: ffffffff8d290808 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2045 [inline]
#0: ffffffff8d290808 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x204/0xcb0 drivers/tty/tty_io.c:2128
1 lock held by syz.5.899/8147:
#0: ffffffff8d290808 (tty_mutex){+.+.}-{3:3}, at: ptmx_open+0xcc/0x2c0 drivers/tty/pty.c:823
1 lock held by syz.9.919/8236:
#0: ffffffff8d290808 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2045 [inline]
#0: ffffffff8d290808 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x204/0xcb0 drivers/tty/tty_io.c:2128
1 lock held by syz-executor/8347:
#0: ffffffff8dd5b968 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:74 [inline]
#0: ffffffff8dd5b968 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x80d/0xfb0 net/core/rtnetlink.c:6163
8 locks held by syz-executor/8390:
2 locks held by syz.1.964/8403:
3 locks held by syz.1.974/8452:
2 locks held by cmp/8454:

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

NMI backtrace for cpu 0

CPU: 0 PID: 28 Comm: khungtaskd Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/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+0xf0e/0xf50 kernel/hung_task.c:377
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295