Hello,
syzbot found the following issue on:
HEAD commit: 1a8763b93150 Linux 6.1.188
git tree: linux-6.1.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=13bdb4c9580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=31dfefc4a14efea3
dashboard link:
https://syzkaller.appspot.com/bug?extid=b9c22629d8b121c7d4a9
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/be5de8c5e41e/disk-1a8763b9.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/b803e8d05dd4/vmlinux-1a8763b9.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/723f53728c4f/bzImage-1a8763b9.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+b9c226...@syzkaller.appspotmail.com
INFO: task syz.5.573:7243 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.5.573 state:D stack:27088 pid:7243 ppid:5633 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_preempt_disabled+0xf/0x20 kernel/sched/core.c:6698
__mutex_lock_common kernel/locking/mutex.c:679 [inline]
__mutex_lock+0x548/0xae0 kernel/locking/mutex.c:747
write_pool_threads+0x10b/0x5e0 fs/nfsd/nfsctl.c:468
nfsctl_transaction_write+0x105/0x150 fs/nfsd/nfsctl.c:114
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:0x7f7aced9e159
RSP: 002b:00007f7acfc8b028 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f7acf026090 RCX: 00007f7aced9e159
RDX: 0000000000000002 RSI: 00002000000001c0 RDI: 0000000000000005
RBP: 00007f7acee3506b R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f7acf026128 R14: 00007f7acf026090 R15: 00007ffe44e7c048
</TASK>
INFO: task syz.5.573:7245 blocked for more than 143 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.5.573 state:D stack:26832 pid:7245 ppid:5633 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_preempt_disabled+0xf/0x20 kernel/sched/core.c:6698
__mutex_lock_common kernel/locking/mutex.c:679 [inline]
__mutex_lock+0x548/0xae0 kernel/locking/mutex.c:747
write_pool_threads+0x10b/0x5e0 fs/nfsd/nfsctl.c:468
nfsctl_transaction_write fs/nfsd/nfsctl.c:114 [inline]
nfsctl_transaction_read+0x165/0x1b0 fs/nfsd/nfsctl.c:129
vfs_read+0x2db/0x960 fs/read_write.c:468
ksys_read+0x14d/0x260 fs/read_write.c:613
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:0x7f7aced9e159
RSP: 002b:00007f7acfc6a028 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
RAX: ffffffffffffffda RBX: 00007f7acf026180 RCX: 00007f7aced9e159
RDX: 0000000000000064 RSI: 0000200000000240 RDI: 0000000000000006
RBP: 00007f7acee3506b R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f7acf026218 R14: 00007f7acf026180 R15: 00007ffe44e7c048
</TASK>
Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
#0: ffffffff8cb2e170 (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: ffffffff8cb2e990 (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/27:
#0: ffffffff8cb2d7e0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:350 [inline]
#0: ffffffff8cb2d7e0 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:791 [inline]
#0: ffffffff8cb2d7e0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x51/0x290 kernel/locking/lockdep.c:6529
1 lock held by dhcpcd/3934:
#0: ffffffff8dd550a8 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:74 [inline]
#0: ffffffff8dd550a8 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x80d/0xfb0 net/core/rtnetlink.c:6163
2 locks held by getty/4031:
#0: ffff88814d85c098 (&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:11/4578:
#0: ffff888017470938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
#1: ffffc90005057d00 ((work_completion)(&pwq->unbound_release_work)){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
#2: ffffffff8cb334b8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:323 [inline]
#2: ffffffff8cb334b8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x3c0/0x890 kernel/rcu/tree_exp.h:962
2 locks held by kworker/0:15/4582:
#0: ffff888017472138 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
#1: ffffc900051a7d00 ((work_completion)(&rew->rew_work)){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
3 locks held by syz.5.573/7241:
#0: ffff88807c7e2368 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x2ae/0x360 fs/file.c:1038
#1: ffff88806243e460 (sb_writers#32){.+.+}-{0:0}, at: vfs_write+0x270/0x9a0 fs/read_write.c:580
#2: ffffffff8cdcce48 (nfsd_mutex){+.+.}-{3:3}, at: write_ports+0xb3/0xb80 fs/nfsd/nfsctl.c:846
3 locks held by syz.5.573/7243:
#0: ffff88807a5914e8 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x2ae/0x360 fs/file.c:1038
#1: ffff88806243e460 (sb_writers#32){.+.+}-{0:0}, at: vfs_write+0x270/0x9a0 fs/read_write.c:580
#2: ffffffff8cdcce48 (nfsd_mutex){+.+.}-{3:3}, at: write_pool_threads+0x10b/0x5e0 fs/nfsd/nfsctl.c:468
2 locks held by syz.5.573/7245:
#0: ffff88805d74d9e8 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x2ae/0x360 fs/file.c:1038
#1: ffffffff8cdcce48 (nfsd_mutex){+.+.}-{3:3}, at: write_pool_threads+0x10b/0x5e0 fs/nfsd/nfsctl.c:468
3 locks held by syz.2.706/7876:
#0: ffff88807c3980e8 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x2ae/0x360 fs/file.c:1038
#1: ffff888058308460 (sb_writers#32){.+.+}-{0:0}, at: vfs_write+0x270/0x9a0 fs/read_write.c:580
#2: ffffffff8cdcce48 (nfsd_mutex){+.+.}-{3:3}, at: write_versions+0x90/0xbb0 fs/nfsd/nfsctl.c:681
3 locks held by syz.2.706/7878:
#0: ffff88807dd68fe8 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x2ae/0x360 fs/file.c:1038
#1: ffff888058308460 (sb_writers#32){.+.+}-{0:0}, at: vfs_write+0x270/0x9a0 fs/read_write.c:580
#2: ffffffff8cdcce48 (nfsd_mutex){+.+.}-{3:3}, at: write_ports+0xb3/0xb80 fs/nfsd/nfsctl.c:846
3 locks held by syz.2.706/7883:
#0: ffff88807b73d9e8 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0x2ae/0x360 fs/file.c:1038
#1: ffff888058308460 (sb_writers#32){.+.+}-{0:0}, at: vfs_write+0x270/0x9a0 fs/read_write.c:580
#2: ffffffff8cdcce48 (nfsd_mutex){+.+.}-{3:3}, at: nfsd_svc+0x61/0xab0 fs/nfsd/nfssvc.c:783
2 locks held by syz-executor/8258:
#0: ffff8880533240e0 (&type->s_umount_key#31){++++}-{3:3}, at: deactivate_super+0xa0/0xd0 fs/super.c:362
#1: ffffffff8cb33380 (rcu_state.barrier_mutex){+.+.}-{3:3}, at: rcu_barrier+0x48/0x5e0 kernel/rcu/tree.c:4023
3 locks held by kworker/u4:17/8609:
#0: ffff888017479138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
#1: ffffc90003cf7d00 ((linkwatch_work).work){+.+.}-{0:0}, at: process_one_work+0x7b4/0x1160 kernel/workqueue.c:2267
#2: ffffffff8dd550a8 (rtnl_mutex){+.+.}-{3:3}, at: linkwatch_event+0xa/0x50 net/core/link_watch.c:263
2 locks held by syz.6.1206/10359:
#0: ffffffff8dd550a8 (rtnl_mutex){+.+.}-{3:3}, at: tun_detach drivers/net/tun.c:698 [inline]
#0: ffffffff8dd550a8 (rtnl_mutex){+.+.}-{3:3}, at: tun_chr_close+0x3d/0x1b0 drivers/net/tun.c:3506
#1: ffffffff8cb334b8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:291 [inline]
#1: ffffffff8cb334b8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x2ec/0x890 kernel/rcu/tree_exp.h:962
1 lock held by syz.1.1208/10360:
#0: ffffffff8dd550a8 (rtnl_mutex){+.+.}-{3:3}, at: tun_detach drivers/net/tun.c:698 [inline]
#0: ffffffff8dd550a8 (rtnl_mutex){+.+.}-{3:3}, at: tun_chr_close+0x3d/0x1b0 drivers/net/tun.c:3506
1 lock held by syz.1.1208/10363:
#0: ffffffff8dd550a8 (rtnl_mutex){+.+.}-{3:3}, at: dev_ioctl+0x54d/0xe80 net/core/dev_ioctl.c:571
1 lock held by syz.1.1208/10371:
#0: ffffffff8dd550a8 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:74 [inline]
#0: ffffffff8dd550a8 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x80d/0xfb0 net/core/rtnetlink.c:6163
=============================================
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 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 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 8844 Comm: kworker/u4:18 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
Workqueue: events_unbound nsim_dev_trap_report_work
RIP: 0010:__is_kernel_text include/asm-generic/sections.h:208 [inline]
RIP: 0010:is_kernel_text include/linux/kallsyms.h:29 [inline]
RIP: 0010:core_kernel_text kernel/extable.c:68 [inline]
RIP: 0010:kernel_text_address+0x15/0xd0 kernel/extable.c:99
Code: 92 c2 20 ca 08 c2 0f b6 c2 5b c3 66 2e 0f 1f 84 00 00 00 00 00 55 41 56 53 48 81 ff 00 00 00 81 0f 93 c0 48 81 ff 48 78 60 8a <0f> 92 c1 bd 01 00 00 00 84 c8 75 0c 48 89 fb e8 a7 6d aa ff 85 c0
RSP: 0018:ffffc900039276d8 EFLAGS: 00000297
RAX: 0000000000000001 RBX: ffffffff81d2ae47 RCX: 0000000080000001
RDX: ffffc90003927701 RSI: dffffc0000000000 RDI: ffffffff81d2ae47
RBP: ffffc900039277b0 R08: ffffc90003927b20 R09: ffffc90003927778
R10: dffffc0000000000 R11: fffff52000724ef1 R12: ffff888054271e00
R13: ffffc90003927b40 R14: dffffc0000000000 R15: 1ffff92000724eee
FS: 0000000000000000(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f03f5df14b8 CR3: 000000007e6ef000 CR4: 00000000003506f0
Call Trace:
<TASK>
__kernel_text_address+0x9/0x30 kernel/extable.c:79
unwind_get_return_address+0x49/0x80 arch/x86/kernel/unwind_orc.c:323
arch_stack_walk+0xf2/0x140 arch/x86/kernel/stacktrace.c:26
stack_trace_save+0xa6/0xf0 kernel/stacktrace.c:122
kasan_save_stack mm/kasan/common.c:46 [inline]
kasan_set_track+0x4b/0x70 mm/kasan/common.c:53
kasan_save_free_info+0x27/0x40 mm/kasan/generic.c:516
____kasan_slab_free+0x126/0x1f0 mm/kasan/common.c:237
kasan_slab_free include/linux/kasan.h:177 [inline]
slab_free_hook mm/slub.c:1729 [inline]
slab_free_freelist_hook+0x133/0x1b0 mm/slub.c:1755
slab_free mm/slub.c:3687 [inline]
kmem_cache_free+0xf7/0x2a0 mm/slub.c:3709
nsim_dev_trap_report drivers/net/netdevsim/dev.c:821 [inline]
nsim_dev_trap_report_work+0x71f/0xa80 drivers/net/netdevsim/dev.c:851
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