syzbot


INFO: task hung in do_renameat2 (2)

Status: upstream: reported C repro on 2024/05/06 01:51
Subsystems: bcachefs
[Documentation on labels]
Reported-by: syzbot+39a12f7473ed8066d2ca@syzkaller.appspotmail.com
First crash: 510d, last: 57m
Cause bisection: the cause commit could be any of (bisect log):
  7e170922f06b ext4: Add allocation criteria 1.5 (CR1_5)
  f52f3d2b9fba ext4: Give symbolic names to mballoc criterias
  
Discussions (3)
Title Replies (including bot) Last reply
[syzbot] [bcachefs?] [kernfs?] INFO: task hung in do_renameat2 (2) 0 (2) 2025/02/04 13:33
[syzbot] Monthly kernfs report (Aug 2024) 0 (1) 2024/08/13 12:33
[syzbot] Monthly kernfs report (May 2024) 0 (1) 2024/05/08 08:25
Similar bugs (4)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 INFO: task hung in do_renameat2 origin:lts-only C done 6 125d 363d 0/3 auto-obsoleted due to no activity on 2025/04/16 19:25
linux-6.1 INFO: task hung in do_renameat2 1 468d 468d 0/3 auto-obsoleted due to no activity on 2024/05/09 03:01
upstream INFO: task hung in do_renameat2 f2fs 2 614d 648d 0/28 auto-obsoleted due to no activity on 2023/12/04 15:30
linux-6.1 INFO: task hung in do_renameat2 (2) 1 362d 362d 0/3 auto-obsoleted due to no activity on 2024/08/22 17:29

Sample crash report:
INFO: task syz-executor413:5827 blocked for more than 143 seconds.
      Not tainted 6.15.0-rc5-syzkaller-00204-g0e1329d4045c #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor413 state:D stack:28888 pid:5827  tgid:5821  ppid:5820   task_flags:0x400040 flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5382 [inline]
 __schedule+0x168f/0x4c70 kernel/sched/core.c:6767
 __schedule_loop kernel/sched/core.c:6845 [inline]
 schedule+0x165/0x360 kernel/sched/core.c:6860
 schedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:6917
 rwsem_down_write_slowpath+0xbec/0x1030 kernel/locking/rwsem.c:1176
 __down_write_common kernel/locking/rwsem.c:1304 [inline]
 __down_write kernel/locking/rwsem.c:1313 [inline]
 down_write_nested+0x1b5/0x200 kernel/locking/rwsem.c:1694
 inode_lock_nested include/linux/fs.h:902 [inline]
 lock_rename fs/namei.c:3265 [inline]
 do_renameat2+0x3dd/0xc50 fs/namei.c:5216
 __do_sys_rename fs/namei.c:5317 [inline]
 __se_sys_rename fs/namei.c:5315 [inline]
 __x64_sys_rename+0x82/0x90 fs/namei.c:5315
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xf6/0x210 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f4d09f58409
RSP: 002b:00007f4d09eeb168 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 00007f4d09fdf6b8 RCX: 00007f4d09f58409
RDX: 00007f4d09f31b56 RSI: 00002000000002c0 RDI: 0000200000000580
RBP: 00007f4d09fdf6b0 R08: 00007ffea48d8be7 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f4d09fdf6bc
R13: 000000000000006e R14: 00007ffea48d8b00 R15: 00007ffea48d8be8
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/31:
 #0: ffffffff8df3b860 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:331 [inline]
 #0: ffffffff8df3b860 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:841 [inline]
 #0: ffffffff8df3b860 (rcu_read_lock){....}-{1:3}, at: debug_show_all_locks+0x2e/0x180 kernel/locking/lockdep.c:6764
2 locks held by getty/5574:
 #0: ffff888034aa20a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: ffffc900033532f0 (&ldata->atomic_read_lock){+.+.}-{4:4}, at: n_tty_read+0x43e/0x1400 drivers/tty/n_tty.c:2222
3 locks held by syz-executor413/5823:
2 locks held by syz-executor413/5827:
 #0: ffff88802c30a420 (sb_writers#4){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:556
 #1: ffff88807bcfabd8 (&type->i_mutex_dir_key#3/1){+.+.}-{4:4}, at: inode_lock_nested include/linux/fs.h:902 [inline]
 #1: ffff88807bcfabd8 (&type->i_mutex_dir_key#3/1){+.+.}-{4:4}, at: lock_rename fs/namei.c:3265 [inline]
 #1: ffff88807bcfabd8 (&type->i_mutex_dir_key#3/1){+.+.}-{4:4}, at: do_renameat2+0x3dd/0xc50 fs/namei.c:5216

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

