[v5.15] WARNING in do_loopback

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: c52b9710c83d Linux 5.15.156
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14e87e08980000
kernel config: https://syzkaller.appspot.com/x/.config?x=567b6ddc38438433
dashboard link: https://syzkaller.appspot.com/bug?extid=c8e81ac628b184c8302c
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/1bd4b9969373/disk-c52b9710.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/10509e89bd25/vmlinux-c52b9710.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a623a4c52eb5/bzImage-c52b9710.xz

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

DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && !rwsem_test_oflags(sem, RWSEM_NONSPINNABLE)): count = 0x0, magic = 0xffff888070fcaf70, owner = 0x0, curr 0xffff8880216dbb80, list empty
WARNING: CPU: 1 PID: 4937 at kernel/locking/rwsem.c:1350 __up_write kernel/locking/rwsem.c:1349 [inline]
WARNING: CPU: 1 PID: 4937 at kernel/locking/rwsem.c:1350 up_write+0x4f5/0x580 kernel/locking/rwsem.c:1604
Modules linked in:
CPU: 1 PID: 4937 Comm: syz-executor.3 Not tainted 5.15.156-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
RIP: 0010:__up_write kernel/locking/rwsem.c:1349 [inline]
RIP: 0010:up_write+0x4f5/0x580 kernel/locking/rwsem.c:1604
Code: 48 c7 c7 00 1d 8b 8a 48 c7 c6 c0 1f 8b 8a 48 8b 54 24 28 48 8b 4c 24 18 4d 89 e0 4c 8b 4c 24 30 53 e8 df 0d ea ff 48 83 c4 08 <0f> 0b e9 71 fd ff ff 48 c7 c1 88 8e e4 8d 80 e1 07 80 c1 03 38 c1
RSP: 0018:ffffc900034ffca0 EFLAGS: 00010296
RAX: ebc39c168a63a700 RBX: ffffffff8a8b1de0 RCX: 0000000000040000
RDX: ffffc9000beca000 RSI: 000000000000b5fb RDI: 000000000000b5fc
RBP: ffffc900034ffd70 R08: ffffffff8166862c R09: ffffed10173667a8
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000000
R13: ffff888070fcaf70 R14: 1ffff9200069ff9c R15: dffffc0000000000
FS: 00007fe080a666c0(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f2664217e00 CR3: 0000000059df2000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
inode_unlock include/linux/fs.h:794 [inline]
unlock_mount fs/namespace.c:2281 [inline]
do_loopback+0x4a5/0x510 fs/namespace.c:2415
do_mount fs/namespace.c:3348 [inline]
__do_sys_mount fs/namespace.c:3556 [inline]
__se_sys_mount+0x2d5/0x3c0 fs/namespace.c:3533
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7fe082514ea9
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:00007fe080a660c8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007fe082643050 RCX: 00007fe082514ea9
RDX: 0000000000000000 RSI: 0000000020000200 RDI: 00000000200002c0
RBP: 00007fe0825614a4 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000101091 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000006e R14: 00007fe082643050 R15: 00007fff37db9848
</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