[v6.1] WARNING: locking bug in evict

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 6741e066ec76 Linux 6.1.87
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=158bda4f180000
kernel config: https://syzkaller.appspot.com/x/.config?x=3fc2f61bd0ae457
dashboard link: https://syzkaller.appspot.com/bug?extid=6817231ba2e4e6b7a7a8
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13625ae7180000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b606a22ddf4b/disk-6741e066.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e31c21737449/vmlinux-6741e066.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ee0cb8c049e9/bzImage-6741e066.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/8caedfd31e63/mount_0.gz

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

------------[ cut here ]------------
DEBUG_LOCKS_WARN_ON(1)
WARNING: CPU: 1 PID: 3956 at kernel/locking/lockdep.c:232 __lock_acquire+0x138b/0x1f80 kernel/locking/lockdep.c:5045
Modules linked in:
CPU: 1 PID: 3956 Comm: syz-executor.0 Not tainted 6.1.87-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
RIP: 0010:hlock_class kernel/locking/lockdep.c:232 [inline]
RIP: 0010:__lock_acquire+0x138b/0x1f80 kernel/locking/lockdep.c:5045
Code: 83 3d d0 2e 09 0d 00 0f 85 00 fe ff ff 48 c7 c7 60 00 ec 8a 48 c7 c6 00 03 ec 8a e8 af 0e e8 ff 48 bf 00 00 00 00 00 fc ff df <0f> 0b e9 dc fd ff ff 49 89 d6 48 c7 c7 60 08 ec 8a e8 1f 07 1e 09
RSP: 0000:ffffc9000524f800 EFLAGS: 00010046
RAX: 4389476327720900 RBX: 0000000000001300 RCX: ffff888021359dc0
RDX: 0000000000000000 RSI: 0000000000000000 RDI: dffffc0000000000
RBP: 0959c1ea29e0e1a6 R08: ffffffff81528eae R09: fffff52000a49e61
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88802135a898
R13: ffff888021359dc0 R14: 0000000000000000 R15: 1ffff1100426b51d
FS: 00007fcb277fe6c0(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fe0b8afc000 CR3: 00000000220bf000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
lock_acquire+0x1f8/0x5a0 kernel/locking/lockdep.c:5662
__raw_spin_lock include/linux/spinlock_api_smp.h:133 [inline]
_raw_spin_lock+0x2a/0x40 kernel/locking/spinlock.c:154
spin_lock include/linux/spinlock.h:351 [inline]
inode_sb_list_del fs/inode.c:504 [inline]
evict+0x161/0x620 fs/inode.c:655
ntfs_fill_super+0x3c05/0x4410 fs/ntfs3/super.c:1190
get_tree_bdev+0x3fe/0x620 fs/super.c:1355
vfs_get_tree+0x88/0x270 fs/super.c:1562
do_new_mount+0x2ba/0xb40 fs/namespace.c:3051
do_mount fs/namespace.c:3394 [inline]
__do_sys_mount fs/namespace.c:3602 [inline]
__se_sys_mount+0x2d5/0x3c0 fs/namespace.c:3579
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:0x7fcb2847f5aa
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 09 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 b0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fcb277fdef8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007fcb277fdf80 RCX: 00007fcb2847f5aa
RDX: 00000000200000c0 RSI: 000000002001f840 RDI: 00007fcb277fdf40
RBP: 00000000200000c0 R08: 00007fcb277fdf80 R09: 0000000000008058
R10: 0000000000008058 R11: 0000000000000246 R12: 000000002001f840
R13: 00007fcb277fdf40 R14: 000000000001f808 R15: 0000000020000140
</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 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.

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