[v6.1] INFO: task hung in do_renameat2

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 883d1a956208 Linux 6.1.75
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=161157a7e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=c421ffef554bdd17
dashboard link: https://syzkaller.appspot.com/bug?extid=8aebd3fa24fb1521f74d
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/1ff30edbe66d/disk-883d1a95.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1cd87be79a04/vmlinux-883d1a95.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e50c5a26cded/Image-883d1a95.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+8aebd3...@syzkaller.appspotmail.com

INFO: task syz-executor.4:20356 blocked for more than 143 seconds.
Not tainted 6.1.75-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.4 state:D stack:0 pid:20356 ppid:4267 flags:0x00000005
Call trace:
__switch_to+0x320/0x754 arch/arm64/kernel/process.c:553
context_switch kernel/sched/core.c:5245 [inline]
__schedule+0xee4/0x1c98 kernel/sched/core.c:6558
schedule+0xc4/0x170 kernel/sched/core.c:6634
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 fs/namei.c:3042 [inline]
do_renameat2+0x4e0/0xe34 fs/namei.c:4954
__do_sys_renameat fs/namei.c:5055 [inline]
__se_sys_renameat fs/namei.c:5052 [inline]
__arm64_sys_renameat+0xc8/0xe4 fs/namei.c:5052
__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:585

Showing all locks held in the system:
1 lock held by rcu_tasks_kthre/12:
#0: ffff800015a04eb0 (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: ffff800015a056b0 (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: ffff800015a04ce0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:317
2 locks held by getty/3981:
#0: ffff0000d8040098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x3c/0x4c drivers/tty/tty_ldsem.c:340
#1: ffff80001bcc02f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x414/0x1214 drivers/tty/n_tty.c:2188
2 locks held by syz-executor.4/20356:
#0: ffff0000cedcc460 (sb_writers#17){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:393
#1: ffff000122d11cb0 (&sb->s_type->i_mutex_key#23/1){+.+.}-{3:3}, at: inode_lock_nested include/linux/fs.h:791 [inline]
#1: ffff000122d11cb0 (&sb->s_type->i_mutex_key#23/1){+.+.}-{3:3}, at: lock_rename fs/namei.c:3042 [inline]
#1: ffff000122d11cb0 (&sb->s_type->i_mutex_key#23/1){+.+.}-{3:3}, at: do_renameat2+0x4e0/0xe34 fs/namei.c:4954
3 locks held by syz-executor.4/20362:
2 locks held by syz-executor.4/20700:
3 locks held by kworker/u4:19/23406:
2 locks held by kworker/u4:21/23411:
2 locks held by kworker/u4:25/23663:
#0: ffff0000c0029138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x664/0x1404 kernel/workqueue.c:2265
#1: ffff80002a8c7c20 ((work_completion)(&ctx->exit_work)){+.+.}-{0:0}, at: process_one_work+0x6a8/0x1404 kernel/workqueue.c:2267
2 locks held by syz-executor.0/26936:

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



---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup