[moderation] [fs?] WARNING in path_mount

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: c760b3725e52 Merge tag 'mm-nonmm-stable-2024-05-22-17-30' ..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17a93014980000
kernel config: https://syzkaller.appspot.com/x/.config?x=966dbeb548ca6926
dashboard link: https://syzkaller.appspot.com/bug?extid=05e6e2588f08f1e74824
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
CC: [bra...@kernel.org ja...@suse.cz linux-...@vger.kernel.org linux-...@vger.kernel.org vi...@zeniv.linux.org.uk]

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

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7bc7510fe41f/non_bootable_disk-c760b372.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/2cc0f81a6b8c/vmlinux-c760b372.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1cfbe622ff02/bzImage-c760b372.xz

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

------------[ cut here ]------------
DEBUG_RWSEMS_WARN_ON((rwsem_owner(sem) != current) && !rwsem_test_oflags(sem, RWSEM_NONSPINNABLE)): count = 0x0, magic = 0xffff888032eecac8, owner = 0x0, curr 0xffff88802ae6c880, list empty
WARNING: CPU: 1 PID: 8230 at kernel/locking/rwsem.c:1369 __up_write kernel/locking/rwsem.c:1369 [inline]
WARNING: CPU: 1 PID: 8230 at kernel/locking/rwsem.c:1369 up_write+0x469/0x520 kernel/locking/rwsem.c:1632
Modules linked in:
CPU: 1 PID: 8230 Comm: syz-executor.3 Not tainted 6.9.0-syzkaller-11952-gc760b3725e52 #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
RIP: 0010:__up_write kernel/locking/rwsem.c:1369 [inline]
RIP: 0010:up_write+0x469/0x520 kernel/locking/rwsem.c:1632
Code: ea 03 80 3c 02 00 75 53 48 8b 13 4d 89 f1 41 55 4d 89 f8 4c 89 e1 48 c7 c6 60 a3 2c 8b 48 c7 c7 80 a2 2c 8b e8 a8 78 e5 ff 90 <0f> 0b 90 90 5a e9 96 fc ff ff 48 89 ef e8 f5 47 7f 00 e9 03 fd ff
RSP: 0018:ffffc900032e7d50 EFLAGS: 00010286
RAX: 0000000000000000 RBX: ffff888032eecac8 RCX: ffffc900234ca000
RDX: 0000000000040000 RSI: ffffffff81500016 RDI: 0000000000000001
RBP: ffff888032eecad0 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000000 R12: ffff888032eecac8
R13: ffffffff8b2ca1c0 R14: ffff88802ae6c880 R15: 0000000000000000
FS: 00007f72a5db36c0(0000) GS:ffff88806b100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f9ced8a1000 CR3: 000000004e0dc000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
inode_unlock include/linux/fs.h:796 [inline]
unlock_mount fs/namespace.c:2514 [inline]
do_new_mount_fc fs/namespace.c:3295 [inline]
do_new_mount fs/namespace.c:3354 [inline]
path_mount+0x1b21/0x1f20 fs/namespace.c:3679
do_mount fs/namespace.c:3692 [inline]
__do_sys_mount fs/namespace.c:3898 [inline]
__se_sys_mount fs/namespace.c:3875 [inline]
__x64_sys_mount+0x297/0x320 fs/namespace.c:3875
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f72a507cee9
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:00007f72a5db30c8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f72a51ac050 RCX: 00007f72a507cee9
RDX: 0000000020000300 RSI: 00000000200002c0 RDI: 0000000000000000
RBP: 00007f72a50c949e R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 000000000000006e R14: 00007f72a51ac050 R15: 00007ffc12e704f8
</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