[v5.15] WARNING in lookup_slow

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 1fe619a7d252 Linux 5.15.113
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14dc0319280000
kernel config: https://syzkaller.appspot.com/x/.config?x=8f10ee30ae29b021
dashboard link: https://syzkaller.appspot.com/bug?extid=5096d8e406f819b7c12a
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/1b707a1e1816/disk-1fe619a7.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/19cc598a8bbe/vmlinux-1fe619a7.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a6cf7269bae5/Image-1fe619a7.gz.xz

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

------------[ cut here ]------------
DEBUG_RWSEMS_WARN_ON(!is_rwsem_reader_owned(sem)): count = 0x0, magic = 0xffff00012190d450, owner = 0x0, curr 0xffff000125453680, list empty
WARNING: CPU: 0 PID: 6479 at kernel/locking/rwsem.c:1315 __up_read+0x568/0x60c kernel/locking/rwsem.c:1315
Modules linked in:
CPU: 0 PID: 6479 Comm: syz-executor.0 Not tainted 5.15.113-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/28/2023
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : __up_read+0x568/0x60c kernel/locking/rwsem.c:1315
lr : __up_read+0x568/0x60c kernel/locking/rwsem.c:1315
sp : ffff80001eaa77a0
x29: ffff80001eaa7820 x28: 1ffff0000291c06a x27: ffff8000148e0000
x26: dfff800000000000 x25: 0000000000000000 x24: ffff00012190d4a8
x23: ffff000125453680 x22: ffff80001eaa77c0 x21: 0000000000000000
x20: ffff00012190d450 x19: ffff00012190d450 x18: 1fffe000368ff78e
x17: 1fffe000368ff78e x16: ffff800011950fac x15: ffff80001497f100
x14: 1ffff0000291c06a x13: ffffffffffffffff x12: 0000000000040000
x11: 0000000000006d1c x10: ffff80001d629000 x9 : b43778202d723000
x8 : b43778202d723000 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000000 x3 : ffff80000a953900
x2 : ffff0001b47fbd10 x1 : 0000000100000000 x0 : 000000000000008c
Call trace:
__up_read+0x568/0x60c kernel/locking/rwsem.c:1315
up_read+0x94/0xe8 kernel/locking/rwsem.c:1584
inode_unlock_shared include/linux/fs.h:802 [inline]
lookup_slow+0x6c/0x84 fs/namei.c:1677
walk_component+0x394/0x4cc fs/namei.c:1972
lookup_last fs/namei.c:2427 [inline]
path_lookupat+0x13c/0x3d0 fs/namei.c:2451
filename_lookup+0x1c4/0x4c8 fs/namei.c:2480
user_path_at_empty+0x5c/0x1a4 fs/namei.c:2853
user_path_at include/linux/namei.h:57 [inline]
do_mount fs/namespace.c:3334 [inline]
__do_sys_mount fs/namespace.c:3545 [inline]
__se_sys_mount fs/namespace.c:3522 [inline]
__arm64_sys_mount+0x4dc/0x5e0 fs/namespace.c:3522
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
irq event stamp: 554
hardirqs last enabled at (553): [<ffff800008268d0c>] raw_spin_rq_unlock_irq kernel/sched/sched.h:1338 [inline]
hardirqs last enabled at (553): [<ffff800008268d0c>] finish_lock_switch+0xbc/0x1e8 kernel/sched/core.c:4780
hardirqs last disabled at (554): [<ffff80001194c640>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:387
softirqs last enabled at (518): [<ffff800008020ccc>] softirq_handle_end kernel/softirq.c:401 [inline]
softirqs last enabled at (518): [<ffff800008020ccc>] __do_softirq+0xb5c/0xe20 kernel/softirq.c:587
softirqs last disabled at (117): [<ffff8000081b573c>] do_softirq_own_stack include/asm-generic/softirq_stack.h:10 [inline]
softirqs last disabled at (117): [<ffff8000081b573c>] invoke_softirq kernel/softirq.c:439 [inline]
softirqs last disabled at (117): [<ffff8000081b573c>] __irq_exit_rcu+0x28c/0x534 kernel/softirq.c:636
---[ end trace 0107ed80e47f6205 ]---
------------[ cut here ]------------
DEBUG_RWSEMS_WARN_ON(tmp < 0): count = 0xffffffffffffff00, magic = 0xffff00012190d450, owner = 0x0, curr 0xffff000125453680, list empty
WARNING: CPU: 0 PID: 6479 at kernel/locking/rwsem.c:1320 __up_read+0x3d0/0x60c kernel/locking/rwsem.c:1320
Modules linked in:
CPU: 0 PID: 6479 Comm: syz-executor.0 Tainted: G W 5.15.113-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/28/2023
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : __up_read+0x3d0/0x60c kernel/locking/rwsem.c:1320
lr : __up_read+0x3d0/0x60c kernel/locking/rwsem.c:1320
sp : ffff80001eaa77a0
x29: ffff80001eaa7820 x28: 1ffff0000291c06a x27: ffff8000148e0000
x26: dfff800000000000 x25: ffffffffffffff00 x24: ffff00012190d4a8
x23: ffff00012190d450 x22: ffffffffffffff00 x21: 0000000000000000
x20: ffff000125453680 x19: ffff00012190d450 x18: 0000000000000002
x17: ff80800008335ea8 x16: ffff800011950fac x15: ffff800008335ea8
x14: 00000000ffffffff x13: ffffffffffffffff x12: 0000000000040000
x11: 0000000000018dad x10: ffff80001d629000 x9 : b43778202d723000
x8 : b43778202d723000 x7 : 0000000000000001 x6 : 0000000000000001
x5 : ffff80001eaa6f18 x4 : ffff8000149bfca0 x3 : ffff80000854dc88
x2 : 0000000000000001 x1 : 0000000000000001
x0 : 0000000000000087
Call trace:
__up_read+0x3d0/0x60c kernel/locking/rwsem.c:1320
up_read+0x94/0xe8 kernel/locking/rwsem.c:1584
inode_unlock_shared include/linux/fs.h:802 [inline]
lookup_slow+0x6c/0x84 fs/namei.c:1677
walk_component+0x394/0x4cc fs/namei.c:1972
lookup_last fs/namei.c:2427 [inline]
path_lookupat+0x13c/0x3d0 fs/namei.c:2451
filename_lookup+0x1c4/0x4c8 fs/namei.c:2480
user_path_at_empty+0x5c/0x1a4 fs/namei.c:2853
user_path_at include/linux/namei.h:57 [inline]
do_mount fs/namespace.c:3334 [inline]
__do_sys_mount fs/namespace.c:3545 [inline]
__se_sys_mount fs/namespace.c:3522 [inline]
__arm64_sys_mount+0x4dc/0x5e0 fs/namespace.c:3522
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
irq event stamp: 561
hardirqs last enabled at (561): [<ffff80001194f440>] __exit_to_kernel_mode arch/arm64/kernel/entry-common.c:81 [inline]
hardirqs last enabled at (561): [<ffff80001194f440>] exit_to_kernel_mode+0x100/0x178 arch/arm64/kernel/entry-common.c:91
hardirqs last disabled at (560): [<ffff800011a1471c>] preempt_schedule_irq+0xac/0x274 kernel/sched/core.c:6777
softirqs last enabled at (518): [<ffff800008020ccc>] softirq_handle_end kernel/softirq.c:401 [inline]
softirqs last enabled at (518): [<ffff800008020ccc>] __do_softirq+0xb5c/0xe20 kernel/softirq.c:587
softirqs last disabled at (117): [<ffff8000081b573c>] do_softirq_own_stack include/asm-generic/softirq_stack.h:10 [inline]
softirqs last disabled at (117): [<ffff8000081b573c>] invoke_softirq kernel/softirq.c:439 [inline]
softirqs last disabled at (117): [<ffff8000081b573c>] __irq_exit_rcu+0x28c/0x534 kernel/softirq.c:636
---[ end trace 0107ed80e47f6206 ]---


---
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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

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

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

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

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.