[v6.1] WARNING: locking bug in do_new_mount

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: c63962be84ef Linux 6.1.124
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=132eeef8580000
kernel config: https://syzkaller.appspot.com/x/.config?x=b61d63ebcdeb2b69
dashboard link: https://syzkaller.appspot.com/bug?extid=b48174d307d926d48d82
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/def628dfde4b/disk-c63962be.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/19bcf728ff3d/vmlinux-c63962be.xz
kernel image: https://storage.googleapis.com/syzbot-assets/dd43dbb11866/bzImage-c63962be.xz

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

loop6: detected capacity change from 0 to 4096
ntfs3: loop6: Different NTFS' sector size (1024) and media sector size (512)
------------[ cut here ]------------
releasing a pinned lock
WARNING: CPU: 1 PID: 19661 at kernel/locking/lockdep.c:5346 lock_release+0x6bc/0xa20 kernel/locking/lockdep.c:5682
Modules linked in:
CPU: 1 PID: 19661 Comm: syz.6.4645 Not tainted 6.1.124-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:__lock_release kernel/locking/lockdep.c:5346 [inline]
RIP: 0010:lock_release+0x6bc/0xa20 kernel/locking/lockdep.c:5682
Code: ff e8 88 d7 47 09 41 f7 c5 00 02 00 00 75 8c eb 8b 0f 0b e9 34 fa ff ff 48 c7 c7 60 3a 0c 8b 48 89 d3 e8 77 e7 e7 ff 48 89 da <0f> 0b e9 dc fb ff ff 48 c7 c1 74 40 9b 8e 80 e1 07 80 c1 03 38 c1
RSP: 0018:ffffc90005c4fb40 EFLAGS: 00010046
RAX: b9f816ecdca46400 RBX: 0000000000000000 RCX: 0000000000080000
RDX: 0000000000000000 RSI: 00000000000243e1 RDI: 00000000000243e2
RBP: ffffc90005c4fc70 R08: ffffffff8152b84e R09: ffffed10171e4f1c
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff8880259a28a0
R13: 0000000000000000 R14: 0000000000000000 R15: dffffc0000000000
FS: 00007fcc4ec956c0(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f9a7f369160 CR3: 0000000063737000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
up_write+0x75/0x580 kernel/locking/rwsem.c:1625
do_new_mount_fc fs/namespace.c:2985 [inline]
do_new_mount+0x3f9/0xb40 fs/namespace.c:3058
do_mount fs/namespace.c:3399 [inline]
__do_sys_mount fs/namespace.c:3607 [inline]
__se_sys_mount+0x2d5/0x3c0 fs/namespace.c:3584
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:0x7fcc4dd874ca
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 1a 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fcc4ec94e68 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007fcc4ec94ef0 RCX: 00007fcc4dd874ca
RDX: 0000000020000040 RSI: 0000000020000980 RDI: 00007fcc4ec94eb0
RBP: 0000000020000040 R08: 00007fcc4ec94ef0 R09: 0000000000800000
R10: 0000000000800000 R11: 0000000000000246 R12: 0000000020000980
R13: 00007fcc4ec94eb0 R14: 000000000001f855 R15: 0000000020000640
</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]

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