NMI backtrace for cpu 0
CPU: 0 UID: 0 PID: 31 Comm: khungtaskd Not tainted 6.15.0-rc5-syzkaller-00204-g0e1329d4045c #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/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:158 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:274 [inline]
 watchdog+0xfee/0x1030 kernel/hung_task.c:437
 kthread+0x70e/0x8a0 kernel/kthread.c:464
 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:153
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 UID: 0 PID: 5823 Comm: syz-executor413 Not tainted 6.15.0-rc5-syzkaller-00204-g0e1329d4045c #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:check_preemption_disabled+0x3/0x120 lib/smp_processor_id.c:13
Code: c0 8b 48 c7 c6 c0 fe c0 8b eb 1c 66 66 66 2e 0f 1f 84 00 00 00 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 55 41 57 <41> 56 53 48 83 ec 10 65 48 8b 05 4e ee 22 07 48 89 44 24 08 65 8b
RSP: 0018:ffffc90003fa6f88 EFLAGS: 00000046
RAX: 98d0f4957106d9ef RBX: 0000000000000202 RCX: cd0dc5490b8a1b00
RDX: 0000000000000003 RSI: ffffffff8d9213f3 RDI: ffffffff8bc0fee0
RBP: ffff88807d4f0b68 R08: ffff88807bccf1df R09: 1ffff1100f799e3b
R10: dffffc0000000000 R11: ffffed100f799e3c R12: 0000000000000003
R13: 0000000000000003 R14: ffff88807bccee40 R15: ffff88807d4f0000
FS:  00007f4d09f0c6c0(0000) GS:ffff888126200000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055de28bfa168 CR3: 000000002732c000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 lockdep_recursion_finish kernel/locking/lockdep.c:472 [inline]
 lock_release+0x27a/0x3e0 kernel/locking/lockdep.c:5889
 __raw_spin_unlock include/linux/spinlock_api_smp.h:141 [inline]
 _raw_spin_unlock+0x16/0x50 kernel/locking/spinlock.c:186
 spin_unlock include/linux/spinlock.h:391 [inline]
 ext4_do_update_inode fs/ext4/inode.c:5209 [inline]
 ext4_mark_iloc_dirty+0x55a/0x1ca0 fs/ext4/inode.c:5869
 __ext4_mark_inode_dirty+0x4be/0x700 fs/ext4/inode.c:6074
 ext4_dirty_inode+0xd0/0x110 fs/ext4/inode.c:6103
 __mark_inode_dirty+0x2ce/0xdf0 fs/fs-writeback.c:2527
 mark_inode_dirty include/linux/fs.h:2545 [inline]
 dquot_alloc_space include/linux/quotaops.h:319 [inline]
 dquot_alloc_block include/linux/quotaops.h:336 [inline]
 ext4_xattr_block_set+0x12ca/0x2ac0 fs/ext4/xattr.c:2048
 ext4_xattr_set_handle+0xdfb/0x1590 fs/ext4/xattr.c:2447
 ext4_initxattrs+0x9f/0x110 fs/ext4/xattr_security.c:44
 security_inode_init_security+0x29d/0x3f0 security/security.c:1852
 __ext4_new_inode+0x3257/0x3bd0 fs/ext4/ialloc.c:1326
 ext4_create+0x22d/0x460 fs/ext4/namei.c:2824
 lookup_open fs/namei.c:3701 [inline]
 open_last_lookups fs/namei.c:3800 [inline]
 path_openat+0x14f1/0x3830 fs/namei.c:4036
 do_filp_open+0x1fa/0x410 fs/namei.c:4066
 do_sys_openat2+0x121/0x1c0 fs/open.c:1429
 do_sys_open fs/open.c:1444 [inline]
 __do_sys_creat fs/open.c:1522 [inline]
 __se_sys_creat fs/open.c:1516 [inline]
 __x64_sys_creat+0x8f/0xc0 fs/open.c:1516
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xf6/0x210 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f4d09f58409
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 81 18 00 00 90 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f4d09f0c168 EFLAGS: 00000246 ORIG_RAX: 0000000000000055
RAX: ffffffffffffffda RBX: 00007f4d09fdf6a8 RCX: 00007f4d09f58409
RDX: ffffffffffffffb0 RSI: 0000000000000182 RDI: 0000200000000000
RBP: 00007f4d09fdf6a0 R08: 00007f4d09f0c6c0 R09: 0000000000000000
R10: 00007f4d09f0c6c0 R11: 0000000000000246 R12: 00007f4d09fdf6ac
R13: 0000000000000006 R14: 00007ffea48d8b00 R15: 00007ffea48d8be8
 </TASK>
INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to run: 1.341 msecs

