[moderation] [ntfs3?] WARNING: nested lock was not taken in ntfs_fill_super (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 610a9b8f49fb Linux 6.7-rc8
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1774937ee80000
kernel config: https://syzkaller.appspot.com/x/.config?x=247b5a935d307ee5
dashboard link: https://syzkaller.appspot.com/bug?extid=ef94253d1e5dbdd5abbd
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
CC: [almaz.ale...@paragon-software.com linux-...@vger.kernel.org linux-...@vger.kernel.org nt...@lists.linux.dev]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/e174ec82158f/disk-610a9b8f.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4bed5e1c1c26/vmlinux-610a9b8f.xz
kernel image: https://storage.googleapis.com/syzbot-assets/4fd13b65ecb5/bzImage-610a9b8f.xz

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

loop0: detected capacity change from 0 to 4096
==================================
WARNING: Nested lock was not taken
6.7.0-rc8-syzkaller #0 Not tainted
----------------------------------
syz-executor.0/17897 is trying to lock:
ffff888089125b70 (&sb->s_type->i_lock_key#41){+.+.}-{2:2}, at: spin_lock include/linux/spinlock.h:351 [inline]
ffff888089125b70 (&sb->s_type->i_lock_key#41){+.+.}-{2:2}, at: iput_final fs/inode.c:1766 [inline]
ffff888089125b70 (&sb->s_type->i_lock_key#41){+.+.}-{2:2}, at: iput.part.0+0x464/0x7b0 fs/inode.c:1803

but this task is not holding:
general protection fault, probably for non-canonical address 0xdffffc0020000002: 0000 [#1] PREEMPT SMP KASAN
KASAN: probably user-memory-access in range [0x0000000100000010-0x0000000100000017]
CPU: 0 PID: 17897 Comm: syz-executor.0 Not tainted 6.7.0-rc8-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
RIP: 0010:print_lock_nested_lock_not_held kernel/locking/lockdep.c:4967 [inline]
RIP: 0010:__lock_acquire+0x11e3/0x3b20 kernel/locking/lockdep.c:5128
Code: ff df 48 c1 ea 03 80 3c 02 00 0f 85 38 28 00 00 48 b8 00 00 00 00 00 fc ff df 49 8b 5c 24 18 48 8d 7b 18 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 0a 28 00 00 48 8b 73 18 48 c7 c7 e0 e1 cc 8a e8
RSP: 0018:ffffc90014c57808 EFLAGS: 00010013
RAX: dffffc0000000000 RBX: 00000000ffffffff RCX: ffffc90004d29000
RDX: 0000000020000002 RSI: ffffffff816aea82 RDI: 0000000100000017
RBP: 0000000000000000 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000080000001 R11: 0000000000000001 R12: ffff888025db28a8
R13: ffff888025db1dc0 R14: 0000000000000001 R15: ffffed1004bb650f
FS: 00007febc97ad6c0(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffdec3eaf78 CR3: 0000000028e35000 CR4: 0000000000350ef0
Call Trace:
<TASK>
lock_acquire kernel/locking/lockdep.c:5754 [inline]
lock_acquire+0x1ae/0x520 kernel/locking/lockdep.c:5719
__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:1766 [inline]
iput.part.0+0x464/0x7b0 fs/inode.c:1803
iput+0x5c/0x80 fs/inode.c:1793
ntfs_fill_super+0x3835/0x4490 fs/ntfs3/super.c:1464
get_tree_bdev+0x3b5/0x650 fs/super.c:1598
vfs_get_tree+0x8c/0x370 fs/super.c:1771
do_new_mount fs/namespace.c:3337 [inline]
path_mount+0x1492/0x1ed0 fs/namespace.c:3664
do_mount fs/namespace.c:3677 [inline]
__do_sys_mount fs/namespace.c:3886 [inline]
__se_sys_mount fs/namespace.c:3863 [inline]
__x64_sys_mount+0x293/0x310 fs/namespace.c:3863
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0x40/0x110 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x63/0x6b
RIP: 0033:0x7febc8a7e3ea
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:00007febc97acee8 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007febc97acf80 RCX: 00007febc8a7e3ea
RDX: 000000002001f700 RSI: 000000002001f740 RDI: 00007febc97acf40
RBP: 000000002001f700 R08: 00007febc97acf80 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000202 R12: 000000002001f740
R13: 00007febc97acf40 R14: 000000000001f6ee R15: 00000000200001c0
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:print_lock_nested_lock_not_held kernel/locking/lockdep.c:4967 [inline]
RIP: 0010:__lock_acquire+0x11e3/0x3b20 kernel/locking/lockdep.c:5128
Code: ff df 48 c1 ea 03 80 3c 02 00 0f 85 38 28 00 00 48 b8 00 00 00 00 00 fc ff df 49 8b 5c 24 18 48 8d 7b 18 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 0a 28 00 00 48 8b 73 18 48 c7 c7 e0 e1 cc 8a e8
RSP: 0018:ffffc90014c57808 EFLAGS: 00010013
RAX: dffffc0000000000 RBX: 00000000ffffffff RCX: ffffc90004d29000
RDX: 0000000020000002 RSI: ffffffff816aea82 RDI: 0000000100000017
RBP: 0000000000000000 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000080000001 R11: 0000000000000001 R12: ffff888025db28a8
R13: ffff888025db1dc0 R14: 0000000000000001 R15: ffffed1004bb650f
FS: 00007febc97ad6c0(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffdec3eaf78 CR3: 0000000028e35000 CR4: 0000000000350ef0
----------------
Code disassembly (best guess), 2 bytes skipped:
0: 48 c1 ea 03 shr $0x3,%rdx
4: 80 3c 02 00 cmpb $0x0,(%rdx,%rax,1)
8: 0f 85 38 28 00 00 jne 0x2846
e: 48 b8 00 00 00 00 00 movabs $0xdffffc0000000000,%rax
15: fc ff df
18: 49 8b 5c 24 18 mov 0x18(%r12),%rbx
1d: 48 8d 7b 18 lea 0x18(%rbx),%rdi
21: 48 89 fa mov %rdi,%rdx
24: 48 c1 ea 03 shr $0x3,%rdx
* 28: 80 3c 02 00 cmpb $0x0,(%rdx,%rax,1) <-- trapping instruction
2c: 0f 85 0a 28 00 00 jne 0x283c
32: 48 8b 73 18 mov 0x18(%rbx),%rsi
36: 48 c7 c7 e0 e1 cc 8a mov $0xffffffff8acce1e0,%rdi
3d: e8 .byte 0xe8


---
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.