syzbot


INFO: task hung in lock_rename (6)

Status: auto-obsoleted due to no activity on 2023/07/28 16:10
Subsystems: ext4
[Documentation on labels]
First crash: 615d, last: 367d
Similar bugs (10)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in lock_rename (3) fs 1 1031d 1031d 0/26 auto-closed as invalid on 2021/10/02 18:08
linux-5.15 INFO: task hung in lock_rename 2 365d 397d 0/3 auto-obsoleted due to no activity on 2023/08/23 09:02
upstream INFO: task hung in lock_rename exfat 53 1977d 2112d 0/26 auto-closed as invalid on 2019/05/30 13:09
linux-6.1 INFO: task hung in lock_rename 3 220d 334d 0/3 auto-obsoleted due to no activity on 2024/01/01 05:54
upstream INFO: task hung in lock_rename (4) fs 3 820d 913d 0/26 closed as invalid on 2022/02/08 09:40
linux-4.19 INFO: task hung in lock_rename 1 843d 843d 0/1 auto-closed as invalid on 2022/05/08 10:15
upstream INFO: task hung in lock_rename (5) fs 2 775d 804d 0/26 auto-closed as invalid on 2022/06/15 04:15
upstream INFO: task hung in lock_rename (2) fs 7 1181d 1205d 0/26 auto-closed as invalid on 2021/05/17 09:31
linux-4.14 INFO: task hung in lock_rename 1 688d 688d 0/1 auto-obsoleted due to no activity on 2022/10/10 13:20
android-49 INFO: task hung in lock_rename C 9 2073d 1843d 0/3 public: reported C repro on 2019/04/14 00:00

Sample crash report:
INFO: task syz-executor.0:29110 blocked for more than 143 seconds.
      Not tainted 6.3.0-syzkaller-11025-g89d77f71f493 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.0  state:D stack:26952 pid:29110 ppid:5034   flags:0x00004004
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5343 [inline]
 __schedule+0xc9a/0x5880 kernel/sched/core.c:6669
 schedule+0xde/0x1a0 kernel/sched/core.c:6745
 schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:6804
 rwsem_down_write_slowpath+0x3e2/0x1220 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+0x1d6/0x200 kernel/locking/rwsem.c:1690
 inode_lock_nested include/linux/fs.h:796 [inline]
 lock_rename+0x1e4/0x280 fs/namei.c:3012
 do_renameat2+0x63d/0xc90 fs/namei.c:4864
 __do_sys_renameat2 fs/namei.c:4956 [inline]
 __se_sys_renameat2 fs/namei.c:4953 [inline]
 __x64_sys_renameat2+0xe8/0x120 fs/namei.c:4953
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f0402a8c169
RSP: 002b:00007f0403722168 EFLAGS: 00000246 ORIG_RAX: 000000000000013c
RAX: ffffffffffffffda RBX: 00007f0402bac050 RCX: 00007f0402a8c169
RDX: 0000000000000004 RSI: 00000000200002c0 RDI: 0000000000000004
RBP: 00007f0402ae7ca1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000020000180 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fffe62b28df R14: 00007f0403722300 R15: 0000000000022000
 </TASK>
INFO: task syz-executor.0:29115 blocked for more than 143 seconds.
      Not tainted 6.3.0-syzkaller-11025-g89d77f71f493 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.0  state:D stack:28912 pid:29115 ppid:5034   flags:0x00000004
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5343 [inline]
 __schedule+0xc9a/0x5880 kernel/sched/core.c:6669
 schedule+0xde/0x1a0 kernel/sched/core.c:6745
 schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:6804
 rwsem_down_write_slowpath+0x3e2/0x1220 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+0x1d6/0x200 kernel/locking/rwsem.c:1690
 inode_lock_nested include/linux/fs.h:796 [inline]
 ext4_rename+0x1593/0x2790 fs/ext4/namei.c:3821
 ext4_rename2+0x1c7/0x270 fs/ext4/namei.c:4200
 vfs_rename+0xef6/0x17a0 fs/namei.c:4772
 do_renameat2+0xb62/0xc90 fs/namei.c:4923
 __do_sys_rename fs/namei.c:4969 [inline]
 __se_sys_rename fs/namei.c:4967 [inline]
 __x64_sys_rename+0x81/0xa0 fs/namei.c:4967
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f0402a8c169
RSP: 002b:00007f0403701168 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 00007f0402bac120 RCX: 00007f0402a8c169
RDX: 0000000000000000 RSI: 00000000200000c0 RDI: 0000000020000200
RBP: 00007f0402ae7ca1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fffe62b28df R14: 00007f0403701300 R15: 0000000000022000
 </TASK>

Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/13:
 #0: ffffffff8c7993b0 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x31/0xd80 kernel/rcu/tasks.h:518
