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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 7367539ad4b0 Merge tag 'cxl-fixes-6.9-rc7' of git://git.ke..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1763f1f8980000
kernel config: https://syzkaller.appspot.com/x/.config?x=3310e643b6ef5d69
dashboard link: https://syzkaller.appspot.com/bug?extid=5d868aac999baa886346
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
CC: [ak...@linux-foundation.org linux-...@vger.kernel.org linu...@kvack.org]

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

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7bc7510fe41f/non_bootable_disk-7367539a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1f814bef5f63/vmlinux-7367539a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/cd1f53098470/bzImage-7367539a.xz

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

loop3: detected capacity change from 0 to 4096
BUG: unable to handle page fault for address: fffffffd8953061c
#PF: supervisor write access in kernel mode
#PF: error_code(0x0002) - not-present page
PGD d57e067 P4D d57e067 PUD 0
Oops: 0002 [#1] PREEMPT SMP KASAN NOPTI
CPU: 2 PID: 5908 Comm: syz-executor.3 Not tainted 6.9.0-rc6-syzkaller-00234-g7367539ad4b0 #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
RIP: 0010:alloc_pages_mpol+0x274/0x610 mm/mempolicy.c:2264
Code: 00 44 89 fe e8 fd 82 a7 ff 45 85 ff 75 05 45 31 ff eb 5f e8 0e 88 a7 ff 8b 54 24 58 44 89 e6 44 89 ef 48 8b 0c 24 e8 cb 26 f7 <ff> 4c 89 f2 48 c1 ea 03 49 89 c7 48 b8 00 00 00 00 00 fc ff df 0f
RSP: 0018:ffffc9000345f898 EFLAGS: 00010286
RAX: ffffea000123f340 RBX: 1ffff9200068bf16 RCX: ffffffff81dd67a2
RDX: 0000000000000000 RSI: ffffffff8b6f5520 RDI: ffffffff8d261b50
RBP: ffffffff946d5340 R08: 0000000000000000 R09: fffffbfff1f3ea42
R10: ffffffff8f9f5217 R11: 0000000000000001 R12: 0000000000000000
R13: 0000000000140cca R14: ffffffff946d5344 R15: 0000000000000001
FS: 00007f7380bc06c0(0000) GS:ffff88806b400000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: fffffffd8953061c CR3: 000000003d546000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
folio_alloc+0x1e/0x40 mm/mempolicy.c:2342
filemap_alloc_folio+0x3ba/0x490 mm/filemap.c:984
do_read_cache_folio+0x1b6/0x540 mm/filemap.c:3711
do_read_cache_page mm/filemap.c:3813 [inline]
read_cache_page+0x5b/0x160 mm/filemap.c:3822
read_mapping_page include/linux/pagemap.h:888 [inline]
ntfs_map_page fs/ntfs3/ntfs_fs.h:922 [inline]
ntfs_fill_super+0x3899/0x4490 fs/ntfs3/super.c:1501
get_tree_bdev+0x36f/0x610 fs/super.c:1614
vfs_get_tree+0x8f/0x380 fs/super.c:1779
do_new_mount fs/namespace.c:3352 [inline]
path_mount+0x14e6/0x1f20 fs/namespace.c:3679
do_mount fs/namespace.c:3692 [inline]
__do_sys_mount fs/namespace.c:3898 [inline]
__se_sys_mount fs/namespace.c:3875 [inline]
__x64_sys_mount+0x297/0x320 fs/namespace.c:3875
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcf/0x260 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f737fe7f3aa
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:00007f7380bbfef8 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f7380bbff80 RCX: 00007f737fe7f3aa
RDX: 0000000020000000 RSI: 0000000020000200 RDI: 00007f7380bbff40
RBP: 0000000020000000 R08: 00007f7380bbff80 R09: 000000000000c040
R10: 000000000000c040 R11: 0000000000000202 R12: 0000000020000200
R13: 00007f7380bbff40 R14: 000000000001f77e R15: 0000000020000100
</TASK>
Modules linked in:
CR2: fffffffd8953061c
---[ end trace 0000000000000000 ]---
RIP: 0010:alloc_pages_mpol+0x274/0x610 mm/mempolicy.c:2264
Code: 00 44 89 fe e8 fd 82 a7 ff 45 85 ff 75 05 45 31 ff eb 5f e8 0e 88 a7 ff 8b 54 24 58 44 89 e6 44 89 ef 48 8b 0c 24 e8 cb 26 f7 <ff> 4c 89 f2 48 c1 ea 03 49 89 c7 48 b8 00 00 00 00 00 fc ff df 0f
RSP: 0018:ffffc9000345f898 EFLAGS: 00010286
RAX: ffffea000123f340 RBX: 1ffff9200068bf16 RCX: ffffffff81dd67a2
RDX: 0000000000000000 RSI: ffffffff8b6f5520 RDI: ffffffff8d261b50
RBP: ffffffff946d5340 R08: 0000000000000000 R09: fffffbfff1f3ea42
R10: ffffffff8f9f5217 R11: 0000000000000001 R12: 0000000000000000
R13: 0000000000140cca R14: ffffffff946d5344 R15: 0000000000000001
FS: 00007f7380bc06c0(0000) GS:ffff88806b400000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: fffffffd8953061c CR3: 000000003d546000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


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