syzbot


INFO: task hung in vfs_rename (2)

Status: auto-obsoleted due to no activity on 2025/12/04 18:25
Subsystems: fs
[Documentation on labels]
Reported-by: syzbot+321477fad98ea6dd35b7@syzkaller.appspotmail.com
First crash: 232d, last: 110d
Cause bisection: failed (error log, bisect log)
  
Fix bisection: failed (error log, bisect log)
  
Discussions (3)
Title Replies (including bot) Last reply
[syzbot] [fs?] INFO: task hung in vfs_rename (2) 4 (6) 2025/07/23 08:38
[PATCH] fs: Additional checks on new and old dir 4 (4) 2025/05/20 17:17
Re: [syzbot] [fs?] INFO: task hung in vfs_rename (2) 1 (1) 2025/04/24 19:51
Similar bugs (3)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 INFO: task hung in vfs_rename 1 1 573d 573d 0/3 auto-obsoleted due to no activity on 2024/08/20 18:33
upstream INFO: task hung in vfs_rename bcachefs 1 80 331d 446d 0/29 auto-obsoleted due to no activity on 2025/03/20 07:53
linux-5.15 INFO: task hung in vfs_rename (2) 1 2 439d 440d 0/3 auto-obsoleted due to no activity on 2025/01/01 05:06
Last patch testing requests (6)
Created Duration User Patch Repo Result
2025/12/04 17:55 28m retest repro upstream OK log
2025/09/10 17:26 15m retest repro upstream report log
2025/06/07 14:44 16m retest repro upstream report log
2025/05/13 12:00 1h53m eadavis@qq.com patch upstream OK log
2025/04/24 11:06 16m hdanton@sina.com patch upstream report log
2025/04/23 11:05 1h33m hdanton@sina.com patch upstream report log

Sample crash report:
INFO: task syz.3.199:8309 blocked for more than 143 seconds.
      Tainted: G        W           6.17.0-rc2-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.3.199       state:D stack:17448 pid:8309  tgid:8307  ppid:7618   task_flags:0x400140 flags:0x00004004
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5357 [inline]
 __schedule+0x16f3/0x4c20 kernel/sched/core.c:6961
 __schedule_loop kernel/sched/core.c:7043 [inline]
 rt_mutex_schedule+0x77/0xf0 kernel/sched/core.c:7339
 rt_mutex_slowlock_block kernel/locking/rtmutex.c:1647 [inline]
 __rt_mutex_slowlock kernel/locking/rtmutex.c:1721 [inline]
 __rt_mutex_slowlock_locked+0x1e04/0x25e0 kernel/locking/rtmutex.c:1760
 rt_mutex_slowlock+0xb5/0x160 kernel/locking/rtmutex.c:1800
 __rt_mutex_lock kernel/locking/rtmutex.c:1815 [inline]
 rwbase_write_lock+0x14f/0x750 kernel/locking/rwbase_rt.c:244
 vfs_rename+0x6d8/0xf00 fs/namei.c:5100
 do_renameat2+0x6ce/0xa80 fs/namei.c:5278
 __do_sys_renameat2 fs/namei.c:5312 [inline]
 __se_sys_renameat2 fs/namei.c:5309 [inline]
 __x64_sys_renameat2+0xce/0xe0 fs/namei.c:5309
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f660836ebe9
RSP: 002b:00007f66065ce038 EFLAGS: 00000246 ORIG_RAX: 000000000000013c
RAX: ffffffffffffffda RBX: 00007f6608595fa0 RCX: 00007f660836ebe9
RDX: ffffffffffffff9c RSI: 0000200000000080 RDI: ffffffffffffff9c
RBP: 00007f66083f1e19 R08: 0000000000000004 R09: 0000000000000000
R10: 00002000000003c0 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f6608596038 R14: 00007f6608595fa0 R15: 00007fff9479da08
 </TASK>
