Hello, syzbot found the following issue on: HEAD commit: 2af3e53a4dc0 Merge tag 'drm-fixes-2023-04-21' of git://ano.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=12f3bf57c80000 kernel config: https://syzkaller.appspot.com/x/.config?x=4afb87f3ec27b7fd dashboard link: https://syzkaller.appspot.com/bug?extid=6310a7df6baca255f9cc compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2 Unfortunately, I don't have any reproducer for this issue yet. Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/845f21360f64/disk-2af3e53a.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/3b9925dc3504/vmlinux-2af3e53a.xz kernel image: https://storage.googleapis.com/syzbot-assets/021758261c12/bzImage-2af3e53a.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+6310a7df6baca255f9cc@xxxxxxxxxxxxxxxxxxxxxxxxx loop5: detected capacity change from 0 to 4096 ------------[ cut here ]------------ DEBUG_LOCKS_WARN_ON(1) WARNING: CPU: 0 PID: 4955 at kernel/locking/lockdep.c:232 hlock_class kernel/locking/lockdep.c:232 [inline] WARNING: CPU: 0 PID: 4955 at kernel/locking/lockdep.c:232 mark_lock+0x14c/0x340 kernel/locking/lockdep.c:4613 Modules linked in: CPU: 0 PID: 4955 Comm: syz-executor.5 Not tainted 6.3.0-rc7-syzkaller-00152-g2af3e53a4dc0 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/30/2023 RIP: 0010:hlock_class kernel/locking/lockdep.c:232 [inline] RIP: 0010:mark_lock+0x14c/0x340 kernel/locking/lockdep.c:4613 Code: 03 42 0f b6 04 28 84 c0 0f 85 d2 01 00 00 83 3d 01 fd e8 0c 00 75 9d 48 c7 c7 40 7c ea 8a 48 c7 c6 e0 7e ea 8a e8 14 fb e7 ff <0f> 0b eb 86 e8 7b 47 ff ff 85 c0 0f 84 33 01 00 00 45 89 f6 4c 89 RSP: 0000:ffffc90005487778 EFLAGS: 00010046 RAX: 15fb29a09693de00 RBX: 0000000000001b00 RCX: 0000000000040000 RDX: ffffc9000e3ef000 RSI: 0000000000007ab5 RDI: 0000000000007ab6 RBP: 0000000000000002 R08: ffffffff81528022 R09: ffffed101730515b R10: 0000000000000000 R11: dffffc0000000001 R12: ffff888046b9c4b0 R13: dffffc0000000000 R14: 0000000000000004 R15: ffff888046b9c4df FS: 00007f42a5e55700(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f7ddc767000 CR3: 0000000053d39000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> mark_usage kernel/locking/lockdep.c:4544 [inline] __lock_acquire+0xc0d/0x1f80 kernel/locking/lockdep.c:5010 lock_acquire+0x1e1/0x520 kernel/locking/lockdep.c:5669 __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:350 [inline] inode_sb_list_del fs/inode.c:503 [inline] evict+0x161/0x620 fs/inode.c:654 ntfs_fill_super+0x3ffc/0x47f0 fs/ntfs3/super.c:1239 get_tree_bdev+0x402/0x620 fs/super.c:1303 vfs_get_tree+0x8c/0x270 fs/super.c:1510 do_new_mount+0x28f/0xae0 fs/namespace.c:3042 do_mount fs/namespace.c:3385 [inline] __do_sys_mount fs/namespace.c:3594 [inline] __se_sys_mount+0x2d9/0x3c0 fs/namespace.c:3571 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f42a508d69a Code: 48 c7 c2 b8 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff eb d2 e8 b8 04 00 00 0f 1f 84 00 00 00 00 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f42a5e54f88 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5 RAX: ffffffffffffffda RBX: 000000000001f6cc RCX: 00007f42a508d69a RDX: 000000002001f700 RSI: 000000002001f740 RDI: 00007f42a5e54fe0 RBP: 00007f42a5e55020 R08: 00007f42a5e55020 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000202 R12: 000000002001f700 R13: 000000002001f740 R14: 00007f42a5e54fe0 R15: 000000002001f780 </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 syzkaller@xxxxxxxxxxxxxxxx. syzbot will keep track of this issue. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
