Hello,
syzbot found the following issue on:
HEAD commit: cc5ec8769306 Linux 5.15.196
git tree: linux-5.15.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=16803612580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=e1bb6d24ef2164eb
dashboard link:
https://syzkaller.appspot.com/bug?extid=7c3b76f40262fa29618c
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=1144e612580000
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/ed7568bc5bb4/disk-cc5ec876.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/e343e0aaac77/vmlinux-cc5ec876.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/089870f2a980/bzImage-cc5ec876.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+7c3b76...@syzkaller.appspotmail.com
INFO: task kworker/u4:0:9 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/u4:0 state:D stack:22824 pid: 9 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
ip6gre_exit_batch_net+0xbf/0x490 net/ipv6/ip6_gre.c:1647
ops_exit_list net/core/net_namespace.c:177 [inline]
cleanup_net+0x77b/0xb80 net/core/net_namespace.c:635
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:1:26 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:1 state:D stack:25768 pid: 26 ppid: 2 flags:0x00004000
Workqueue: ipv6_addrconf addrconf_dad_work
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
addrconf_dad_work+0xc4/0x1520 net/ipv6/addrconf.c:4110
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 udevd:3560 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:udevd state:D stack:23816 pid: 3560 ppid: 1 flags:0x00004002
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
device_lock include/linux/device.h:764 [inline]
uevent_show+0x17a/0x330 drivers/base/core.c:2408
dev_attr_show+0x50/0xb0 drivers/base/core.c:2110
sysfs_kf_seq_show+0x316/0x4c0 fs/sysfs/file.c:61
seq_read_iter+0x49b/0xd50 fs/seq_file.c:230
call_read_iter include/linux/fs.h:2167 [inline]
new_sync_read fs/read_write.c:404 [inline]
vfs_read+0x725/0xcf0 fs/read_write.c:485
ksys_read+0x14d/0x250 fs/read_write.c:623
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:0x7fb47e31f407
RSP: 002b:00007fff09962260 EFLAGS: 00000202 ORIG_RAX: 0000000000000000
RAX: ffffffffffffffda RBX: 00007fb47e231880 RCX: 00007fb47e31f407
RDX: 0000000000001000 RSI: 00005604c949eb30 RDI: 000000000000000c
RBP: 00007fb47e467ff0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000202 R12: 000000000000000a
R13: 00007fb47e467ea0 R14: 0000000000000000 R15: 00005604c9420bd0
</TASK>
INFO: task dhcpcd:3853 blocked for more than 144 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:dhcpcd state:D stack:21376 pid: 3853 ppid: 3852 flags:0x00004002
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
percpu_rwsem_wait+0x2d8/0x310 kernel/locking/percpu-rwsem.c:160
__percpu_down_read+0xc9/0x100 kernel/locking/percpu-rwsem.c:174
percpu_down_read include/linux/percpu-rwsem.h:65 [inline]
cgroup_threadgroup_change_begin include/linux/cgroup-defs.h:724 [inline]
cgroup_css_set_fork kernel/cgroup/cgroup.c:6225 [inline]
cgroup_can_fork+0xc94/0xda0 kernel/cgroup/cgroup.c:6343
copy_process+0x2290/0x3e00 kernel/fork.c:2382
kernel_clone+0x219/0x930 kernel/fork.c:2679
__do_sys_clone kernel/fork.c:2796 [inline]
__se_sys_clone kernel/fork.c:2780 [inline]
__x64_sys_clone+0x170/0x1c0 kernel/fork.c:2780
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:0x7fe3ac5e1636
RSP: 002b:00007ffc9c330ee0 EFLAGS: 00000246 ORIG_RAX: 0000000000000038
RAX: ffffffffffffffda RBX: 00007ffc9c330ee8 RCX: 00007fe3ac5e1636
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000001200011
RBP: 00007ffc9c351430 R08: 0000000000000000 R09: 0000000000000001
R10: 00007fe3ac50da10 R11: 0000000000000246 R12: 00007ffc9c331020
R13: 0000000000000000 R14: 0000000000000000 R15: 000055a5f8a09ac0
</TASK>
INFO: task kworker/0:4:4238 blocked for more than 144 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/0:4 state:D stack:23880 pid: 4238 ppid: 2 flags:0x00004000
Workqueue: ipv6_addrconf addrconf_dad_work
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
addrconf_dad_work+0xc4/0x1520 net/ipv6/addrconf.c:4110
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 syz-executor:4315 blocked for more than 144 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor state:D stack:21768 pid: 4315 ppid: 4312 flags:0x00004000
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
rwsem_down_write_slowpath+0xc46/0x11f0 kernel/locking/rwsem.c:1165
mmap_write_lock include/linux/mmap_lock.h:71 [inline]
mpol_rebind_mm+0x33/0x2c0 mm/mempolicy.c:381
cpuset_attach+0x330/0x5f0 kernel/cgroup/cpuset.c:2376
cgroup_migrate_execute+0x7eb/0x1010 kernel/cgroup/cgroup.c:2597
cgroup_attach_task+0x562/0x7e0 kernel/cgroup/cgroup.c:2892
__cgroup1_procs_write+0x2e5/0x3f0 kernel/cgroup/cgroup-v1.c:527
cgroup_file_write+0x2f7/0x630 kernel/cgroup/cgroup.c:3966
kernfs_fop_write_iter+0x379/0x4c0 fs/kernfs/file.c:296
call_write_iter include/linux/fs.h:2173 [inline]
new_sync_write fs/read_write.c:507 [inline]
vfs_write+0x712/0xd00 fs/read_write.c:594
ksys_write+0x14d/0x250 fs/read_write.c:647
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:0x7f9c7496e1ff
RSP: 002b:00007ffdf9caf3d0 EFLAGS: 00000293 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007f9c7496e1ff
RDX: 0000000000000001 RSI: 00007ffdf9caf420 RDI: 0000000000000003
RBP: 00007ffdf9caf990 R08: 0000000000000000 R09: 00007ffdf9caf227
R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000001
R13: 00007ffdf9caf420 R14: 00007ffdf9caf950 R15: 00007ffdf9caf990
</TASK>
INFO: task syz-executor:4323 blocked for more than 144 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor state:D stack:22336 pid: 4323 ppid: 4313 flags:0x00004000
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
del_device_store+0xce/0x380 drivers/net/netdevsim/bus.c:344
kernfs_fop_write_iter+0x379/0x4c0 fs/kernfs/file.c:296
call_write_iter include/linux/fs.h:2173 [inline]
new_sync_write fs/read_write.c:507 [inline]
vfs_write+0x712/0xd00 fs/read_write.c:594
ksys_write+0x14d/0x250 fs/read_write.c:647
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:0x7fc46d0611ff
RSP: 002b:00007ffd0d22d4d0 EFLAGS: 00000293 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 0000000000000005 RCX: 00007fc46d0611ff
RDX: 0000000000000001 RSI: 00007ffd0d22d520 RDI: 0000000000000005
RBP: 00007fc46d0e82cb R08: 0000000000000000 R09: 00007ffd0d22d327
R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000001
R13: 00007ffd0d22d520 R14: 00007fc46dde7620 R15: 0000000000000003
</TASK>
INFO: task syz-executor:4326 blocked for more than 145 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor state:D stack:22416 pid: 4326 ppid: 4318 flags:0x00004000
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
nsim_init_netdevsim drivers/net/netdevsim/netdev.c:310 [inline]
nsim_create+0x2ef/0x3e0 drivers/net/netdevsim/netdev.c:365
__nsim_dev_port_add+0x5c7/0x980 drivers/net/netdevsim/dev.c:1312
nsim_dev_port_add_all+0x37/0x100 drivers/net/netdevsim/dev.c:1372
nsim_dev_probe+0x754/0x9c0 drivers/net/netdevsim/dev.c:1513
call_driver_probe drivers/base/dd.c:-1 [inline]
really_probe+0x284/0xc80 drivers/base/dd.c:595
__driver_probe_device+0x18c/0x330 drivers/base/dd.c:755
driver_probe_device+0x4f/0x420 drivers/base/dd.c:785
__device_attach_driver+0x2b0/0x500 drivers/base/dd.c:907
bus_for_each_drv+0x175/0x200 drivers/base/bus.c:429
__device_attach+0x29b/0x460 drivers/base/dd.c:979
bus_probe_device+0xbc/0x1e0 drivers/base/bus.c:489
device_add+0xa00/0xfb0 drivers/base/core.c:3412
nsim_bus_dev_new drivers/net/netdevsim/bus.c:435 [inline]
new_device_store+0x3d8/0x740 drivers/net/netdevsim/bus.c:302
kernfs_fop_write_iter+0x379/0x4c0 fs/kernfs/file.c:296
call_write_iter include/linux/fs.h:2173 [inline]
new_sync_write fs/read_write.c:507 [inline]
vfs_write+0x712/0xd00 fs/read_write.c:594
ksys_write+0x14d/0x250 fs/read_write.c:647
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:0x7f4f236761ff
RSP: 002b:00007ffc6f1726f0 EFLAGS: 00000293 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 0000000000000005 RCX: 00007f4f236761ff
RDX: 0000000000000003 RSI: 00007ffc6f172740 RDI: 0000000000000005
RBP: 00007f4f236fd2ef R08: 0000000000000000 R09: 00007ffc6f172547
R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000003
R13: 00007ffc6f172740 R14: 00007f4f243fc620 R15: 0000000000000003
</TASK>
Showing all locks held in the system:
1 lock held by kthreadd/2:
#0: ffffffff8c1421f0 (cgroup_threadgroup_rwsem){++++}-{0:0}, at: copy_process+0x2290/0x3e00 kernel/fork.c:2382
3 locks held by kworker/0:0/7:
#0: ffff888016871938 ((wq_completion)events_power_efficient){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc90000cc7d00 ((reg_check_chans).work){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
#2: ffffffff8d238988 (rtnl_mutex){+.+.}-{3:3}, at: reg_check_chans_work+0x81/0xa50 net/wireless/reg.c:2437
4 locks held by kworker/u4:0/9:
#0: ffff8880169cd938 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc90000ce7d00 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
#2: ffffffff8d22cd10 (pernet_ops_rwsem){++++}-{3:3}, at: cleanup_net+0x132/0xb80 net/core/net_namespace.c:589
#3: ffffffff8d238988 (rtnl_mutex){+.+.}-{3:3}, at: ip6gre_exit_batch_net+0xbf/0x490 net/ipv6/ip6_gre.c:1647
3 locks held by kworker/1:1/26:
#0: ffff88802a8af938 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc90000e1fd00 ((work_completion)(&(&ifa->dad_work)->work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
#2: ffffffff8d238988 (rtnl_mutex){+.+.}-{3:3}, at: addrconf_dad_work+0xc4/0x1520 net/ipv6/addrconf.c:4110
1 lock held by khungtaskd/27:
#0: ffffffff8c11c760 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
2 locks held by kworker/u4:2/154:
4 locks held by udevd/3560:
#0: ffff888022664e80 (&p->lock){+.+.}-{3:3}, at: seq_read_iter+0xad/0xd50 fs/seq_file.c:182
#1: ffff888079b39488 (&of->mutex){+.+.}-{3:3}, at: kernfs_seq_start+0x51/0x3c0 fs/kernfs/file.c:112
#2: ffff88807460e748 (kn->active#32){++++}-{0:0}, at: kernfs_seq_start+0x71/0x3c0 fs/kernfs/file.c:113
#3: ffff888075b31178 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:764 [inline]
#3: ffff888075b31178 (&dev->mutex){....}-{3:3}, at: uevent_show+0x17a/0x330 drivers/base/core.c:2408
1 lock held by dhcpcd/3853:
#0: ffffffff8c1421f0 (cgroup_threadgroup_rwsem){++++}-{0:0}, at: copy_process+0x2290/0x3e00 kernel/fork.c:2382
2 locks held by getty/3952:
#0: ffff88814ce67098 (&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
3 locks held by kworker/0:4/4238:
#0: ffff88802a8af938 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc90002fbfd00 ((work_completion)(&(&ifa->dad_work)->work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
#2: ffffffff8d238988 (rtnl_mutex){+.+.}-{3:3}, at: addrconf_dad_work+0xc4/0x1520 net/ipv6/addrconf.c:4110
1 lock held by syz-executor/4314:
#0: ffffffff8c1421f0 (cgroup_threadgroup_rwsem){++++}-{0:0}, at: do_exit+0x256/0x20a0 kernel/exit.c:830
7 locks held by syz-executor/4315:
#0: ffff888018dc4460 (sb_writers#11){.+.+}-{0:0}, at: vfs_write+0x28a/0xd00 fs/read_write.c:590
#1: ffff888024d07888 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1e5/0x4c0 fs/kernfs/file.c:287
#2: ffffffff8c142008 (cgroup_mutex){+.+.}-{3:3}, at: cgroup_kn_lock_live+0xee/0x230 kernel/cgroup/cgroup.c:1662
#3: ffffffff8bfbaed0 (cpu_hotplug_lock){++++}-{0:0}, at: cgroup_attach_lock kernel/cgroup/cgroup.c:2411 [inline]
#3: ffffffff8bfbaed0 (cpu_hotplug_lock){++++}-{0:0}, at: cgroup_procs_write_start+0x17c/0x580 kernel/cgroup/cgroup.c:2921
#4: ffffffff8c1421f0 (cgroup_threadgroup_rwsem){++++}-{0:0}, at: cgroup_attach_lock kernel/cgroup/cgroup.c:2413 [inline]
#4: ffffffff8c1421f0 (cgroup_threadgroup_rwsem){++++}-{0:0}, at: cgroup_procs_write_start+0x192/0x580 kernel/cgroup/cgroup.c:2921
#5: ffffffff8c14fb48 (cpuset_mutex){+.+.}-{3:3}, at: cpuset_attach+0xac/0x5f0 kernel/cgroup/cpuset.c:2348
#6: ffff88807823f828 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock include/linux/mmap_lock.h:71 [inline]
#6: ffff88807823f828 (&mm->mmap_lock){++++}-{3:3}, at: mpol_rebind_mm+0x33/0x2c0 mm/mempolicy.c:381
2 locks held by syz-executor/4317:
#0: ffffffff8c1a68f0 (dup_mmap_sem){.+.+}-{0:0}, at: dup_mmap kernel/fork.c:503 [inline]
#0: ffffffff8c1a68f0 (dup_mmap_sem){.+.+}-{0:0}, at: dup_mm kernel/fork.c:1466 [inline]
#0: ffffffff8c1a68f0 (dup_mmap_sem){.+.+}-{0:0}, at: copy_mm+0x21f/0x1380 kernel/fork.c:1518
#1: ffff88801e6ec728 (&mm->mmap_lock){++++}-{3:3}, at: mmap_write_lock_killable include/linux/mmap_lock.h:87 [inline]
#1: ffff88801e6ec728 (&mm->mmap_lock){++++}-{3:3}, at: dup_mmap kernel/fork.c:504 [inline]
#1: ffff88801e6ec728 (&mm->mmap_lock){++++}-{3:3}, at: dup_mm kernel/fork.c:1466 [inline]
#1: ffff88801e6ec728 (&mm->mmap_lock){++++}-{3:3}, at: copy_mm+0x238/0x1380 kernel/fork.c:1518
4 locks held by syz-executor/4319:
#0: ffffffff8d295710 (cb_lock){++++}-{3:3}, at: genl_rcv+0x15/0x40 net/netlink/genetlink.c:802
#1: ffffffff8d295568 (genl_mutex){+.+.}-{3:3}, at: genl_lock net/netlink/genetlink.c:33 [inline]
#1: ffffffff8d295568 (genl_mutex){+.+.}-{3:3}, at: genl_rcv_msg+0x137/0xf40 net/netlink/genetlink.c:790
#2: ffffffff8d238988 (rtnl_mutex){+.+.}-{3:3}, at: wg_set_device+0xf2/0x1e70 drivers/net/wireguard/netlink.c:504
#3: ffff8880771053e8 (&wg->device_update_lock){+.+.}-{3:3}, at: wg_set_device+0x10a/0x1e70 drivers/net/wireguard/netlink.c:505
4 locks held by syz-executor/4323:
#0: ffff88807f1e4460 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x28a/0xd00 fs/read_write.c:590
#1: ffff88805b752c88 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1e5/0x4c0 fs/kernfs/file.c:287
#2: ffff8880234ce918 (kn->active#362){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x208/0x4c0 fs/kernfs/file.c:288
#3: ffffffff8cb725e8 (nsim_bus_dev_list_lock){+.+.}-{3:3}, at: del_device_store+0xce/0x380 drivers/net/netdevsim/bus.c:344
6 locks held by syz-executor/4326:
#0: ffff88807f1e4460 (sb_writers#8){.+.+}-{0:0}, at: vfs_write+0x28a/0xd00 fs/read_write.c:590
#1: ffff88801e858488 (&of->mutex){+.+.}-{3:3}, at: kernfs_fop_write_iter+0x1e5/0x4c0 fs/kernfs/file.c:287
#2: ffff8880234ce830 (kn->active#363){.+.+}-{0:0}, at: kernfs_fop_write_iter+0x208/0x4c0 fs/kernfs/file.c:288
#3: ffffffff8cb725e8 (nsim_bus_dev_list_lock){+.+.}-{3:3}, at: new_device_store+0x13c/0x740 drivers/net/netdevsim/bus.c:295
#4: ffff888075b31178 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:764 [inline]
#4: ffff888075b31178 (&dev->mutex){....}-{3:3}, at: __device_attach+0x85/0x460 drivers/base/dd.c:954
#5: ffffffff8d238988 (rtnl_mutex){+.+.}-{3:3}, at: nsim_init_netdevsim drivers/net/netdevsim/netdev.c:310 [inline]
#5: ffffffff8d238988 (rtnl_mutex){+.+.}-{3:3}, at: nsim_create+0x2ef/0x3e0 drivers/net/netdevsim/netdev.c:365
=============================================
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 10/02/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 0 to CPUs 1:
NMI backtrace for cpu 1 skipped: idling at native_safe_halt arch/x86/include/asm/irqflags.h:51 [inline]
NMI backtrace for cpu 1 skipped: idling at arch_safe_halt arch/x86/include/asm/irqflags.h:89 [inline]
NMI backtrace for cpu 1 skipped: idling at default_idle+0xb/0x10 arch/x86/kernel/process.c:729
---
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