INFO: lockdep is turned off.
NMI backtrace for cpu 1
CPU: 1 UID: 0 PID: 39 Comm: khungtaskd Tainted: G        W           6.17.0-rc2-syzkaller #0 PREEMPT_{RT,(full)} 
Tainted: [W]=WARN
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
Call Trace:
 <TASK>
 dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120
 nmi_cpu_backtrace+0x39e/0x3d0 lib/nmi_backtrace.c:113
 nmi_trigger_cpumask_backtrace+0x17a/0x300 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:160 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:328 [inline]
 watchdog+0xf93/0xfe0 kernel/hung_task.c:491
 kthread+0x711/0x8a0 kernel/kthread.c:463
 ret_from_fork+0x3fc/0x770 arch/x86/kernel/process.c:148
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 UID: 0 PID: 10579 Comm: syz-executor Tainted: G        W           6.17.0-rc2-syzkaller #0 PREEMPT_{RT,(full)} 
Tainted: [W]=WARN
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
RIP: 0010:__sanitizer_cov_trace_const_cmp8+0x0/0xa0 kernel/kcov.c:320
Code: 00 00 48 89 7c 0a 10 48 89 74 0a 18 48 89 44 0a 20 e9 54 5f 3b 09 cc 0f 1f 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 <f3> 0f 1e fa 48 8b 04 24 65 48 8b 0c 25 08 b0 f5 91 65 44 8b 05 77
RSP: 0018:ffffc90005fb73a8 EFLAGS: 00000246
RAX: 000000ffffffffff RBX: 800000005743b007 RCX: ffff888034820000
RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000000
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: fffff940002ba1d9 R12: 0000000000000000
R13: 0000000000000000 R14: 000000000005743b R15: 0000000000000001
FS:  000055555aa76500(0000) GS:ffff8881268c5000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f9fe0db59f0 CR3: 000000005862e000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 pte_write arch/x86/include/asm/pgtable.h:218 [inline]
 __page_table_check_ptes_set+0x24e/0x2f0 mm/page_table_check.c:209
 page_table_check_ptes_set include/linux/page_table_check.h:76 [inline]
 set_ptes include/linux/pgtable.h:292 [inline]
 __copy_present_ptes mm/memory.c:972 [inline]
 copy_present_ptes mm/memory.c:1051 [inline]
 copy_pte_range mm/memory.c:1174 [inline]
 copy_pmd_range+0x3f84/0x6ab0 mm/memory.c:1261
 copy_pud_range mm/memory.c:1298 [inline]
 copy_p4d_range mm/memory.c:1322 [inline]
 copy_page_range+0xaff/0x1170 mm/memory.c:1410
 dup_mmap+0xf63/0x1a90 mm/mmap.c:1834
 dup_mm kernel/fork.c:1485 [inline]
 copy_mm+0x13c/0x4b0 kernel/fork.c:1537
 copy_process+0x1704/0x3ae0 kernel/fork.c:2175
 kernel_clone+0x224/0x7c0 kernel/fork.c:2605
 __do_sys_clone kernel/fork.c:2748 [inline]
 __se_sys_clone kernel/fork.c:2732 [inline]
 __x64_sys_clone+0x18b/0x1e0 kernel/fork.c:2732
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f42fdaf5453
Code: 1f 84 00 00 00 00 00 64 48 8b 04 25 10 00 00 00 45 31 c0 31 d2 31 f6 bf 11 00 20 01 4c 8d 90 d0 02 00 00 b8 38 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 35 89 c2 85 c0 75 2c 64 48 8b 04 25 10 00 00
RSP: 002b:00007ffc773ae578 EFLAGS: 00000246 ORIG_RAX: 0000000000000038
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f42fdaf5453
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000001200011
RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000001
R10: 000055555aa767d0 R11: 0000000000000246 R12: 0000000000000000
R13: 00000000000927c0 R14: 0000000000060dce R15: 00007ffc773ae710
 </TASK>

Crashes (15):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/08/18 22:21 upstream c17b750b3ad9 1804e95e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in vfs_rename
2025/08/17 01:01 upstream 90d970cade8e 1804e95e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in vfs_rename
2025/07/18 08:32 upstream 6832a9317eee 88248e14 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in vfs_rename
2025/07/09 07:46 upstream 733923397fd9 4d9fdfa4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in vfs_rename
2025/06/21 14:58 upstream 11313e2f7812 d6cdfb8a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in vfs_rename
2025/06/17 08:03 upstream 9afe652958c3 cfebc887 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in vfs_rename
2025/05/24 13:09 upstream 4856ebd99715 ed351ea7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in vfs_rename
2025/05/16 15:47 upstream fee3e843b309 cfde8269 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in vfs_rename
2025/05/02 14:41 upstream ebd297a2affa d7f099d1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in vfs_rename
2025/04/29 04:57 upstream f15d97df5afa aeb6ec69 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in vfs_rename
2025/04/29 01:15 upstream f15d97df5afa aeb6ec69 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in vfs_rename
2025/04/27 20:02 upstream 5bc1018675ec c6b4fb39 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in vfs_rename
2025/04/19 08:15 upstream 3088d26962e8 2a20f901 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in vfs_rename
2025/04/18 21:19 upstream fc96b232f8e7 2a20f901 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs INFO: task hung in vfs_rename
2025/04/18 16:12 upstream fc96b232f8e7 2a20f901 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in vfs_rename
* Struck through repros no longer work on HEAD.