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=13215bb9580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=31dfefc4a14efea3
dashboard link:
https://syzkaller.appspot.com/bug?extid=a250ae8cd98c724fe377
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+a250ae...@syzkaller.appspotmail.com
INFO: task syz.0.68:4734 blocked for more than 144 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.0.68 state:D stack:26000 pid:4734 ppid:4274 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
do_uevent+0x1e9/0x490 fs/dlm/lockspace.c:210
new_lockspace fs/dlm/lockspace.c:659 [inline]
__dlm_new_lockspace+0x1d6a/0x22b0 fs/dlm/lockspace.c:719
device_create_lockspace+0xc4/0x350 fs/dlm/user.c:426
device_write+0x893/0xea0 fs/dlm/user.c:618
vfs_write+0x2dc/0x9a0 fs/read_write.c:582
ksys_write+0x14d/0x260 fs/read_write.c:637
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:0x7f075a99e019
RSP: 002b:00007f075b941028 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f075ac25fa0 RCX: 00007f075a99e019
RDX: 0000000000000078 RSI: 0000200000000400 RDI: 0000000000000005
RBP: 00007f075aa3500c R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f075ac26038 R14: 00007f075ac25fa0 R15: 00007ffc0f74abf8
</TASK>
Showing all locks held in the system:
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
2 locks held by kworker/1:0/22:
#0: ffff888017472138 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
#1: ffffc900001c7d00 ((work_completion)(&rew->rew_work)){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
1 lock held by khungtaskd/27:
#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
1 lock held by dhcpcd/3933:
#0: ffffffff8dd5b968 (rtnl_mutex){+.+.}-{3:3}, at: __netlink_dump_start+0x11e/0x6f0 net/netlink/af_netlink.c:2310
2 locks held by getty/4028:
#0: ffff88814cbc6098 (&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
2 locks held by kworker/0:3/4290:
3 locks held by kworker/1:4/4320:
#0: ffff88802f3bad38 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
#1: ffffc90004307d00 ((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 kworker/u4:77/4480:
#0: ffff8880b8e3ad18 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x98/0x130 kernel/sched/core.c:546
#1: ffff8880b8e27888 (&per_cpu_ptr(group->pcpu, cpu)->seq){-.-.}-{0:0}, at: psi_task_switch+0x400/0x740 kernel/sched/psi.c:999
#2: ffff8880b8e27888 (&per_cpu_ptr(group->pcpu, cpu)->seq){-.-.}-{0:0}, at: psi_task_change+0xdc/0x240 kernel/sched/psi.c:924
#3: ffffffff96e5b850 (&obj_hash[i].lock){-.-.}-{2:2}, at: debug_object_activate+0x68/0x4f0 lib/debugobjects.c:747
#4: ffffffff8c9df808 (text_mutex){+.+.}-{3:3}, at: arch_jump_label_transform_apply+0xe/0x20 arch/x86/kernel/jump_label.c:145
4 locks held by kworker/u4:98/4501:
#0: ffff888017479138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
#1: ffffc900063c7d00 ((linkwatch_work).work){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
#2: ffffffff8dd5b968 (rtnl_mutex){+.+.}-{3:3}, at: linkwatch_event+0xa/0x50 net/core/link_watch.c:263
#3: ffffffff8cb33838 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:323 [inline]
#3: ffffffff8cb33838 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x3c0/0x890 kernel/rcu/tree_exp.h:962
4 locks held by kworker/u4:100/4503:
#0: ffff88801761e938 ((wq_completion)netns){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
#1: ffffc900063e7d00 (net_cleanup_work){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
#2: ffffffff8dd4ead0 (pernet_ops_rwsem){++++}-{3:3}, at: cleanup_net+0x148/0xba0 net/core/net_namespace.c:594
#3: ffffffff8dd5b968 (rtnl_mutex){+.+.}-{3:3}, at: ip_tunnel_delete_nets+0xd2/0x370 net/ipv4/ip_tunnel.c:1152
1 lock held by syz.0.68/4734:
#0: ffffffff96d4d888 (&ls_lock){+.+.}-{3:3}, at: __dlm_new_lockspace+0xad/0x22b0 fs/dlm/lockspace.c:713
1 lock held by dlm_recoverd/4744:
#0: ffff8880769fcca0 (&ls->ls_in_recovery){+.+.}-{3:3}, at: dlm_recoverd+0xa6/0x1df0 fs/dlm/recoverd.c:312
1 lock held by syz-executor/5233:
#0: ffffffff8cb33838 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:323 [inline]
#0: ffffffff8cb33838 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x3c0/0x890 kernel/rcu/tree_exp.h:962
2 locks held by syz-executor/5768:
#0: ffffffff8ddbc170 (cb_lock){++++}-{3:3}, at: genl_rcv+0x15/0x40 net/netlink/genetlink.c:860
#1: ffffffff8dd5b968 (rtnl_mutex){+.+.}-{3:3}, at: nl80211_pre_doit+0x5a/0x890 net/wireless/nl80211.c:16372
3 locks held by syz.1.186/5947:
#0: ffff88807d0d34e8 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x2ae/0x360 fs/file.c:1038
#1: ffff888048548460 (sb_writers#14){.+.+}-{0:0}, at: vfs_write+0x270/0x9a0 fs/read_write.c:580
#2: ffffffff8cdcce08 (nfsd_mutex){+.+.}-{3:3}, at: nfsd_svc+0x61/0xab0 fs/nfsd/nfssvc.c:783
=============================================
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/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
</TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 4501 Comm: kworker/u4:98 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Workqueue: xprtiod xs_tcp_setup_socket
RIP: 0010:preempt_latency_start kernel/sched/core.c:5695 [inline]
RIP: 0010:preempt_count_add+0xbf/0x190 kernel/sched/core.c:5718
Code: e8 86 6e 0c 00 65 4c 8b 35 5e b2 a9 7e 49 81 c6 d8 14 00 00 4c 89 f0 48 c1 e8 03 42 80 3c 38 00 74 08 4c 89 f7 e8 61 9e 7a 00 <49> 89 1e 5b 41 5e 41 5f c3 89 fb e8 11 dc b9 02 89 df 85 c0 74 9b
RSP: 0018:ffffc900063c7640 EFLAGS: 00000046
RAX: 1ffff11005683a1b RBX: 0000000000000000 RCX: ffffffff96c17100
RDX: dffffc0000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc900063c76f8 R08: ffffffff90b10357 R09: 1ffffffff216206a
R10: dffffc0000000000 R11: fffffbfff216206b R12: dffffc0000000000
R13: 0000000000000000 R14: ffff88802b41d0d8 R15: dffffc0000000000
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000056406d735138 CR3: 000000000c88e000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
__raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:109 [inline]
_raw_spin_lock_irqsave+0x95/0x100 kernel/locking/spinlock.c:162
__unfreeze_partials+0x8f/0x1e0 mm/slub.c:2555
put_cpu_partial+0x17c/0x250 mm/slub.c:2667
qlink_free mm/kasan/quarantine.c:168 [inline]
qlist_free_all+0x76/0xe0 mm/kasan/quarantine.c:187
kasan_quarantine_reduce+0x144/0x160 mm/kasan/quarantine.c:294
__kasan_slab_alloc+0x1e/0x80 mm/kasan/common.c:306
kasan_slab_alloc include/linux/kasan.h:201 [inline]
slab_post_alloc_hook+0x4b/0x490 mm/slab.h:737
slab_alloc_node mm/slub.c:3359 [inline]
slab_alloc mm/slub.c:3367 [inline]
__kmem_cache_alloc_lru mm/slub.c:3374 [inline]
kmem_cache_alloc+0x18b/0x2f0 mm/slub.c:3383
kmem_cache_zalloc include/linux/slab.h:689 [inline]
lsm_inode_alloc security/security.c:597 [inline]
security_inode_alloc+0x30/0x110 security/security.c:1041
inode_init_always+0x910/0xc90 fs/inode.c:232
alloc_inode fs/inode.c:268 [inline]
new_inode_pseudo+0x91/0x1c0 fs/inode.c:1063
sock_alloc net/socket.c:631 [inline]
__sock_create+0x129/0x940 net/socket.c:1514
xs_create_sock+0xfa/0x760 net/sunrpc/xprtsock.c:1841
xs_tcp_setup_socket+0x1c2/0xb80 net/sunrpc/xprtsock.c:2303
process_one_work+0x8ab/0x1160 kernel/workqueue.c:2292
worker_thread+0xaf5/0x12a0 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