syzbot


BUG: unable to handle kernel NULL pointer dereference in filemap_read_folio

Status: upstream: reported on 2022/10/20 13:25
Reported-by: syzbot+e33c2a7e25ff31df5297@syzkaller.appspotmail.com
First crash: 46d, last: 30d

Sample crash report:
ntfs: volume version 3.1.
BUG: kernel NULL pointer dereference, address: 0000000000000000
#PF: supervisor instruction fetch in kernel mode
#PF: error_code(0x0010) - not-present page
PGD 7bba8067 P4D 7bba8067 PUD 3428d067 PMD 0 
Oops: 0010 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 4932 Comm: syz-executor.0 Not tainted 6.1.0-rc2-syzkaller-00105-gb229b6ca5abb #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/11/2022
RIP: 0010:0x0
Code: Unable to access opcode bytes at 0xffffffffffffffd6.
RSP: 0018:ffffc90005d5f618 EFLAGS: 00010283
RAX: ffffffff81b52218 RBX: 0000000000000000 RCX: 0000000000040000
RDX: ffffc90004cf1000 RSI: ffffea0000eb2440 RDI: 0000000000000000
RBP: ffffc90005d5f700 R08: dffffc0000000000 R09: fffff940001d6489
R10: fffff940001d6489 R11: 1ffffd40001d6488 R12: 0000000000000000
R13: dffffc0000000000 R14: ffffea0000eb2440 R15: ffffea0000eb2448
FS:  00007fcc60d76700(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffd6 CR3: 0000000076440000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 filemap_read_folio+0x187/0x7d0 mm/filemap.c:2407
 do_read_cache_folio+0x2d3/0x790 mm/filemap.c:3534
 do_read_cache_page mm/filemap.c:3576 [inline]
 read_cache_page+0x56/0x270 mm/filemap.c:3585
 read_mapping_page include/linux/pagemap.h:756 [inline]
 ntfs_map_page fs/ntfs/aops.h:75 [inline]
 ntfs_check_logfile+0x381/0x28f0 fs/ntfs/logfile.c:532
 load_and_check_logfile+0x6f/0xd0 fs/ntfs/super.c:1215
 load_system_files+0x31f4/0x4870 fs/ntfs/super.c:1941
 ntfs_fill_super+0x19a9/0x2bf0 fs/ntfs/super.c:2892
 mount_bdev+0x26c/0x3a0 fs/super.c:1400
 legacy_get_tree+0xea/0x180 fs/fs_context.c:610
 vfs_get_tree+0x88/0x270 fs/super.c:1530
 do_new_mount+0x289/0xad0 fs/namespace.c:3040
 do_mount fs/namespace.c:3383 [inline]
 __do_sys_mount fs/namespace.c:3591 [inline]
 __se_sys_mount+0x2d3/0x3c0 fs/namespace.c:3568
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7fcc6008cada
Code: 48 c7 c2 b8 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff eb d2 e8 b8 04 00 00 0f 1f 84 00 00 00 00 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fcc60d75f88 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000020000200 RCX: 00007fcc6008cada
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007fcc60d75fe0
RBP: 00007fcc60d76020 R08: 00007fcc60d76020 R09: 0000000020000000
R10: 0000000000000000 R11: 0000000000000202 R12: 0000000020000000
R13: 0000000020000100 R14: 00007fcc60d75fe0 R15: 0000000020077ea0
 </TASK>
Modules linked in:
CR2: 0000000000000000
---[ end trace 0000000000000000 ]---
RIP: 0010:0x0
Code: Unable to access opcode bytes at 0xffffffffffffffd6.
RSP: 0018:ffffc90005d5f618 EFLAGS: 00010283
RAX: ffffffff81b52218 RBX: 0000000000000000 RCX: 0000000000040000
RDX: ffffc90004cf1000 RSI: ffffea0000eb2440 RDI: 0000000000000000
RBP: ffffc90005d5f700 R08: dffffc0000000000 R09: fffff940001d6489
R10: fffff940001d6489 R11: 1ffffd40001d6488 R12: 0000000000000000
R13: dffffc0000000000 R14: ffffea0000eb2440 R15: ffffea0000eb2448
FS:  00007fcc60d76700(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffd6 CR3: 0000000076440000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400

Crashes (8):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Title
ci2-upstream-fs 2022/10/29 19:26 upstream b229b6ca5abb 2a71366b .config log report info BUG: unable to handle kernel NULL pointer dereference in filemap_read_folio
ci2-upstream-fs 2022/10/26 13:51 upstream 4dc12f37a8e9 2159e4d2 .config log report info BUG: unable to handle kernel NULL pointer dereference in filemap_read_folio
ci-upstream-kasan-gce-root 2022/10/23 08:32 upstream d47136c28015 c0b80a55 .config log report info BUG: unable to handle kernel NULL pointer dereference in filemap_read_folio
ci-upstream-kasan-gce-smack-root 2022/10/20 13:24 upstream 55be6084c8e0 b31320fc .config log report info BUG: unable to handle kernel NULL pointer dereference in filemap_read_folio
ci2-upstream-fs 2022/10/18 23:53 upstream 493ffd6605b2 b31320fc .config log report info BUG: unable to handle kernel NULL pointer dereference in filemap_read_folio
ci2-upstream-fs 2022/10/18 16:06 upstream 493ffd6605b2 b31320fc .config log report info BUG: unable to handle kernel NULL pointer dereference in filemap_read_folio
ci2-upstream-fs 2022/10/15 18:45 upstream 493ffd6605b2 67cb024c .config log report info BUG: unable to handle kernel NULL pointer dereference in filemap_read_folio
ci2-upstream-fs 2022/10/13 19:45 upstream 493ffd6605b2 adf90437 .config log report info BUG: unable to handle kernel NULL pointer dereference in filemap_read_folio
* Struck through repros no longer work on HEAD.