syzbot


BUG: unable to handle kernel NULL pointer dereference in get_next_nat_page

Status: moderation: reported on 2022/04/06 16:20
Reported-by: syzbot+5e2426815f625f449a45@syzkaller.appspotmail.com
First crash: 184d, last: 83d

Sample crash report:
BUG: kernel NULL pointer dereference, address: 0000000000000000
#PF: supervisor instruction fetch in kernel mode
#PF: error_code(0x0010) - not-present page
PGD 74746067 P4D 74746067 PUD 0 
Oops: 0010 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 18777 Comm: syz-executor.5 Not tainted 5.19.0-rc6-syzkaller-00104-g72a8e05d4f66 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/29/2022
RIP: 0010:0x0
Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.
RSP: 0018:ffffc90004bb75a0 EFLAGS: 00010292
RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffff888025793b00
RDX: 0000000000000000 RSI: ffffea000281a280 RDI: ffff888034e403b8
RBP: ffffea000282a7c0 R08: ffffffff81b5e24b R09: fffff94000503451
R10: fffff94000503451 R11: 1ffffd4000503450 R12: ffffea000282a7c0
R13: dffffc0000000000 R14: ffffea000281a280 R15: ffffea000282a7c8
FS:  0000555556f50400(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffd6 CR3: 000000002872d000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 get_next_nat_page+0x3a9/0x770 fs/f2fs/node.c:154
 __flush_nat_entry_set fs/f2fs/node.c:3007 [inline]
 f2fs_flush_nat_entries+0x9f7/0x1d10 fs/f2fs/node.c:3111
 f2fs_write_checkpoint+0x14f1/0x1d70 fs/f2fs/checkpoint.c:1669
 f2fs_issue_checkpoint+0x361/0x4e0
 sync_filesystem+0x1bc/0x220 fs/sync.c:66
 generic_shutdown_super+0x6b/0x300 fs/super.c:445
 kill_block_super+0x79/0xd0 fs/super.c:1394
 kill_f2fs_super+0x2f9/0x3c0 fs/f2fs/super.c:4516
 deactivate_locked_super+0xa7/0xf0 fs/super.c:332
 cleanup_mnt+0x452/0x500 fs/namespace.c:1186
 task_work_run+0x146/0x1c0 kernel/task_work.c:177
 resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
 exit_to_user_mode_loop+0x134/0x160 kernel/entry/common.c:169
 exit_to_user_mode_prepare+0xad/0x110 kernel/entry/common.c:201
 __syscall_exit_to_user_mode_work kernel/entry/common.c:283 [inline]
 syscall_exit_to_user_mode+0x2e/0x60 kernel/entry/common.c:294
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f4bbd68a577
Code: ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 66 0f 1f 44 00 00 31 f6 e9 09 00 00 00 66 0f 1f 84 00 00 00 00 00 b8 a6 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:00007ffdb1f7f498 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007f4bbd68a577
RDX: 00007ffdb1f7f56a RSI: 000000000000000a RDI: 00007ffdb1f7f560
RBP: 00007ffdb1f7f560 R08: 00000000ffffffff R09: 00007ffdb1f7f330
R10: 0000555556f518b3 R11: 0000000000000246 R12: 00007f4bbd6e21c8
R13: 00007ffdb1f80620 R14: 0000555556f51810 R15: 00007ffdb1f80660
 </TASK>
Modules linked in:
CR2: 0000000000000000
---[ end trace 0000000000000000 ]---
RIP: 0010:0x0
Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.
RSP: 0018:ffffc90004bb75a0 EFLAGS: 00010292
RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffff888025793b00
RDX: 0000000000000000 RSI: ffffea000281a280 RDI: ffff888034e403b8
RBP: ffffea000282a7c0 R08: ffffffff81b5e24b R09: fffff94000503451
R10: fffff94000503451 R11: 1ffffd4000503450 R12: ffffea000282a7c0
R13: dffffc0000000000 R14: ffffea000281a280 R15: ffffea000282a7c8
FS:  0000555556f50400(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffd6 CR3: 000000002872d000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400

Crashes (3):
Manager Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Title
ci-upstream-kasan-gce-smack-root 2022/07/12 19:21 upstream 72a8e05d4f66 d91dd8ea .config log report info BUG: unable to handle kernel NULL pointer dereference in get_next_nat_page
ci-upstream-kasan-gce-smack-root 2022/06/12 07:17 upstream 7a68065eb9cd 0d5abf15 .config log report info BUG: unable to handle kernel NULL pointer dereference in get_next_nat_page
ci-upstream-kasan-gce-smack-root 2022/04/02 16:16 upstream 88e6c0207623 79a2a8fc .config log report info BUG: unable to handle kernel NULL pointer dereference in get_next_nat_page
* Struck through repros no longer work on HEAD.