[v6.1] WARNING in path_openat (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: dcbc050cb0d3 Linux 6.1.89
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=153fad37180000
kernel config: https://syzkaller.appspot.com/x/.config?x=22f9bec33cc10172
dashboard link: https://syzkaller.appspot.com/bug?extid=7af33ee264a3bdd72bc0
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/62590cf0da60/disk-dcbc050c.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f48fe2388a70/vmlinux-dcbc050c.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f4eb42b21e90/bzImage-dcbc050c.xz

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

DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && !rwsem_test_oflags(sem, RWSEM_NONSPINNABLE)): count = 0x0, magic = 0xffff888070ddf1d0, owner = 0x0, curr 0xffff888073821dc0, list empty
WARNING: CPU: 1 PID: 3772 at kernel/locking/rwsem.c:1372 __up_write kernel/locking/rwsem.c:1371 [inline]
WARNING: CPU: 1 PID: 3772 at kernel/locking/rwsem.c:1372 up_write+0x4f5/0x580 kernel/locking/rwsem.c:1626
Modules linked in:
CPU: 1 PID: 3772 Comm: syz-executor.1 Not tainted 6.1.89-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
RIP: 0010:__up_write kernel/locking/rwsem.c:1371 [inline]
RIP: 0010:up_write+0x4f5/0x580 kernel/locking/rwsem.c:1626
Code: 48 c7 c7 60 f5 eb 8a 48 c7 c6 a0 f7 eb 8a 48 8b 54 24 28 48 8b 4c 24 18 4d 89 e0 4c 8b 4c 24 30 53 e8 9f d5 e8 ff 48 83 c4 08 <0f> 0b e9 71 fd ff ff 48 c7 c1 a8 b3 73 8e 80 e1 07 80 c1 03 38 c1
RSP: 0018:ffffc90005487840 EFLAGS: 00010292
RAX: 6f7003eb026fb400 RBX: ffffffff8aebf640 RCX: 0000000000040000
RDX: ffffc9000b749000 RSI: 000000000001376c RDI: 000000000001376d
RBP: ffffc90005487910 R08: ffffffff81528eae R09: fffff52000a90e69
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000000
R13: ffff888070ddf1d0 R14: 1ffff92000a90f10 R15: dffffc0000000000
FS: 00007f4e77d016c0(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000560daa47dfc0 CR3: 000000007a34e000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
inode_unlock include/linux/fs.h:763 [inline]
open_last_lookups fs/namei.c:3556 [inline]
path_openat+0x1544/0x2e60 fs/namei.c:3782
do_filp_open+0x230/0x480 fs/namei.c:3812
do_sys_openat2+0x13b/0x500 fs/open.c:1318
do_sys_open fs/open.c:1334 [inline]
__do_sys_open fs/open.c:1342 [inline]
__se_sys_open fs/open.c:1338 [inline]
__x64_sys_open+0x221/0x270 fs/open.c:1338
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f4e7707dea9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f4e77d010c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000002
RAX: ffffffffffffffda RBX: 00007f4e771ac050 RCX: 00007f4e7707dea9
RDX: 0000000000000000 RSI: 0000000000080040 RDI: 00000000200002c0
RBP: 00007f4e770ca4a4 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000006e R14: 00007f4e771ac050 R15: 00007ffc7a1c8998
</TASK>


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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 284087d4f7d5 Linux 5.15.158
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1116ea2f180000
kernel config: https://syzkaller.appspot.com/x/.config?x=ab74f93e8454887c
dashboard link: https://syzkaller.appspot.com/bug?extid=fc894423606203c31beb

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/0accc7dacf9d/disk-284087d4.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/fb6b5b110f8c/vmlinux-284087d4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6763bebdbfea/Image-284087d4.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:

Reported-by: syzbot+fc8944...@syzkaller.appspotmail.com

------------[ cut here ]------------
DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && !rwsem_test_oflags(sem, RWSEM_NONSPINNABLE)): count = 0x0, magic = 0xffff0000e9088a90, owner = 0x0, curr 0xffff0000d5448000, list empty
WARNING: CPU: 1 PID: 6484 at kernel/locking/rwsem.c:1350 __up_write kernel/locking/rwsem.c:1349 [inline]
WARNING: CPU: 1 PID: 6484 at kernel/locking/rwsem.c:1350 up_write+0x524/0x6f0 kernel/locking/rwsem.c:1604
Modules linked in:
CPU: 1 PID: 6484 Comm: syz-executor.4 Not tainted 5.15.158-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024

pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : __up_write kernel/locking/rwsem.c:1349 [inline]
pc : up_write+0x524/0x6f0 kernel/locking/rwsem.c:1604
lr : __up_write kernel/locking/rwsem.c:1349 [inline]
lr : up_write+0x524/0x6f0 kernel/locking/rwsem.c:1604
sp : ffff80001d9a76c0
x29: ffff80001d9a76d0 x28: ffff0000d6d727d0 x27: ffff80001d9a7a18
x26: dfff800000000000 x25: 1fffe0001d21115f x24: ffff0000e9088ae8
x23: 0000000000000000 x22: 0000000000000000 x21: ffff0000d5448000
x20: ffff0000e9088a90 x19: ffff0000e9088a90 x18: 1fffe0003690198e
x17: 1fffe0003690198e x16: ffff800011998e34 x15: ffff8000149dec00
x14: 1ffff0000292806a x13: dfff800000000000 x12: 0000000000040000
x11: 000000000001986a x10: ffff800028410000 x9 : aa91540b76df8000
x8 : aa91540b76df8000 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000000 x3 : ffff80000a978b80
x2 : ffff0001b480cd10 x1 : 0000000100000000 x0 : 00000000000000bd
Call trace:
__up_write kernel/locking/rwsem.c:1349 [inline]
up_write+0x524/0x6f0 kernel/locking/rwsem.c:1604
inode_unlock include/linux/fs.h:794 [inline]
open_last_lookups fs/namei.c:3536 [inline]
path_openat+0x1198/0x26cc fs/namei.c:3739
do_filp_open+0x1a8/0x3b4 fs/namei.c:3769
do_sys_openat2+0x128/0x3d8 fs/open.c:1253
do_sys_open fs/open.c:1269 [inline]
__do_sys_openat fs/open.c:1285 [inline]
__se_sys_openat fs/open.c:1280 [inline]
__arm64_sys_openat+0x1f0/0x240 fs/open.c:1280
__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:608
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
irq event stamp: 478
hardirqs last enabled at (477): [<ffff800008269adc>] raw_spin_rq_unlock_irq kernel/sched/sched.h:1338 [inline]
hardirqs last enabled at (477): [<ffff800008269adc>] finish_lock_switch+0xbc/0x1e8 kernel/sched/core.c:4784
hardirqs last disabled at (478): [<ffff8000119944c0>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:396
softirqs last enabled at (474): [<ffff800008021c64>] softirq_handle_end kernel/softirq.c:401 [inline]
softirqs last enabled at (474): [<ffff800008021c64>] __do_softirq+0xb5c/0xdb0 kernel/softirq.c:587
softirqs last disabled at (385): [<ffff8000081b6568>] do_softirq_own_stack include/asm-generic/softirq_stack.h:10 [inline]
softirqs last disabled at (385): [<ffff8000081b6568>] invoke_softirq kernel/softirq.c:439 [inline]
softirqs last disabled at (385): [<ffff8000081b6568>] __irq_exit_rcu+0x264/0x4d4 kernel/softirq.c:637
---[ end trace 31eec7981fdcee68 ]---