Crashes (216):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/05/10 16:22 upstream 0e1329d4045c 77908e5f .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs INFO: task hung in do_renameat2
2025/02/04 13:33 upstream 0de63bb7d919 8f267cef .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs INFO: task hung in do_renameat2
2025/05/12 03:05 upstream cd802e7e5f1e 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2025/05/11 14:00 upstream 3ce9925823c7 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2025/05/06 21:01 upstream 0d8d44db295c 350f4ffc .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2025/05/06 09:36 upstream 01f95500a162 ae98e6b9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2025/05/01 15:53 upstream 4f79eaa2ceac 51b137cd .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2025/04/28 16:52 upstream b4432656b36e c6b4fb39 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in do_renameat2
2025/04/27 15:44 upstream 5bc1018675ec c6b4fb39 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2025/04/25 20:09 upstream 02ddfb981de8 c6b4fb39 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2025/04/25 00:33 upstream e72e9e693307 9882047a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2025/04/24 10:57 upstream a79be02bba5c 9882047a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2025/04/23 09:48 upstream bc3372351d0c 53a8b9bd .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2025/04/22 09:24 upstream a33b5a08cbbd 2a20f901 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2025/04/21 13:34 upstream 9d7a0577c9db 2a20f901 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2025/04/21 12:20 upstream 9d7a0577c9db 2a20f901 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2025/04/20 21:38 upstream 6fea5fabd332 2a20f901 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2025/04/20 07:04 upstream 119009db2674 2a20f901 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2025/04/10 13:34 upstream 3b07108ada81 988b336c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2025/03/26 10:32 upstream 2df0c02dab82 89d30d73 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2025/03/22 07:41 upstream d07de43e3f05 c6512ef7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2025/03/21 15:50 upstream b3ee1e460951 62330552 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2025/03/19 01:45 upstream 76b6905c11fd 22a6c2b1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2025/03/06 10:43 upstream bb2281fb05e5 831e3629 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2025/03/04 07:39 upstream 99fa936e8e4f c3901742 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2025/03/03 03:00 upstream b91872c56940 c3901742 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2025/03/02 09:57 upstream ece144f151ac c3901742 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2025/02/20 01:55 upstream 6537cfb395f3 b257a9b7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2025/02/15 01:54 upstream 128c8f96eb86 1022af74 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2025/02/04 09:37 upstream 0de63bb7d919 8f267cef .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2025/01/16 20:08 upstream ce69b4019001 f9e07a6e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2025/01/13 04:11 upstream be548645527a 6dbc6a9b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2025/01/06 09:09 upstream ab75170520d4 f3558dbf .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2025/01/05 22:38 upstream ab75170520d4 f3558dbf .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2024/12/31 22:26 upstream ccb98ccef0e5 d3ccff63 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in do_renameat2
2024/12/24 17:51 upstream f07044dd0df0 444551c4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2024/12/21 22:43 upstream 499551201b5f d7f584ee .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2024/12/20 13:06 upstream 8faabc041a00 1d58202c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in do_renameat2
2024/12/17 10:31 upstream f44d154d6e3d f93b2b55 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2024/12/17 04:24 upstream f44d154d6e3d eec85da6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2024/12/16 08:16 upstream 78d4f34e2115 7cbfbb3a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2024/12/08 09:12 upstream 7503345ac5f5 9ac0fdc6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2024/12/02 17:54 upstream e70140ba0d2b b499ea68 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2024/11/25 23:47 upstream 9f16d5e6f220 11dbc254 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2024/11/19 08:53 upstream 23acd177540d 571351cb .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2024/06/17 00:03 upstream 2ccbdf43d5e7 f429ab00 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in do_renameat2
2024/05/23 13:54 upstream 8f6a15f095a6 4d098039 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in do_renameat2
2024/05/05 02:55 upstream 7367539ad4b0 610f2a54 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2024/05/02 01:43 upstream 0106679839f7 3ba885bc .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2024/04/22 21:37 upstream ed30a4a51bb1 36c961ad .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2025/04/07 05:03 linux-next a4cda136f021 1c65791e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in do_renameat2
2025/02/26 03:14 linux-next e5d3fd687aac d34966d1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in do_renameat2
2025/01/12 17:35 linux-next 7b4b9bf203da 6dbc6a9b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in do_renameat2
2025/01/07 00:00 linux-next 8155b4ef3466 f3558dbf .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in do_renameat2
2024/12/31 09:51 linux-next 8155b4ef3466 d3ccff63 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in do_renameat2
2025/01/19 20:45 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 1950a0af2d55 f2cb035c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in do_renameat2
* Struck through repros no longer work on HEAD.