syzbot


INFO: task hung in lock_rename

Status: auto-obsoleted due to no activity on 2024/01/01 05:54
Reported-by: syzbot+053bd1c776f16c7ec272@syzkaller.appspotmail.com
First crash: 539d, last: 425d
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 1235d 1235d 0/28 auto-closed as invalid on 2021/10/02 18:08
linux-5.15 INFO: task hung in lock_rename 2 570d 601d 0/3 auto-obsoleted due to no activity on 2023/08/23 09:02
upstream INFO: task hung in lock_rename exfat 53 2182d 2316d 0/28 auto-closed as invalid on 2019/05/30 13:09
upstream INFO: task hung in lock_rename (4) fs 3 1024d 1118d 0/28 closed as invalid on 2022/02/08 09:40
linux-4.19 INFO: task hung in lock_rename 1 1048d 1048d 0/1 auto-closed as invalid on 2022/05/08 10:15
upstream INFO: task hung in lock_rename (5) fs 2 980d 1009d 0/28 auto-closed as invalid on 2022/06/15 04:15
upstream INFO: task hung in lock_rename (2) fs 7 1386d 1410d 0/28 auto-closed as invalid on 2021/05/17 09:31
linux-4.14 INFO: task hung in lock_rename 1 893d 893d 0/1 auto-obsoleted due to no activity on 2022/10/10 13:20
android-49 INFO: task hung in lock_rename C 9 2277d 2048d 0/3 public: reported C repro on 2019/04/14 00:00
upstream INFO: task hung in lock_rename (6) ext4 18 571d 820d 0/28 auto-obsoleted due to no activity on 2023/07/28 16:10

Sample crash report:
INFO: task syz-executor.5:28853 blocked for more than 143 seconds.
      Not tainted 6.1.54-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.5  state:D stack:0     pid:28853 ppid:4271   flags:0x00000005
Call trace:
 __switch_to+0x320/0x754 arch/arm64/kernel/process.c:553
 context_switch kernel/sched/core.c:5241 [inline]
 __schedule+0xee4/0x1c98 kernel/sched/core.c:6554
 schedule+0xc4/0x170 kernel/sched/core.c:6630
 rwsem_down_write_slowpath+0xc80/0x156c kernel/locking/rwsem.c:1189
 __down_write_common kernel/locking/rwsem.c:1314 [inline]
 __down_write kernel/locking/rwsem.c:1323 [inline]
 down_write_nested+0x90/0x94 kernel/locking/rwsem.c:1690
 inode_lock_nested include/linux/fs.h:791 [inline]
 lock_rename+0xdc/0x198 fs/namei.c:2990
 do_renameat2+0x49c/0x1040 fs/namei.c:4876
 __do_sys_renameat2 fs/namei.c:4968 [inline]
 __se_sys_renameat2 fs/namei.c:4965 [inline]
 __arm64_sys_renameat2+0xe0/0xfc fs/namei.c:4965
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
 do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
 el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:581

Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
 #0: ffff800015a84ef0 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x44/0xcf4 kernel/rcu/tasks.h:516
1 lock held by rcu_tasks_trace/13:
 #0: ffff800015a856f0 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x44/0xcf4 kernel/rcu/tasks.h:516
1 lock held by khungtaskd/28:
 #0: ffff800015a84d20 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:305
2 locks held by kworker/u4:5/1581:
1 lock held by udevd/3843:
2 locks held by getty/3986:
 #0: ffff0000d6246098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x3c/0x4c drivers/tty/tty_ldsem.c:340
 #1: ffff80001bd502f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1214 drivers/tty/n_tty.c:2188
4 locks held by kworker/u4:19/20474:
2 locks held by syz-executor.5/28847:
2 locks held by syz-executor.5/28853:
 #0: ffff00013f3be460 (sb_writers#17){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:393
 #1: ffff0000df561180 (&type->i_mutex_dir_key#12/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:791 [inline]
 #1: ffff0000df561180 (&type->i_mutex_dir_key#12/1){+.+.}-{3:3}, at: lock_rename+0xdc/0x198 fs/namei.c:2990
1 lock held by syz-executor.0/2020:
 #0: ffff0001636f9130 (&tty->atomic_write_lock){+.+.}-{3:3}, at: tty_write_lock drivers/tty/tty_io.c:944 [inline]
 #0: ffff0001636f9130 (&tty->atomic_write_lock){+.+.}-{3:3}, at: send_break+0xc4/0x2f4 drivers/tty/tty_io.c:2478
1 lock held by syz-executor.4/2044:
 #0: ffff000160a78210 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:756 [inline]
 #0: ffff000160a78210 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: __sock_release net/socket.c:651 [inline]
 #0: ffff000160a78210 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: sock_close+0x80/0x1fc net/socket.c:1370

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


Crashes (3):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/09/23 05:53 linux-6.1.y a356197db198 0b6a67ac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in lock_rename
2023/06/01 06:41 linux-6.1.y d2869ace6eeb babc4389 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan INFO: task hung in lock_rename
2023/06/19 04:02 linux-6.1.y ca87e77a2ef8 f3921d4d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 INFO: task hung in lock_rename
* Struck through repros no longer work on HEAD.