[moderation] [ntfs3?] BUG: unable to handle kernel paging request in evict (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: e5fa841af679 Merge tag 'pull-fixes' of git://git.kernel.or..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=168ddc5b980000
kernel config: https://syzkaller.appspot.com/x/.config?x=73debf7508ac7a0b
dashboard link: https://syzkaller.appspot.com/bug?extid=65f9282ba28d4b906049
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 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/d5e570f2796f/disk-e5fa841a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7c7a0a6c5996/vmlinux-e5fa841a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b00150a1d74e/bzImage-e5fa841a.xz

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

BUG: unable to handle page fault for address: ffffffffffffffc8
#PF: supervisor write access in kernel mode
#PF: error_code(0x0002) - not-present page
PGD db80067 P4D db80067 PUD db82067 PMD 0
Oops: Oops: 0002 [#1] PREEMPT SMP KASAN NOPTI
CPU: 1 UID: 0 PID: 10190 Comm: syz.4.1967 Not tainted 6.11.0-rc3-syzkaller-00279-ge5fa841af679 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
RIP: 0010:lock_acquire kernel/locking/lockdep.c:5759 [inline]
RIP: 0010:lock_acquire+0x1b0/0x560 kernel/locking/lockdep.c:5724
Code: 02 00 00 4c 89 f7 6a 00 41 0f 94 c1 48 89 c5 6a 00 45 0f b6 c9 ff b4 24 00 01 00 00 41 57 8b 4c 24 2c 8b 74 24 28 e8 3f ad ff <ff> 48 c7 c7 00 da 4c 8b 48 83 c4 28 e8 4f 38 a8 09 b8 ff ff ff ff
RSP: 0018:ffffc90002e5f838 EFLAGS: 00010086
RAX: 0000000000000001 RBX: 1ffff920005cbf0e RCX: 0000000000000001
RDX: 0000000000000001 RSI: 0000000000000008 RDI: ffffffff93632818
RBP: 0000000000000200 R08: 0000000000000000 R09: fffffbfff28c8301
R10: ffffffff9464180f R11: 0000000000000000 R12: 0000000000000001
R13: 0000000000000000 R14: ffff88805c4e3650 R15: 0000000000000000
FS: 00007fbfc1b6d6c0(0000) GS:ffff8880b9300000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffc8 CR3: 000000001f9fa000 CR4: 0000000000350ef0
Call Trace:
<TASK>
__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]
inode_wait_for_lru_isolating fs/inode.c:510 [inline]
evict+0x310/0x8c0 fs/inode.c:693
iput_final fs/inode.c:1838 [inline]
iput.part.0+0x5a8/0x7f0 fs/inode.c:1864
iput+0x5c/0x80 fs/inode.c:1854
ntfs_fill_super+0x3325/0x41a0 fs/ntfs3/super.c:1467
get_tree_bdev+0x372/0x610 fs/super.c:1635
vfs_get_tree+0x92/0x380 fs/super.c:1800
do_new_mount fs/namespace.c:3472 [inline]
path_mount+0x14e6/0x1f20 fs/namespace.c:3799
do_mount fs/namespace.c:3812 [inline]
__do_sys_mount fs/namespace.c:4020 [inline]
__se_sys_mount fs/namespace.c:3997 [inline]
__x64_sys_mount+0x294/0x320 fs/namespace.c:3997
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fbfc0d7b61a
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:00007fbfc1b6ce68 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007fbfc1b6cef0 RCX: 00007fbfc0d7b61a
RDX: 000000002001f800 RSI: 0000000020000000 RDI: 00007fbfc1b6ceb0
RBP: 000000002001f800 R08: 00007fbfc1b6cef0 R09: 0000000000800840
R10: 0000000000800840 R11: 0000000000000246 R12: 0000000020000000
R13: 00007fbfc1b6ceb0 R14: 000000000001f85d R15: 0000000020000080
</TASK>
Modules linked in:
CR2: ffffffffffffffc8
---[ end trace 0000000000000000 ]---
RIP: 0010:lock_acquire kernel/locking/lockdep.c:5759 [inline]
RIP: 0010:lock_acquire+0x1b0/0x560 kernel/locking/lockdep.c:5724
Code: 02 00 00 4c 89 f7 6a 00 41 0f 94 c1 48 89 c5 6a 00 45 0f b6 c9 ff b4 24 00 01 00 00 41 57 8b 4c 24 2c 8b 74 24 28 e8 3f ad ff <ff> 48 c7 c7 00 da 4c 8b 48 83 c4 28 e8 4f 38 a8 09 b8 ff ff ff ff
RSP: 0018:ffffc90002e5f838 EFLAGS: 00010086
RAX: 0000000000000001 RBX: 1ffff920005cbf0e RCX: 0000000000000001
RDX: 0000000000000001 RSI: 0000000000000008 RDI: ffffffff93632818
RBP: 0000000000000200 R08: 0000000000000000 R09: fffffbfff28c8301
R10: ffffffff9464180f R11: 0000000000000000 R12: 0000000000000001
R13: 0000000000000000 R14: ffff88805c4e3650 R15: 0000000000000000
FS: 00007fbfc1b6d6c0(0000) GS:ffff8880b9300000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffc8 CR3: 000000001f9fa000 CR4: 0000000000350ef0


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