[v6.6] INFO: task hung in filename_create

0 views
Skip to first unread message

syzbot

unread,
Dec 23, 2025, 9:32:19 PM (7 hours ago) Dec 23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 5fa4793a2d2d Linux 6.6.119
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16da2022580000
kernel config: https://syzkaller.appspot.com/x/.config?x=691a6769a86ac817
dashboard link: https://syzkaller.appspot.com/bug?extid=ec2b95df7cbdc439bc15
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/63699875f1dd/disk-5fa4793a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8506652fcb6f/vmlinux-5fa4793a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1b30ceed1710/bzImage-5fa4793a.xz

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

INFO: task syz.6.579:9020 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.579 state:D stack:29128 pid:9020 ppid:7300 flags:0x00004006
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5380 [inline]
__schedule+0x14d2/0x44d0 kernel/sched/core.c:6699
schedule+0xbd/0x170 kernel/sched/core.c:6773
schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:6832
rwsem_down_write_slowpath+0xbd2/0xfa0 kernel/locking/rwsem.c:1178
__down_write_common kernel/locking/rwsem.c:1306 [inline]
__down_write kernel/locking/rwsem.c:1315 [inline]
down_write_nested+0x1b1/0x1f0 kernel/locking/rwsem.c:1690
inode_lock_nested include/linux/fs.h:839 [inline]
filename_create+0x1f6/0x460 fs/namei.c:3890
do_mknodat+0x183/0x4f0 fs/namei.c:4036
__do_sys_mknod fs/namei.c:4082 [inline]
__se_sys_mknod fs/namei.c:4080 [inline]
__x64_sys_mknod+0x8e/0xa0 fs/namei.c:4080
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fb19798f749
RSP: 002b:00007fb1987a4038 EFLAGS: 00000246 ORIG_RAX: 0000000000000085
RAX: ffffffffffffffda RBX: 00007fb197be6180 RCX: 00007fb19798f749
RDX: 000000000000070d RSI: 0000000000000000 RDI: 0000200000000000
RBP: 00007fb197a13f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fb197be6218 R14: 00007fb197be6180 R15: 00007ffca2b8db28
</TASK>
INFO: task syz.6.579:9021 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.579 state:D stack:26952 pid:9021 ppid:7300 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5380 [inline]
__schedule+0x14d2/0x44d0 kernel/sched/core.c:6699
schedule+0xbd/0x170 kernel/sched/core.c:6773
schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:6832
rwsem_down_write_slowpath+0xbd2/0xfa0 kernel/locking/rwsem.c:1178
__down_write_common kernel/locking/rwsem.c:1306 [inline]
__down_write kernel/locking/rwsem.c:1315 [inline]
down_write+0x1a7/0x1f0 kernel/locking/rwsem.c:1574
inode_lock include/linux/fs.h:804 [inline]
open_last_lookups fs/namei.c:3561 [inline]
path_openat+0x7c6/0x3190 fs/namei.c:3794
do_filp_open+0x1c5/0x3d0 fs/namei.c:3824
do_sys_openat2+0x12c/0x1c0 fs/open.c:1421
do_sys_open fs/open.c:1436 [inline]
__do_sys_creat fs/open.c:1514 [inline]
__se_sys_creat fs/open.c:1508 [inline]
__x64_sys_creat+0x90/0xb0 fs/open.c:1508
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fb19798f749
RSP: 002b:00007fb198783038 EFLAGS: 00000246 ORIG_RAX: 0000000000000055
RAX: ffffffffffffffda RBX: 00007fb197be6270 RCX: 00007fb19798f749
RDX: 0000000000000000 RSI: 0000000000000194 RDI: 0000200000000100
RBP: 00007fb197a13f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fb197be6308 R14: 00007fb197be6270 R15: 00007ffca2b8db28
</TASK>
INFO: task syz.6.579:9022 blocked for more than 145 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.6.579 state:D stack:28584 pid:9022 ppid:7300 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5380 [inline]
__schedule+0x14d2/0x44d0 kernel/sched/core.c:6699
schedule+0xbd/0x170 kernel/sched/core.c:6773
schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:6832
rwsem_down_read_slowpath+0x4f8/0x840 kernel/locking/rwsem.c:1086
__down_read_common kernel/locking/rwsem.c:1250 [inline]
__down_read kernel/locking/rwsem.c:1263 [inline]
down_read+0x98/0x2e0 kernel/locking/rwsem.c:1522
inode_lock_shared include/linux/fs.h:814 [inline]
lookup_slow+0x46/0x70 fs/namei.c:1718
walk_component+0x2be/0x3f0 fs/namei.c:2010
lookup_last fs/namei.c:2467 [inline]
path_lookupat+0x169/0x440 fs/namei.c:2491
filename_lookup+0x1f4/0x510 fs/namei.c:2520
user_path_at_empty+0x42/0x60 fs/namei.c:2917
user_path_at include/linux/namei.h:57 [inline]
user_statfs+0x98/0x170 fs/statfs.c:103
__do_sys_statfs fs/statfs.c:195 [inline]
__se_sys_statfs fs/statfs.c:192 [inline]
__x64_sys_statfs+0xe1/0x1b0 fs/statfs.c:192
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fb19798f749
RSP: 002b:00007fb198762038 EFLAGS: 00000246 ORIG_RAX: 0000000000000089
RAX: ffffffffffffffda RBX: 00007fb197be6360 RCX: 00007fb19798f749
RDX: 0000000000000000 RSI: 0000200000000240 RDI: 0000200000000400
RBP: 00007fb197a13f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fb197be63f8 R14: 00007fb197be6360 R15: 00007ffca2b8db28
</TASK>
INFO: task syz.6.579:9024 blocked for more than 146 seconds.
Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.6.579 state:D stack:29000 pid:9024 ppid:7300 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5380 [inline]
__schedule+0x14d2/0x44d0 kernel/sched/core.c:6699
schedule+0xbd/0x170 kernel/sched/core.c:6773
schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:6832
rwsem_down_write_slowpath+0xbd2/0xfa0 kernel/locking/rwsem.c:1178
__down_write_common kernel/locking/rwsem.c:1306 [inline]
__down_write kernel/locking/rwsem.c:1315 [inline]
down_write_nested+0x1b1/0x1f0 kernel/locking/rwsem.c:1690
lock_rename include/linux/fs.h:-1 [inline]
do_renameat2+0x427/0xc70 fs/namei.c:4972
__do_sys_rename fs/namei.c:5079 [inline]
__se_sys_rename fs/namei.c:5077 [inline]
__x64_sys_rename+0x86/0x90 fs/namei.c:5077
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fb19798f749
RSP: 002b:00007fb198741038 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 00007fb197be6450 RCX: 00007fb19798f749
RDX: 0000000000000000 RSI: 0000200000000f40 RDI: 00002000000003c0
RBP: 00007fb197a13f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fb197be64e8 R14: 00007fb197be6450 R15: 00007ffca2b8db28
</TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/29:
#0: ffffffff8cd2ff20 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:334 [inline]
#0: ffffffff8cd2ff20 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:786 [inline]
#0: ffffffff8cd2ff20 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x55/0x290 kernel/locking/lockdep.c:6633
2 locks held by getty/5527:
#0: ffff88802cd1c0a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
#1: ffffc9000328b2f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x425/0x1380 drivers/tty/n_tty.c:2217
2 locks held by kworker/0:4/5810:
#0: ffff888017872538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2609 [inline]
#0: ffff888017872538 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_scheduled_works+0x957/0x15b0 kernel/workqueue.c:2711
#1: ffffc9000496fd00 ((work_completion)(&rew->rew_work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2609 [inline]
#1: ffffc9000496fd00 ((work_completion)(&rew->rew_work)){+.+.}-{0:0}, at: process_scheduled_works+0x957/0x15b0 kernel/workqueue.c:2711
3 locks held by kworker/u4:9/6029:
#0: ffff88802c59f138 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2609 [inline]
#0: ffff88802c59f138 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_scheduled_works+0x957/0x15b0 kernel/workqueue.c:2711
#1: ffffc9000bd8fd00 ((work_completion)(&(&net->ipv6.addr_chk_work)->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2609 [inline]
#1: ffffc9000bd8fd00 ((work_completion)(&(&net->ipv6.addr_chk_work)->work)){+.+.}-{0:0}, at: process_scheduled_works+0x957/0x15b0 kernel/workqueue.c:2711
#2: ffffffff8dfb5448 (rtnl_mutex){+.+.}-{3:3}, at: addrconf_verify_work+0x19/0x30 net/ipv6/addrconf.c:4700
4 locks held by kworker/u4:11/6860:
#0: ffff88801d67d138 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2609 [inline]
#0: ffff88801d67d138 ((wq_completion)writeback){+.+.}-{0:0}, at: process_scheduled_works+0x957/0x15b0 kernel/workqueue.c:2711
#1: ffffc9000464fd00 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2609 [inline]
#1: ffffc9000464fd00 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_scheduled_works+0x957/0x15b0 kernel/workqueue.c:2711
#2: ffff8880581520e0 (&type->s_umount_key#55){++++}-{3:3}, at: super_trylock_shared+0x20/0xf0 fs/super.c:607
#3: ffff88805f714bc8 (&jfs_ip->commit_mutex){+.+.}-{3:3}, at: jfs_commit_inode+0x1cb/0x520 fs/jfs/inode.c:108
4 locks held by syz.6.579/8999:
2 locks held by syz.6.579/9020:
#0: ffff888058152418 (sb_writers#14){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:412
#1: ffff88805f714f90 (&type->i_mutex_dir_key#10/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:839 [inline]
#1: ffff88805f714f90 (&type->i_mutex_dir_key#10/1){+.+.}-{3:3}, at: filename_create+0x1f6/0x460 fs/namei.c:3890
2 locks held by syz.6.579/9021:
#0: ffff888058152418 (sb_writers#14){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:412
#1: ffff88805f714f90 (&type->i_mutex_dir_key#10){++++}-{3:3}, at: inode_lock include/linux/fs.h:804 [inline]
#1: ffff88805f714f90 (&type->i_mutex_dir_key#10){++++}-{3:3}, at: open_last_lookups fs/namei.c:3561 [inline]
#1: ffff88805f714f90 (&type->i_mutex_dir_key#10){++++}-{3:3}, at: path_openat+0x7c6/0x3190 fs/namei.c:3794
1 lock held by syz.6.579/9022:
#0: ffff88805f714f90 (&type->i_mutex_dir_key#10){++++}-{3:3}, at: inode_lock_shared include/linux/fs.h:814 [inline]
#0: ffff88805f714f90 (&type->i_mutex_dir_key#10){++++}-{3:3}, at: lookup_slow+0x46/0x70 fs/namei.c:1718
2 locks held by syz.6.579/9024:
#0: ffff888058152418 (sb_writers#14){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:412
#1: ffff88805f714f90 (&type->i_mutex_dir_key#10/1){+.+.}-{3:3}, at: lock_rename include/linux/fs.h:-1 [inline]
#1: ffff88805f714f90 (&type->i_mutex_dir_key#10/1){+.+.}-{3:3}, at: do_renameat2+0x427/0xc70 fs/namei.c:4972
2 locks held by syz.2.812/9970:
#0: ffff8880581520e0 (&type->s_umount_key#55){++++}-{3:3}, at: __super_lock fs/super.c:58 [inline]
#0: ffff8880581520e0 (&type->s_umount_key#55){++++}-{3:3}, at: super_lock+0x167/0x360 fs/super.c:117
#1: ffff88802164e7d0 (&bdi->wb_switch_rwsem){+.+.}-{3:3}, at: bdi_down_write_wb_switch_rwsem fs/fs-writeback.c:364 [inline]
#1: ffff88802164e7d0 (&bdi->wb_switch_rwsem){+.+.}-{3:3}, at: sync_inodes_sb+0x1a0/0x9e0 fs/fs-writeback.c:2770
1 lock held by syz-executor/10128:
#0: ffffffff8dfb5448 (rtnl_mutex){+.+.}-{3:3}, at: tun_detach drivers/net/tun.c:698 [inline]
#0: ffffffff8dfb5448 (rtnl_mutex){+.+.}-{3:3}, at: tun_chr_close+0x41/0x1c0 drivers/net/tun.c:3511
1 lock held by syz.7.898/10329:
#0: ffffffff8dfb5448 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:78 [inline]
#0: ffffffff8dfb5448 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x76f/0xf10 net/core/rtnetlink.c:6469

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

