syzbot


INFO: task hung in ext4_rename

Status: auto-obsoleted due to no activity on 2023/07/04 22:26
Subsystems: ext4
[Documentation on labels]
First crash: 681d, last: 664d

Sample crash report:
INFO: task syz-executor.1:9527 blocked for more than 143 seconds.
      Not tainted 6.3.0-rc5-syzkaller-00032-g99ddf2254feb #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.1  state:D stack:26752 pid:9527  ppid:5101   flags:0x00004004
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5307 [inline]
 __schedule+0xc91/0x5770 kernel/sched/core.c:6625
 schedule+0xde/0x1a0 kernel/sched/core.c:6701
 schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:6760
 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:793 [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:0x7ff483a8c169
RSP: 002b:00007ff48487d168 EFLAGS: 00000246 ORIG_RAX: 0000000000000052
RAX: ffffffffffffffda RBX: 00007ff483babf80 RCX: 00007ff483a8c169
RDX: 0000000000000000 RSI: 00000000200000c0 RDI: 0000000020000200
RBP: 00007ff483ae7ca1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffe291148bf R14: 00007ff48487d300 R15: 0000000000022000
 </TASK>
INFO: task syz-executor.1:9536 blocked for more than 143 seconds.
      Not tainted 6.3.0-rc5-syzkaller-00032-g99ddf2254feb #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.1  state:D stack:28632 pid:9536  ppid:5101   flags:0x00004004
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5307 [inline]
 __schedule+0xc91/0x5770 kernel/sched/core.c:6625
 schedule+0xde/0x1a0 kernel/sched/core.c:6701
 schedule_preempt_disabled+0x13/0x20 kernel/sched/core.c:6760
 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:793 [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:0x7ff483a8c169
RSP: 002b:00007ff48483b168 EFLAGS: 00000246 ORIG_RAX: 000000000000013c
RAX: ffffffffffffffda RBX: 00007ff483bac120 RCX: 00007ff483a8c169
RDX: 0000000000000004 RSI: 00000000200002c0 RDI: 0000000000000004
RBP: 00007ff483ae7ca1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000020000180 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffe291148bf R14: 00007ff48483b300 R15: 0000000000022000
 </TASK>

Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/11:
 #0: ffffffff8c791a70 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x31/0xd80 kernel/rcu/tasks.h:510
1 lock held by rcu_tasks_trace/12:
 #0: ffffffff8c791770 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x31/0xd80 kernel/rcu/tasks.h:510
1 lock held by khungtaskd/27:
 #0: ffffffff8c7925c0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x55/0x340 kernel/locking/lockdep.c:6495
2 locks held by getty/4740:
 #0: ffff8880294db098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x26/0x80 drivers/tty/tty_ldisc.c:244
 #1: ffffc900020482f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0xef4/0x13e0 drivers/tty/n_tty.c:2177
2 locks held by syz-fuzzer/5091:
 #0: ffff88802307dba8 (&f->f_pos_lock){+.+.}-{3:3}, at: __fdget_pos+0xe7/0x100 fs/file.c:1047
 #1: ffff888034c34900 (&type->i_mutex_dir_key#3){++++}-{3:3}, at: iterate_dir+0xd1/0x6f0 fs/readdir.c:55
5 locks held by kworker/u4:17/5466:
 #0: ffff8880b983c2d8 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x2f/0x120 kernel/sched/core.c:539
 #1: ffff8880b9828808 (&per_cpu_ptr(group->pcpu, cpu)->seq){-.-.}-{0:0}, at: psi_task_switch+0x2de/0x950 kernel/sched/psi.c:976
 #2: ffff8880b9829698 (&base->lock){-.-.}-{2:2}, at: lock_timer_base+0x5a/0x1f0 kernel/time/timer.c:999
 #3: ffffffff91fd24d0 (&obj_hash[i].lock){-.-.}-{2:2}, at: debug_object_activate+0x132/0x3e0 lib/debugobjects.c:665
 #4: ffffffff8c6589c8 (text_mutex){+.+.}-{3:3}, at: arch_jump_label_transform_apply+0x12/0x30 arch/x86/kernel/jump_label.c:145
4 locks held by syz-executor.1/9527:
 #0: ffff88814b766460 (sb_writers#5){.+.+}-{0:0}, at: do_renameat2+0x37f/0xc90 fs/namei.c:4859
 #1: ffff888034c34900 (&type->i_mutex_dir_key#3/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:793 [inline]
 #1: ffff888034c34900 (&type->i_mutex_dir_key#3/1){+.+.}-{3:3}, at: lock_rename+0x229/0x280 fs/namei.c:2991
 #2: ffff88807b3146c0 (&type->i_mutex_dir_key#3){++++}-{3:3}, at: inode_lock include/linux/fs.h:758 [inline]
 #2: ffff88807b3146c0 (&type->i_mutex_dir_key#3){++++}-{3:3}, at: vfs_rename+0x4f9/0x17a0 fs/namei.c:4744
 #3: ffff888030ed5580 (&type->i_mutex_dir_key#3/4){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:793 [inline]
 #3: ffff888030ed5580 (&type->i_mutex_dir_key#3/4){+.+.}-{3:3}, at: ext4_rename+0x1593/0x2790 fs/ext4/namei.c:3821
4 locks held by syz-executor.1/9536:
 #0: ffff88814b766460 (sb_writers#5){.+.+}-{0:0}, at: do_renameat2+0x37f/0xc90 fs/namei.c:4859
 #1: ffff88814b766748 (&type->s_vfs_rename_key#2){+.+.}-{3:3}, at: lock_rename+0x58/0x280 fs/namei.c:2995
 #2: ffff888030ed5580 (&type->i_mutex_dir_key#3/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:793 [inline]
 #2: ffff888030ed5580 (&type->i_mutex_dir_key#3/1){+.+.}-{3:3}, at: lock_rename+0x1b0/0x280 fs/namei.c:3011
 #3: ffff88807b3146c0 (&type->i_mutex_dir_key#3/5){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:793 [inline]
 #3: ffff88807b3146c0 (&type->i_mutex_dir_key#3/5){+.+.}-{3:3}, at: lock_rename+0x1e4/0x280 fs/namei.c:3012
2 locks held by syz-executor.2/9591:
 #0: ffff88814b766460 (sb_writers#5){.+.+}-{0:0}, at: do_renameat2+0x37f/0xc90 fs/namei.c:4859
 #1: ffff88814b766748 (&type->s_vfs_rename_key#2){+.+.}-{3:3}, at: lock_rename+0x58/0x280 fs/namei.c:2995
2 locks held by syz-executor.3/9597:
 #0: ffff88814b766460 (sb_writers#5){.+.+}-{0:0}, at: do_renameat2+0x37f/0xc90 fs/namei.c:4859
 #1: ffff88814b766748 (&type->s_vfs_rename_key#2){+.+.}-{3:3}, at: lock_rename+0x58/0x280 fs/namei.c:2995
2 locks held by syz-executor.4/9601:
 #0: ffff88814b766460 (sb_writers#5){.+.+}-{0:0}, at: do_renameat2+0x37f/0xc90 fs/namei.c:4859
 #1: ffff88814b766748 (&type->s_vfs_rename_key#2){+.+.}-{3:3}, at: lock_rename+0x58/0x280 fs/namei.c:2995

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

NMI backtrace for cpu 1
CPU: 1 PID: 27 Comm: khungtaskd Not tainted 6.3.0-rc5-syzkaller-00032-g99ddf2254feb #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/30/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+0x2e8/0x3a0 kernel/kthread.c:376
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
 </TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 4408 Comm: syslogd Not tainted 6.3.0-rc5-syzkaller-00032-g99ddf2254feb #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/30/2023
RIP: 0010:preempt_count_add+0x43/0x140 kernel/sched/core.c:5778
Code: 53 83 e0 07 89 fb 48 c1 e9 03 83 c0 03 0f b6 14 11 38 d0 7c 08 84 d2 0f 85 e1 00 00 00 8b 15 54 d3 82 10 65 01 1d d5 29 ad 7e <85> d2 75 11 65 8b 05 ca 29 ad 7e 0f b6 c0 3d f4 00 00 00 7f 64 65
RSP: 0018:ffffc9000342fd48 EFLAGS: 00000282
RAX: 0000000000000003 RBX: 0000000000000001 RCX: 1ffffffff23b2c48
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000001
RBP: ffff8880188ce000 R08: 0000000000000000 R09: ffffffff914c7c2f
R10: fffffbfff2298f85 R11: 0000000000000000 R12: 0000000000000000
R13: 1ffff92000685fb2 R14: ffffc9000342fec8 R15: ffff8880233b15fc
FS:  00007f3257945800(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000c014753072 CR3: 000000007ea90000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 percpu_down_read include/linux/percpu-rwsem.h:53 [inline]
 __sb_start_write include/linux/fs.h:1477 [inline]
 sb_start_write include/linux/fs.h:1552 [inline]
 file_start_write include/linux/fs.h:2505 [inline]
 vfs_write+0x753/0xe10 fs/read_write.c:580
 ksys_write+0x12b/0x250 fs/read_write.c:637
 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:0x7f3257ad19a3
Code: 8b 15 d9 f4 0c 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb b7 0f 1f 00 64 8b 04 25 18 00 00 00 85 c0 75 14 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 55 c3 0f 1f 40 00 48 83 ec 28 48 89 54 24 18
RSP: 002b:00007ffe180b5448 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007f3257ad19a3
RDX: 0000000000000058 RSI: 0000564a97134600 RDI: 0000000000000003
RBP: 0000564a97134600 R08: 00007f3257b61040 R09: 00007f3257b610c0
R10: 00007f3257b60fc0 R11: 0000000000000246 R12: 0000000000000058
R13: 00007f3257945788 R14: 0000000000000004 R15: 0000564a97134410
 </TASK>

Crashes (2):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/04/05 22:18 upstream 99ddf2254feb 8b834965 .config console log report info ci-upstream-kasan-gce-selinux-root INFO: task hung in ext4_rename
2023/03/19 22:33 upstream 5cdfdd6da323 7939252e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in ext4_rename
* Struck through repros no longer work on HEAD.