1 lock held by rcu_tasks_trace/14:
 #0: ffffffff8c7990b0 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x31/0xd80 kernel/rcu/tasks.h:518
1 lock held by khungtaskd/27:
 #0: ffffffff8c799fc0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x55/0x340 kernel/locking/lockdep.c:6545
2 locks held by getty/4749:
 #0: ffff888028a01098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x26/0x80 drivers/tty/tty_ldisc.c:243
 #1: ffffc900015b02f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0xef4/0x13e0 drivers/tty/n_tty.c:2176
2 locks held by syz-fuzzer/4991:
 #0: ffff888029aeb9e8 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0xe7/0x100 fs/file.c:1047
 #1: ffff8880902af200 (&type->i_mutex_dir_key#3){++++}-{3:3}, at: iterate_dir+0xd1/0x6f0 fs/readdir.c:55
2 locks held by kworker/u4:28/11012:
 #0: ffff8880b993c5d8 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x2f/0x120 kernel/sched/core.c:558
 #1: ffff8880b9928848 (&per_cpu_ptr(group->pcpu, cpu)->seq){-.-.}-{0:0}, at: psi_task_switch+0x216/0x950 kernel/sched/psi.c:984
4 locks held by syz-executor.0/29110:
 #0: ffff88802cb14460 (sb_writers#4){.+.+}-{0:0}, at: do_renameat2+0x37f/0xc90 fs/namei.c:4859
 #1: ffff88802cb14748 (&type->s_vfs_rename_key#2){+.+.}-{3:3}, at: lock_rename+0x58/0x280 fs/namei.c:2995
 #2: ffff88808c392c00 (&type->i_mutex_dir_key#3/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:796 [inline]
 #2: ffff88808c392c00 (&type->i_mutex_dir_key#3/1){+.+.}-{3:3}, at: lock_rename+0x1b0/0x280 fs/namei.c:3011
 #3: ffff88809035a200 (&type->i_mutex_dir_key#3/5){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:796 [inline]
 #3: ffff88809035a200 (&type->i_mutex_dir_key#3/5){+.+.}-{3:3}, at: lock_rename+0x1e4/0x280 fs/namei.c:3012
4 locks held by syz-executor.0/29115:
 #0: ffff88802cb14460 (sb_writers#4){.+.+}-{0:0}, at: do_renameat2+0x37f/0xc90 fs/namei.c:4859
 #1: ffff8880902af200 (&type->i_mutex_dir_key#3/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:796 [inline]
 #1: ffff8880902af200 (&type->i_mutex_dir_key#3/1){+.+.}-{3:3}, at: lock_rename+0x229/0x280 fs/namei.c:2991
 #2: ffff88809035a200 (&type->i_mutex_dir_key#3){++++}-{3:3}, at: inode_lock include/linux/fs.h:761 [inline]
 #2: ffff88809035a200 (&type->i_mutex_dir_key#3){++++}-{3:3}, at: vfs_rename+0x4f9/0x17a0 fs/namei.c:4744
 #3: ffff88808c392c00 (&type->i_mutex_dir_key#3/4){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:796 [inline]
 #3: ffff88808c392c00 (&type->i_mutex_dir_key#3/4){+.+.}-{3:3}, at: ext4_rename+0x1593/0x2790 fs/ext4/namei.c:3821

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

NMI backtrace for cpu 0
CPU: 0 PID: 27 Comm: khungtaskd Not tainted 6.3.0-syzkaller-11025-g89d77f71f493 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/2023
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xd9/0x150 lib/dump_stack.c:106
 nmi_cpu_backtrace+0x29c/0x350 lib/nmi_backtrace.c:113
 nmi_trigger_cpumask_backtrace+0x2a4/0x300 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:222 [inline]
 watchdog+0xe16/0x1090 kernel/hung_task.c:379
 kthread+0x344/0x440 kernel/kthread.c:379
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
 </TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 11012 Comm: kworker/u4:28 Not tainted 6.3.0-syzkaller-11025-g89d77f71f493 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/2023