NMI backtrace for cpu 1
CPU: 1 PID: 29 Comm: khungtaskd Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
Call Trace:
<TASK>
dump_stack_lvl+0x16c/0x230 lib/dump_stack.c:106
nmi_cpu_backtrace+0x39b/0x3d0 lib/nmi_backtrace.c:113
nmi_trigger_cpumask_backtrace+0x17a/0x2f0 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:160 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:222 [inline]
watchdog+0xf41/0xf80 kernel/hung_task.c:379
kthread+0x2fa/0x390 kernel/kthread.c:388
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
</TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 8999 Comm: syz.6.579 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
RIP: 0010:preempt_count arch/x86/include/asm/preempt.h:27 [inline]
RIP: 0010:check_kcov_mode kernel/kcov.c:182 [inline]
RIP: 0010:__sanitizer_cov_trace_pc+0x10/0x60 kernel/kcov.c:216
Code: 89 fb e8 13 00 00 00 48 8b 3d 9c 92 c4 0c 48 89 de 5b e9 43 9d 56 00 cc cc cc f3 0f 1e fa 48 8b 04 24 65 48 8b 0d f0 24 7e 7e <65> 8b 15 f1 24 7e 7e 81 e2 00 01 ff 00 74 11 81 fa 00 01 00 00 75
RSP: 0018:ffffc90004d6f320 EFLAGS: 00000246
RAX: ffffffff82feee6a RBX: 0000000000000004 RCX: ffff88802b7c1e00
RDX: ffff88802b7c1e00 RSI: 0000000000000000 RDI: 00000000000000ff
RBP: 0000000000000000 R08: 0000000200000000 R09: 0000000000000000
R10: 00300065006c0069 R11: 006605ff00000020 R12: dffffc0000000000
R13: ffff88807684b000 R14: 0000000000000000 R15: 1ffff1100ed09602
FS: 00007fb1987e66c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055556a3655c8 CR3: 000000005df3d000 CR4: 00000000003506f0
Call Trace:
<TASK>
dtSplitRoot+0x77a/0x16b0 fs/jfs/jfs_dtree.c:1979
dtSplitUp fs/jfs/jfs_dtree.c:993 [inline]
dtInsert+0xeec/0x5f40 fs/jfs/jfs_dtree.c:871
jfs_create+0x6a1/0xa40 fs/jfs/namei.c:137
lookup_open fs/namei.c:3496 [inline]
open_last_lookups fs/namei.c:3564 [inline]
path_openat+0x1277/0x3190 fs/namei.c:3794
do_filp_open+0x1c5/0x3d0 fs/namei.c:3824
do_sys_openat2+0x12c/0x1c0 fs/open.c:1421
do_sys_open fs/open.c:1436 [inline]
__do_sys_creat fs/open.c:1514 [inline]
__se_sys_creat fs/open.c:1508 [inline]
__x64_sys_creat+0x90/0xb0 fs/open.c:1508
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fb19798f749
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fb1987e6038 EFLAGS: 00000246 ORIG_RAX: 0000000000000055
RAX: ffffffffffffffda RBX: 00007fb197be5fa0 RCX: 00007fb19798f749
RDX: 0000000000000000 RSI: 000000000000001b RDI: 0000200000000580
RBP: 00007fb197a13f91 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fb197be6038 R14: 00007fb197be5fa0 R15: 00007ffca2b8db28
</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