[syzbot] [ntfs3?] WARNING: locking bug in ntfs_fill_super (2)

Hello,

syzbot found the following issue on:

HEAD commit: 715ca9dd687f Merge tag 'io_uring-6.12-20241019' of git://g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1700ec87980000
kernel config: https://syzkaller.appspot.com/x/.config?x=16e543edc81a3008
dashboard link: https://syzkaller.appspot.com/bug?extid=b856fe782caf1f85be6e
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/7ae9f0c1b9fa/disk-715ca9dd.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/91e10a24baa4/vmlinux-715ca9dd.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f46b6b5990f3/bzImage-715ca9dd.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: [email protected]

loop5: detected capacity change from 0 to 4096
ntfs3(loop5): Different NTFS sector size (2048) and media sector size (512).
------------[ cut here ]------------
DEBUG_LOCKS_WARN_ON(1)
WARNING: CPU: 1 PID: 6340 at kernel/locking/lockdep.c:232 hlock_class kernel/locking/lockdep.c:232 [inline]
WARNING: CPU: 1 PID: 6340 at kernel/locking/lockdep.c:232 __lock_acquire+0x1345/0x2050 kernel/locking/lockdep.c:5199
Modules linked in:
CPU: 1 UID: 0 PID: 6340 Comm: syz.5.66 Not tainted 6.12.0-rc3-syzkaller-00420-g715ca9dd687f #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
RIP: 0010:hlock_class kernel/locking/lockdep.c:232 [inline]
RIP: 0010:__lock_acquire+0x1345/0x2050 kernel/locking/lockdep.c:5199
Code: 00 00 83 3d 2c c1 ac 0e 00 75 23 90 48 c7 c7 60 c9 0a 8c 48 c7 c6 00 cc 0a 8c e8 86 71 e5 ff 48 ba 00 00 00 00 00 fc ff df 90 <0f> 0b 90 90 90 31 db 48 83 c3 40 48 89 d8 48 c1 e8 03 80 3c 10 00
RSP: 0018:ffffc90003f2f650 EFLAGS: 00010046
RAX: 11c528de68187400 RBX: 0000000000000f00 RCX: 0000000000040000
RDX: dffffc0000000000 RSI: 000000000000dc83 RDI: 000000000000dc84
RBP: 39845540049e23b7 R08: ffffffff8155e402 R09: fffffbfff1cf9fe0
R10: dffffc0000000000 R11: fffffbfff1cf9fe0 R12: 0000000000000001
R13: ffff88802e92e4d8 R14: 1ffff11005d25ca5 R15: ffff88802e92e528
FS: 00007f47db4276c0(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020a1a000 CR3: 000000007873e000 CR4: 0000000000350ef0
Call Trace:
<TASK>
lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5825
__raw_spin_lock include/linux/spinlock_api_smp.h:133 [inline]
_raw_spin_lock+0x2e/0x40 kernel/locking/spinlock.c:154
spin_lock include/linux/spinlock.h:351 [inline]
iput_final fs/inode.c:1866 [inline]
iput+0x615/0xa50 fs/inode.c:1903
ntfs_fill_super+0x3e27/0x4730 fs/ntfs3/super.c:1472
get_tree_bdev+0x3f9/0x570 fs/super.c:1635
vfs_get_tree+0x92/0x2b0 fs/super.c:1800
do_new_mount+0x2be/0xb40 fs/namespace.c:3507
do_mount fs/namespace.c:3847 [inline]
__do_sys_mount fs/namespace.c:4055 [inline]
__se_sys_mount+0x2d6/0x3c0 fs/namespace.c:4032
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f47da57f79a
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:00007f47db426e68 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f47db426ef0 RCX: 00007f47da57f79a
RDX: 00000000200000c0 RSI: 0000000020000b00 RDI: 00007f47db426eb0
RBP: 00000000200000c0 R08: 00007f47db426ef0 R09: 0000000000000010
R10: 0000000000000010 R11: 0000000000000246 R12: 0000000020000b00
R13: 00007f47db426eb0 R14: 000000000001f3bc R15: 0000000020000280
</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 [email protected].

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 has found a reproducer for the following issue on:

HEAD commit: 85a2dd7d7c81 Add linux-next specific files for 20241125
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=137ee778580000
kernel config: https://syzkaller.appspot.com/x/.config?x=e348a4873516af92
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14173ee8580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/eff72ae97118/disk-85a2dd7d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/18f336c941c2/vmlinux-85a2dd7d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ddb67e7b7257/bzImage-85a2dd7d.xz
mounted in repro #1: https://storage.googleapis.com/syzbot-assets/0dfd78502424/mount_0.gz
mounted in repro #2: https://storage.googleapis.com/syzbot-assets/48b325f85b71/mount_2.gz
loop0: detected capacity change from 0 to 4096
WARNING: CPU: 1 PID: 10300 at kernel/locking/lockdep.c:232 hlock_class kernel/locking/lockdep.c:232 [inline]
WARNING: CPU: 1 PID: 10300 at kernel/locking/lockdep.c:232 __lock_acquire+0x135a/0x2100 kernel/locking/lockdep.c:5223
Modules linked in:
CPU: 1 UID: 0 PID: 10300 Comm: syz.0.2130 Not tainted 6.12.0-next-20241125-syzkaller #0
RIP: 0010:__lock_acquire+0x135a/0x2100 kernel/locking/lockdep.c:5223
Code: 00 00 83 3d fb 04 9f 0e 00 75 23 90 48 c7 c7 e0 94 0a 8c 48 c7 c6 e0 97 0a 8c e8 b1 54 e5 ff 48 ba 00 00 00 00 00 fc ff df 90 <0f> 0b 90 90 90 31 db 48 83 c3 40 48 89 d8 48 c1 e8 03 80 3c 10 00
RSP: 0018:ffffc9000c03f650 EFLAGS: 00010046
RAX: 89afe599c3bc1700 RBX: 0000000000001700 RCX: ffff88802fd80000
RDX: dffffc0000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 8fe977d821a4f04f R08: ffffffff81601b32 R09: 1ffff110170e519a
R10: dffffc0000000000 R11: ffffed10170e519b R12: ffff88802fd80000
R13: ffff88802fd80000 R14: 1ffff11005fb0165 R15: 0000000000000001
FS: 00007fdea42fe6c0(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CR2: 00007f4631891001 CR3: 0000000031e76000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5849
iput_final fs/inode.c:1935 [inline]
iput+0x615/0xa50 fs/inode.c:1972
ntfs_fill_super+0x3e27/0x4730 fs/ntfs3/super.c:1472
get_tree_bdev_flags+0x48c/0x5c0 fs/super.c:1636
vfs_get_tree+0x90/0x2b0 fs/super.c:1814
__do_sys_mount fs/namespace.c:4057 [inline]
__se_sys_mount+0x2d6/0x3c0 fs/namespace.c:4034
RIP: 0033:0x7fdea357ffba
RSP: 002b:00007fdea42fde68 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007fdea42fdef0 RCX: 00007fdea357ffba
RDX: 0000000020000080 RSI: 000000002001f740 RDI: 00007fdea42fdeb0
RBP: 0000000020000080 R08: 00007fdea42fdef0 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000002001f740
R13: 00007fdea42fdeb0 R14: 000000000001f70e R15: 00000000200000c0
</TASK>


---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.