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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 7ed2632ec7d7 drm/ttm: fix ttm pool initialization for no-d..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17da9c17e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=bc36d99546fe9035
dashboard link: https://syzkaller.appspot.com/bug?extid=3b3963b76bd3a7c96a6d
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: i386
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-7ed2632e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/5b8998a9800a/vmlinux-7ed2632e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6bd9ae557f26/bzImage-7ed2632e.xz

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

BUG: unable to handle page fault for address: fffffffd8928478d
#PF: supervisor write access in kernel mode
#PF: error_code(0x0002) - not-present page
PGD cf7b067 P4D cf7b067 PUD 0
Oops: 0002 [#1] PREEMPT SMP KASAN
CPU: 3 PID: 9441 Comm: syz-executor.2 Not tainted 6.8.0-rc1-syzkaller-00026-g7ed2632ec7d7 #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+0x257/0x5f0 mm/mempolicy.c:2133
Code: 00 44 89 fe e8 da d4 aa ff 45 85 ff 75 05 45 31 ff eb 5f e8 5b d9 aa ff 8b 54 24 58 44 89 e6 44 89 ef 48 8b 0c 24 e8 58 8f 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:ffffc900200c7880 EFLAGS: 00010286
RAX: ffffea0001510dc0 RBX: 1ffff92004018f13 RCX: ffffffff81d4db1f
RDX: 0000000000000000 RSI: ffffffff8b2fd300 RDI: ffffffff8ca98a78
RBP: ffffffff92a50800 R08: 0000000000000000 R09: fffffbfff1e75d62
R10: ffffffff8f3aeb17 R11: 0000000000000001 R12: 0000000000000000
R13: 0000000000140cca R14: ffffffff92a50804 R15: 0000000000000001
FS: 0000000000000000(0000) GS:ffff88802c900000(0063) knlGS:00000000f7f5ab40
CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
CR2: fffffffd8928478d CR3: 000000001c82c000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
folio_alloc+0x1e/0xe0 mm/mempolicy.c:2211
filemap_alloc_folio+0x3bb/0x490 mm/filemap.c:975
do_read_cache_folio+0x1b8/0x540 mm/filemap.c:3667
do_read_cache_page mm/filemap.c:3769 [inline]
read_cache_page+0x5b/0x160 mm/filemap.c:3778
read_mapping_page include/linux/pagemap.h:888 [inline]
ntfs_map_page fs/ntfs3/ntfs_fs.h:915 [inline]
ntfs_fill_super+0x39ba/0x4490 fs/ntfs3/super.c:1485
get_tree_bdev+0x36b/0x600 fs/super.c:1619
vfs_get_tree+0x8c/0x370 fs/super.c:1784
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]
__ia32_sys_mount+0x291/0x310 fs/namespace.c:3875
do_syscall_32_irqs_on arch/x86/entry/common.c:165 [inline]
__do_fast_syscall_32+0x79/0x110 arch/x86/entry/common.c:321
do_fast_syscall_32+0x33/0x70 arch/x86/entry/common.c:346
entry_SYSENTER_compat_after_hwframe+0x70/0x7a
RIP: 0023:0xf7f5f579
Code: b8 01 10 06 03 74 b4 01 10 07 03 74 b0 01 10 08 03 74 d8 01 00 00 00 00 00 00 00 00 00 00 00 00 00 51 52 55 89 e5 0f 34 cd 80 <5d> 5a 59 c3 90 90 90 90 8d b4 26 00 00 00 00 8d b4 26 00 00 00 00
RSP: 002b:00000000f7f5a400 EFLAGS: 00000292 ORIG_RAX: 0000000000000015
RAX: ffffffffffffffda RBX: 00000000f7f5a460 RCX: 0000000020000200
RDX: 0000000020000040 RSI: 000000000000c040 RDI: 00000000f7f5a4a0
RBP: 00000000f7f5a460 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000296 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
</TASK>
Modules linked in:
CR2: fffffffd8928478d
---[ end trace 0000000000000000 ]---
RIP: 0010:alloc_pages_mpol+0x257/0x5f0 mm/mempolicy.c:2133
Code: 00 44 89 fe e8 da d4 aa ff 45 85 ff 75 05 45 31 ff eb 5f e8 5b d9 aa ff 8b 54 24 58 44 89 e6 44 89 ef 48 8b 0c 24 e8 58 8f 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:ffffc900200c7880 EFLAGS: 00010286
RAX: ffffea0001510dc0 RBX: 1ffff92004018f13 RCX: ffffffff81d4db1f
RDX: 0000000000000000 RSI: ffffffff8b2fd300 RDI: ffffffff8ca98a78
RBP: ffffffff92a50800 R08: 0000000000000000 R09: fffffbfff1e75d62
R10: ffffffff8f3aeb17 R11: 0000000000000001 R12: 0000000000000000
R13: 0000000000140cca R14: ffffffff92a50804 R15: 0000000000000001
FS: 0000000000000000(0000) GS:ffff88802c900000(0063) knlGS:00000000f7f5ab40
CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
CR2: fffffffd8928478d CR3: 000000001c82c000 CR4: 0000000000350ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess), 2 bytes skipped:
0: 10 06 adc %al,(%rsi)
2: 03 74 b4 01 add 0x1(%rsp,%rsi,4),%esi
6: 10 07 adc %al,(%rdi)
8: 03 74 b0 01 add 0x1(%rax,%rsi,4),%esi
c: 10 08 adc %cl,(%rax)
e: 03 74 d8 01 add 0x1(%rax,%rbx,8),%esi
1e: 00 51 52 add %dl,0x52(%rcx)
21: 55 push %rbp
22: 89 e5 mov %esp,%ebp
24: 0f 34 sysenter
26: cd 80 int $0x80
* 28: 5d pop %rbp <-- trapping instruction
29: 5a pop %rdx
2a: 59 pop %rcx
2b: c3 ret
2c: 90 nop
2d: 90 nop
2e: 90 nop
2f: 90 nop
30: 8d b4 26 00 00 00 00 lea 0x0(%rsi,%riz,1),%esi
37: 8d b4 26 00 00 00 00 lea 0x0(%rsi,%riz,1),%esi


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