syzbot


INFO: task hung in do_renameat2 (2)

Status: upstream: reported C repro on 2024/05/06 01:51
Subsystems: ext4
[Documentation on labels]
Reported-by: syzbot+39a12f7473ed8066d2ca@syzkaller.appspotmail.com
First crash: 556d, last: 5d12h
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 (4)
Title Replies (including bot) Last reply
[syzbot] Monthly ext4 report (Jun 2025) 0 (1) 2025/06/26 05:37
[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 171d 409d 0/3 auto-obsoleted due to no activity on 2025/04/16 19:25
linux-6.1 INFO: task hung in do_renameat2 1 514d 514d 0/3 auto-obsoleted due to no activity on 2024/05/09 03:01
upstream INFO: task hung in do_renameat2 f2fs 2 660d 695d 0/29 auto-obsoleted due to no activity on 2023/12/04 15:30
linux-6.1 INFO: task hung in do_renameat2 (2) 1 408d 408d 0/3 auto-obsoleted due to no activity on 2024/08/22 17:29

Sample crash report:
INFO: task syz-executor211:5857 blocked for more than 143 seconds.
      Not tainted 6.15.0-syzkaller-10820-gcd2e103d57e5 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor211 state:D stack:28856 pid:5857  tgid:5852  ppid:5849   task_flags:0x400040 flags:0x00004006
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5392 [inline]
 __schedule+0x16a2/0x4cb0 kernel/sched/core.c:6781
 __schedule_loop kernel/sched/core.c:6859 [inline]
 schedule+0x165/0x360 kernel/sched/core.c:6874
 schedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:6931
 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:912 [inline]
 lock_rename fs/namei.c:3272 [inline]
 do_renameat2+0x3dd/0xc50 fs/namei.c:5223
 __do_sys_rename fs/namei.c:5324 [inline]
 __se_sys_rename fs/namei.c:5322 [inline]
 __x64_sys_rename+0x82/0x90 fs/namei.c:5322
 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:0x7f8632293739
RSP: 002b:00007f8632226168 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 00007f863231a6d8 RCX: 00007f8632293739
RDX: 00007f863226cdf6 RSI: 0000200000000180 RDI: 00002000000003c0
RBP: 00007f863231a6d0 R08: 00007fffd7fce227 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007f863231a6dc
R13: 000000000000006e R14: 00007fffd7fce140 R15: 00007fffd7fce228
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/31:
 #0: ffffffff8e13d080 (rcu_read_lock){....}-{1:3}, at: rcu_lock_acquire include/linux/rcupdate.h:331 [inline]
 #0: ffffffff8e13d080 (rcu_read_lock){....}-{1:3}, at: rcu_read_lock include/linux/rcupdate.h:841 [inline]
 #0: ffffffff8e13d080 (rcu_read_lock){....}-{1:3}, at: debug_show_all_locks+0x2e/0x180 kernel/locking/lockdep.c:6770
2 locks held by getty/5580:
 #0: ffff8880352820a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: ffffc9000332b2f0 (&ldata->atomic_read_lock){+.+.}-{4:4}, at: n_tty_read+0x43e/0x1400 drivers/tty/n_tty.c:2222
3 locks held by syz-executor211/5853:
2 locks held by syz-executor211/5857:
 #0: ffff888071d28428 (sb_writers#4){.+.+}-{0:0}, at: mnt_want_write+0x41/0x90 fs/namespace.c:557
 #1: ffff88807dc83d40 (&type->i_mutex_dir_key#3/1){+.+.}-{4:4}, at: inode_lock_nested include/linux/fs.h:912 [inline]
 #1: ffff88807dc83d40 (&type->i_mutex_dir_key#3/1){+.+.}-{4:4}, at: lock_rename fs/namei.c:3272 [inline]
 #1: ffff88807dc83d40 (&type->i_mutex_dir_key#3/1){+.+.}-{4:4}, at: do_renameat2+0x3dd/0xc50 fs/namei.c:5223

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

NMI backtrace for cpu 0
CPU: 0 UID: 0 PID: 31 Comm: khungtaskd Not tainted 6.15.0-syzkaller-10820-gcd2e103d57e5 #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:307 [inline]
 watchdog+0xfee/0x1030 kernel/hung_task.c:470
 kthread+0x711/0x8a0 kernel/kthread.c:464
 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 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 UID: 0 PID: 5853 Comm: syz-executor211 Not tainted 6.15.0-syzkaller-10820-gcd2e103d57e5 #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
RIP: 0010:errseq_check+0x47/0x80 lib/errseq.c:153
Code: 00 00 00 fc ff df 0f b6 04 08 84 c0 75 32 41 8b 2e 89 ef 89 de e8 69 57 07 fd 39 dd 75 13 e8 a0 55 07 fd 31 ed 89 e8 5b 41 5e <5d> e9 d3 55 a7 06 cc e8 8d 55 07 fd 81 e5 ff 0f 00 00 f7 dd eb e5
RSP: 0018:ffffc9000456f530 EFLAGS: 00000246
RAX: 0000000000000000 RBX: ffff888148c94ea8 RCX: ffff888072668000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffff88807dfaa1d0 R09: 0000000000000001
R10: dffffc0000000000 R11: fffffbfff1f3f25f R12: ffff888071d28000
R13: ffff88807229c000 R14: ffff88807229cbd0 R15: dffffc0000000000
FS:  00007f86322476c0(0000) GS:ffff888125d95000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000056397f7d0660 CR3: 000000007432e000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 ext4_check_bdev_write_error fs/ext4/ext4_jbd2.c:222 [inline]
 __ext4_journal_get_write_access+0x138/0x570 fs/ext4/ext4_jbd2.c:249
 ext4_xattr_block_set+0x12f3/0x2ac0 fs/ext4/xattr.c:2053
 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/0x3c50 fs/ext4/ialloc.c:1325
 ext4_create+0x22d/0x460 fs/ext4/namei.c:2822
 vfs_create+0x24b/0x400 fs/namei.c:3405
 do_mknodat+0x3c6/0x4d0 fs/namei.c:4285
 __do_sys_mknodat fs/namei.c:4313 [inline]
 __se_sys_mknodat fs/namei.c:4310 [inline]
 __x64_sys_mknodat+0xa7/0xc0 fs/namei.c:4310
 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:0x7f8632293739
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:00007f8632247168 EFLAGS: 00000246 ORIG_RAX: 0000000000000103
RAX: ffffffffffffffda RBX: 00007f863231a6c8 RCX: 00007f8632293739
RDX: 0000000000000400 RSI: 0000200000000180 RDI: 0000000000000004
RBP: 00007f863231a6c0 R08: 00007f86322476c0 R09: 0000000000000000
R10: 0000000000000103 R11: 0000000000000246 R12: 00007f863231a6cc
R13: 0000000000000006 R14: 00007fffd7fce140 R15: 00007fffd7fce228
 </TASK>

Crashes (232):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/06/02 08:49 upstream cd2e103d57e5 3d2f584d .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/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/06/22 01:58 upstream 3f75bfff44be d6cdfb8a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2025/06/19 22:21 upstream 24770983ccfe ed3e87f7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2025/06/15 17:27 upstream 8c6bc74c7f89 5f4b362d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2025/06/07 06:08 upstream c0c9379f235d 4826c28e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2025/05/28 18:07 upstream 3d413f0cfd7e 3d2f584d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2025/05/28 08:35 upstream feacb1774bd5 874a1386 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2025/05/26 00:31 upstream 0f8c0258bf04 2d4582d0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2025/05/22 21:13 upstream 5cdb2c77c4c3 0919b50b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2025/05/22 09:44 upstream d608703fcdd9 0919b50b .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2025/05/19 22:17 upstream a5806cd506af b84f0537 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2025/05/13 23:29 upstream e9565e23cd89 7344edeb .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in do_renameat2
2025/05/13 07:42 upstream 627277ba7c23 f6671af7 .config console log report info [disk image] [vmlinux] [kernel image] 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
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/06/01 23:06 linux-next 3a83b350b5be 3d2f584d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root 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/06/16 14:04 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 39dfc971e42d d1716036 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in do_renameat2
2025/06/04 14:22 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci d7fa1af5b33e fd5e6e61 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 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.