syzbot


BUG: unable to handle kernel paging request in mi_init

Status: upstream: reported on 2025/02/14 06:55
Subsystems: ntfs3
[Documentation on labels]
Reported-by: syzbot+8282d8328968be03242e@syzkaller.appspotmail.com
First crash: 151d, last: 2d00h
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [ntfs3?] BUG: unable to handle kernel paging request in mi_init 0 (1) 2025/02/14 06:55

Sample crash report:
loop0: detected capacity change from 0 to 4096
ntfs3(loop0): Different NTFS sector size (2048) and media sector size (512).
BUG: unable to handle page fault for address: ffffed11087e875b
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
PGD 5ffcd067 P4D 5ffcd067 PUD 0 
Oops: Oops: 0000 [#1] SMP KASAN NOPTI
CPU: 0 UID: 0 PID: 5312 Comm: syz.0.0 Not tainted 6.15.0-syzkaller-03589-gfeacb1774bd5 #0 PREEMPT(full) 
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
RIP: 0010:mi_init+0x84/0xe0 fs/ntfs3/record.c:105
Code: 89 f0 48 c1 e8 03 42 0f b6 04 20 84 c0 75 5f 41 8b 3e be 40 0c 00 00 e8 6a cc 0f ff 49 89 c6 48 83 c3 20 48 89 d8 48 c1 e8 03 <42> 80 3c 20 00 74 08 48 89 df e8 0d 97 1a ff 4c 89 33 31 c9 4d 85
RSP: 0018:ffffc9000d35f730 EFLAGS: 00010a06
RAX: 1ffff110087e875c RBX: ffff888043f43ae0 RCX: 6a1cb85f4e65e600
RDX: 0000000000000800 RSI: ffffffff8be24de0 RDI: ffffffff8be24da0
RBP: 000000000000000a R08: 0000000000000c40 R09: 00000000ffffffff
R10: dffffc0000000000 R11: fffffbfff1f3fd17 R12: dffffc00ffffffff
R13: ffff8880332ca7d4 R14: ffff888043ab8000 R15: ffff888043f43b38
FS:  00007ff858ba06c0(0000) GS:ffff88808d28c000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffed11087e875b CR3: 0000000035453000 CR4: 0000000000352ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 ntfs_read_mft fs/ntfs3/inode.c:54 [inline]
 ntfs_iget5+0x356/0x37c0 fs/ntfs3/inode.c:540
 ntfs_fill_super+0x3940/0x40c0 fs/ntfs3/super.c:1518
 get_tree_bdev_flags+0x40b/0x4d0 fs/super.c:1686
 vfs_get_tree+0x8f/0x2b0 fs/super.c:1809
 do_new_mount+0x24a/0xa40 fs/namespace.c:3882
 do_mount fs/namespace.c:4222 [inline]
 __do_sys_mount fs/namespace.c:4433 [inline]
 __se_sys_mount+0x317/0x410 fs/namespace.c:4410
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7ff857d9010a
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:00007ff858b9fe68 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007ff858b9fef0 RCX: 00007ff857d9010a
RDX: 000020000001f340 RSI: 0000200000000040 RDI: 00007ff858b9feb0
RBP: 000020000001f340 R08: 00007ff858b9fef0 R09: 0000000000000890
R10: 0000000000000890 R11: 0000000000000246 R12: 0000200000000040
R13: 00007ff858b9feb0 R14: 000000000001f335 R15: 0000200000000380
 </TASK>
Modules linked in:
CR2: ffffed11087e875b
---[ end trace 0000000000000000 ]---
RIP: 0010:mi_init+0x84/0xe0 fs/ntfs3/record.c:105
Code: 89 f0 48 c1 e8 03 42 0f b6 04 20 84 c0 75 5f 41 8b 3e be 40 0c 00 00 e8 6a cc 0f ff 49 89 c6 48 83 c3 20 48 89 d8 48 c1 e8 03 <42> 80 3c 20 00 74 08 48 89 df e8 0d 97 1a ff 4c 89 33 31 c9 4d 85
RSP: 0018:ffffc9000d35f730 EFLAGS: 00010a06
RAX: 1ffff110087e875c RBX: ffff888043f43ae0 RCX: 6a1cb85f4e65e600
RDX: 0000000000000800 RSI: ffffffff8be24de0 RDI: ffffffff8be24da0
RBP: 000000000000000a R08: 0000000000000c40 R09: 00000000ffffffff
R10: dffffc0000000000 R11: fffffbfff1f3fd17 R12: dffffc00ffffffff
R13: ffff8880332ca7d4 R14: ffff888043ab8000 R15: ffff888043f43b38
FS:  00007ff858ba06c0(0000) GS:ffff88808d28c000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffed11087e875b CR3: 0000000035453000 CR4: 0000000000352ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
   0:	89 f0                	mov    %esi,%eax
   2:	48 c1 e8 03          	shr    $0x3,%rax
   6:	42 0f b6 04 20       	movzbl (%rax,%r12,1),%eax
   b:	84 c0                	test   %al,%al
   d:	75 5f                	jne    0x6e
   f:	41 8b 3e             	mov    (%r14),%edi
  12:	be 40 0c 00 00       	mov    $0xc40,%esi
  17:	e8 6a cc 0f ff       	call   0xff0fcc86
  1c:	49 89 c6             	mov    %rax,%r14
  1f:	48 83 c3 20          	add    $0x20,%rbx
  23:	48 89 d8             	mov    %rbx,%rax
  26:	48 c1 e8 03          	shr    $0x3,%rax
* 2a:	42 80 3c 20 00       	cmpb   $0x0,(%rax,%r12,1) <-- trapping instruction
  2f:	74 08                	je     0x39
  31:	48 89 df             	mov    %rbx,%rdi
  34:	e8 0d 97 1a ff       	call   0xff1a9746
  39:	4c 89 33             	mov    %r14,(%rbx)
  3c:	31 c9                	xor    %ecx,%ecx
  3e:	4d                   	rex.WRB
  3f:	85                   	.byte 0x85

Crashes (13):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/05/29 00:35 upstream feacb1774bd5 3d2f584d .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root BUG: unable to handle kernel paging request in mi_init
2025/04/08 03:47 upstream 0af2f6be1b42 a2ada0e7 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root BUG: unable to handle kernel paging request in mi_init
2025/02/28 12:57 upstream 76544811c850 1e7a43e1 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root BUG: unable to handle kernel paging request in mi_init
2025/02/28 02:54 upstream 1e15510b71c9 6a8fcbc4 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root BUG: unable to handle kernel paging request in mi_init
2025/02/25 22:12 upstream 2a1944bff549 d34966d1 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root BUG: unable to handle kernel paging request in mi_init
2025/02/22 12:43 upstream ff202c5028a1 d34966d1 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root BUG: unable to handle kernel paging request in mi_init
2025/02/19 07:29 upstream 6537cfb395f3 9a14138f .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root BUG: unable to handle kernel paging request in mi_init
2025/02/19 02:50 upstream 6537cfb395f3 9a14138f .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root BUG: unable to handle kernel paging request in mi_init
2025/02/14 06:54 upstream ab68d7eb7b1a d9a046cf .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root BUG: unable to handle kernel paging request in mi_init
2025/02/12 20:40 upstream 09fbf3d50205 b27c2402 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root BUG: unable to handle kernel paging request in mi_init
2025/01/20 05:08 upstream 9528d418de4d f2cb035c .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root BUG: unable to handle kernel paging request in mi_init
2025/01/15 07:34 upstream c3812b15000c 7315a7cf .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root BUG: unable to handle kernel paging request in mi_init
2024/12/30 03:02 upstream 4099a71718b0 d3ccff63 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root BUG: unable to handle kernel paging request in mi_init
* Struck through repros no longer work on HEAD.