[v6.1] INFO: task hung in do_renameat2 (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 909ba1f1b414 Linux 6.1.90
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17f16884980000
kernel config: https://syzkaller.appspot.com/x/.config?x=660c4d17e3d2ceeb
dashboard link: https://syzkaller.appspot.com/bug?extid=74e792c3ce00a3c0c168
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/5a4f1efb0858/disk-909ba1f1.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/5f7faf626bf2/vmlinux-909ba1f1.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9d7a2826732f/Image-909ba1f1.gz.xz

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

INFO: task syz-executor.4:4573 blocked for more than 143 seconds.
Not tainted 6.1.90-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.4 state:D stack:0 pid:4573 ppid:4244 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
do_renameat2+0x538/0xe64 fs/namei.c:4968
__do_sys_renameat2 fs/namei.c:5062 [inline]
__se_sys_renameat2 fs/namei.c:5059 [inline]
__arm64_sys_renameat2+0xe0/0xfc fs/namei.c:5059
__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
INFO: task syz-executor.4:4577 blocked for more than 143 seconds.
Not tainted 6.1.90-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz-executor.4 state:D stack:0 pid:4577 ppid:4244 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
schedule_preempt_disabled+0x18/0x2c kernel/sched/core.c:6693
rwsem_down_read_slowpath+0x534/0x858 kernel/locking/rwsem.c:1094
__down_read_common kernel/locking/rwsem.c:1261 [inline]
__down_read kernel/locking/rwsem.c:1274 [inline]
down_read+0xac/0x308 kernel/locking/rwsem.c:1522
inode_lock_shared include/linux/fs.h:768 [inline]
lookup_slow+0x50/0x84 fs/namei.c:1706
walk_component+0x280/0x36c fs/namei.c:1998
lookup_last fs/namei.c:2455 [inline]
path_lookupat+0x13c/0x3d0 fs/namei.c:2479
filename_lookup+0x1d4/0x4e0 fs/namei.c:2508
user_path_at_empty+0x5c/0x84 fs/namei.c:2907
user_path_at include/linux/namei.h:57 [inline]
path_setxattr+0xbc/0x258 fs/xattr.c:631
__do_sys_setxattr fs/xattr.c:652 [inline]
__se_sys_setxattr fs/xattr.c:648 [inline]
__arm64_sys_setxattr+0xbc/0xd8 fs/xattr.c:648
__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: ffff800015a14e70 (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: ffff800015a15670 (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: ffff800015a14ca0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0xc/0x44 include/linux/rcupdate.h:349
2 locks held by kworker/u4:2/39:
#0: ffff0000c0029138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x664/0x1404 kernel/workqueue.c:2265
#1: ffff80001b2b7c20 ((work_completion)(&ctx->exit_work)){+.+.}-{0:0}, at: process_one_work+0x6a8/0x1404 kernel/workqueue.c:2267
2 locks held by getty/3981:
#0: ffff0000d5edb098 (&tty->ldisc_sem){++++}-{0:0}, at: ldsem_down_read+0x3c/0x4c drivers/tty/tty_ldsem.c:340
#1: ffff80001bcf02f0 (&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/4564:
2 locks held by syz-executor.4/4573:
#0: ffff0000c3206460 (sb_writers#17){.+.+}-{0:0}, at: mnt_want_write+0x44/0x9c fs/namespace.c:393
#1: ffff0000e273c188 (&type->i_mutex_dir_key#12/1){+.+.}-{3:3}, at: do_renameat2+0x538/0xe64 fs/namei.c:4968
1 lock held by syz-executor.4/4577:
#0: ffff0000e273c188 (&type->i_mutex_dir_key#13){.+.+}-{3:3}, at: inode_lock_shared include/linux/fs.h:768 [inline]
#0: ffff0000e273c188 (&type->i_mutex_dir_key#13){.+.+}-{3:3}, at: lookup_slow+0x50/0x84 fs/namei.c:1706
2 locks held by kworker/1:17/4633:
#0: ffff0000c0021938 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x664/0x1404 kernel/workqueue.c:2265
#1: ffff80001efe7c20 ((work_completion)(&rew->rew_work)){+.+.}-{0:0}, at: process_one_work+0x6a8/0x1404 kernel/workqueue.c:2267
1 lock held by syz-executor.0/4710:
#0: ffff800015a1a278 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:291 [inline]
#0: ffff800015a1a278 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x3e0/0x77c kernel/rcu/tree_exp.h:962
3 locks held by kworker/u4:7/4956:
#0: ffff0000c8bef138 ((wq_completion)phy25){+.+.}-{0:0}, at: process_one_work+0x664/0x1404 kernel/workqueue.c:2265
#1: ffff8000201c7c20 ((work_completion)(&sdata->work)){+.+.}-{0:0}, at: process_one_work+0x6a8/0x1404 kernel/workqueue.c:2267
#2: ffff0000cdd5cd40 (&wdev->mtx){+.+.}-{3:3}, at: sdata_lock net/mac80211/ieee80211_i.h:1114 [inline]
#2: ffff0000cdd5cd40 (&wdev->mtx){+.+.}-{3:3}, at: ieee80211_ibss_rx_queued_mgmt+0x100/0x27a0 net/mac80211/ibss.c:1627
1 lock held by udevd/5051:
#0: ffff0000c0496bd8 (mapping.invalidate_lock#2){.+.+}-{3:3}, at: filemap_invalidate_lock_shared include/linux/fs.h:813 [inline]
#0: ffff0000c0496bd8 (mapping.invalidate_lock#2){.+.+}-{3:3}, at: page_cache_ra_unbounded+0xc8/0x58c mm/readahead.c:226
2 locks held by syz-executor.2/8397:
5 locks held by syz-executor.4/8404:
#0: ffff800017e7bcf0 (cb_lock){++++}-{3:3}, at: genl_rcv+0x28/0x50 net/netlink/genetlink.c:860
#1: ffff0000f0ed07c8 (&rdev->wiphy.mtx){+.+.}-{3:3}, at: wiphy_lock include/net/cfg80211.h:5639 [inline]
#1: ffff0000f0ed07c8 (&rdev->wiphy.mtx){+.+.}-{3:3}, at: nl80211_pre_doit+0x484/0x764 net/wireless/nl80211.c:16262
#2: ffff0000cdd5cd40 (&wdev->mtx){+.+.}-{3:3}, at: wdev_lock net/wireless/core.h:231 [inline]
#2: ffff0000cdd5cd40 (&wdev->mtx){+.+.}-{3:3}, at: nl80211_new_key+0x4b4/0x9ec net/wireless/nl80211.c:4705
#3: ffff0000f0ed17a0 (&local->sta_mtx){+.+.}-{3:3}, at: ieee80211_add_key+0x388/0x960 net/mac80211/cfg.c:513
#4: ffff0000f0ed2a88 (&local->key_mtx){+.+.}-{3:3}, at: ieee80211_key_link+0x144/0x11f0 net/mac80211/key.c:855
1 lock held by syz-executor.1/8414:
#0: ffff0000c900e130 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: lock_sock include/net/sock.h:1748 [inline]
#0: ffff0000c900e130 (sk_lock-AF_PACKET){+.+.}-{0:0}, at: packet_setsockopt+0x518/0x1228 net/packet/af_packet.c:3797

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



---
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