Workqueue: events_unbound toggle_allocation_gate
RIP: 0010:write_comp_data+0x3f/0x90 kernel/kcov.c:236
Code: 49 89 f8 65 48 8b 14 25 c0 bb 03 00 a9 00 01 ff 00 74 0e 85 f6 74 59 8b 82 0c 16 00 00 85 c0 74 4f 8b 82 e8 15 00 00 83 f8 03 <75> 44 48 8b 82 f0 15 00 00 8b 92 ec 15 00 00 48 8b 38 48 c1 e2 03
RSP: 0018:ffffc90005d47938 EFLAGS: 00000293
RAX: 0000000000000000 RBX: ffff8880b98451e0 RCX: ffffffff81790eb3
RDX: ffff88807b225940 RSI: 0000000000000000 RDI: 0000000000000005
RBP: 0000000000000003 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000000 R12: ffffed1017308a3d
R13: 0000000000000000 R14: dffffc0000000000 R15: 0000000000000001
FS:  0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055620e21e680 CR3: 000000000c572000 CR4: 0000000000350ee0
Call Trace:
 <TASK>
 csd_lock_wait kernel/smp.c:285 [inline]
 smp_call_function_many_cond+0x6a3/0x15a0 kernel/smp.c:828
 on_each_cpu_cond_mask+0x5a/0xa0 kernel/smp.c:996
 on_each_cpu include/linux/smp.h:71 [inline]
 text_poke_sync arch/x86/kernel/alternative.c:1770 [inline]
 text_poke_bp_batch+0x634/0x770 arch/x86/kernel/alternative.c:2053
 text_poke_flush arch/x86/kernel/alternative.c:2161 [inline]
 text_poke_flush arch/x86/kernel/alternative.c:2158 [inline]
 text_poke_finish+0x1a/0x30 arch/x86/kernel/alternative.c:2168
 arch_jump_label_transform_apply+0x17/0x30 arch/x86/kernel/jump_label.c:146
 jump_label_update+0x32f/0x410 kernel/jump_label.c:829
 static_key_enable_cpuslocked+0x1b5/0x270 kernel/jump_label.c:205
 static_key_enable+0x1a/0x20 kernel/jump_label.c:218
 toggle_allocation_gate mm/kfence/core.c:831 [inline]
 toggle_allocation_gate+0xf8/0x230 mm/kfence/core.c:823
 process_one_work+0x991/0x15c0 kernel/workqueue.c:2390
 worker_thread+0x669/0x1090 kernel/workqueue.c:2537
 kthread+0x344/0x440 kernel/kthread.c:379
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
 </TASK>

Crashes (18):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/04/29 16:08 upstream 89d77f71f493 62df2017 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in lock_rename
2023/04/27 16:37 upstream 6e98b09da931 6f3d6fa7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_rename
2023/04/18 22:46 upstream af67688dca57 d931e9f0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in lock_rename
2023/04/05 04:27 upstream 76f598ba7d8e 831373d3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_rename
2023/04/03 15:08 upstream 7e364e56293b 41147e3e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_rename
2023/03/22 12:40 upstream a1effab7a3a3 d846e076 .config console log report info ci-upstream-kasan-gce-selinux-root INFO: task hung in lock_rename
2023/03/19 05:04 upstream a3671bd86a97 7939252e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in lock_rename
2023/03/13 07:49 upstream eeac8ede1755 5205ef30 .config console log report info ci-upstream-kasan-gce-root INFO: task hung in lock_rename
2023/03/06 07:45 upstream f915322fe014 f8902b57 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in lock_rename
2023/03/03 02:01 upstream 857f1268a591 f8902b57 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in lock_rename
2023/02/16 07:20 upstream 033c40a89f55 6be0f1f5 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_rename
2022/12/10 00:17 upstream 0d1409e4ff08 67be1ae7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs INFO: task hung in lock_rename
2022/10/12 07:10 upstream 493ffd6605b2 02b6492e .config console log report info [disk image] [vmlinux] ci2-upstream-fs INFO: task hung in lock_rename
2022/09/30 10:37 upstream 987a926c1d8a 45fd7169 .config console log report info [disk image] [vmlinux] ci2-upstream-fs INFO: task hung in lock_rename
2022/09/23 03:25 upstream dc164f4fb00a 0042f2b4 .config console log report info [disk image] [vmlinux] ci2-upstream-fs INFO: task hung in lock_rename
2022/09/21 00:01 upstream 60891ec99e14 c4b8ccfd .config console log report info [disk image] [vmlinux] ci2-upstream-fs INFO: task hung in lock_rename
2022/08/24 06:20 linux-next 05477f3653b8 cea8b0f7 .config console log report info ci-upstream-linux-next-kasan-gce-root INFO: task hung in lock_rename
2022/09/24 11:36 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci c194837ebb57 0042f2b4 .config console log report info [disk image] [vmlinux] ci-upstream-gce-arm64 INFO: task hung in lock_rename
* Struck through repros no longer work on HEAD.