[v5.15] BUG: unable to handle kernel NULL pointer dereference in f2fs_update_meta_page

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 9465fef4ae35 Linux 5.15.153
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=12db2f03180000
kernel config: https://syzkaller.appspot.com/x/.config?x=176c746ee3348b33
dashboard link: https://syzkaller.appspot.com/bug?extid=b998afe9239e90678c06
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17d25d9d180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14802cc5180000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/2962c02652ce/disk-9465fef4.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d0f5a1ce082d/vmlinux-9465fef4.xz
kernel image: https://storage.googleapis.com/syzbot-assets/86b5b1eea636/bzImage-9465fef4.xz
mounted in repro #1: https://storage.googleapis.com/syzbot-assets/c077ef5d366a/mount_0.gz
mounted in repro #2: https://storage.googleapis.com/syzbot-assets/f97ffae9cd70/mount_1.gz

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

BUG: kernel NULL pointer dereference, address: 0000000000000000
#PF: supervisor instruction fetch in kernel mode
#PF: error_code(0x0010) - not-present page
PGD 0 P4D 0
Oops: 0010 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 3534 Comm: syz-executor127 Not tainted 5.15.153-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
RIP: 0010:0x0
Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.
RSP: 0018:ffffc90002e676f8 EFLAGS: 00010282
RAX: 1ffffffff152dc4b RBX: ffffea0001bf8900 RCX: ffffffff8a96e258
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffea0001bf8900
RBP: ffffc90002e678f0 R08: ffffffff81ab2159 R09: fffff9400037f121
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88807e046310
R13: 0000000000000001 R14: ffff88807d8bc000 R15: ffff888078e20000
FS: 00005555573aa380(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffd6 CR3: 000000007d8c8000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
f2fs_update_meta_page+0x45/0x60 fs/f2fs/segment.c:2468
do_checkpoint+0x1dc5/0x4310 fs/f2fs/checkpoint.c:1539
f2fs_write_checkpoint+0x126f/0x1b50 fs/f2fs/checkpoint.c:1700
f2fs_issue_checkpoint+0x2d8/0x4c0 fs/f2fs/checkpoint.c:1861
sync_filesystem+0x1bc/0x220 fs/sync.c:66
generic_shutdown_super+0x6e/0x2c0 fs/super.c:448
kill_block_super+0x7a/0xe0 fs/super.c:1414
kill_f2fs_super+0x2ff/0x3c0 fs/f2fs/super.c:4539
deactivate_locked_super+0xa0/0x110 fs/super.c:335
cleanup_mnt+0x44e/0x500 fs/namespace.c:1143
task_work_run+0x129/0x1a0 kernel/task_work.c:164
tracehook_notify_resume include/linux/tracehook.h:189 [inline]
exit_to_user_mode_loop+0x106/0x130 kernel/entry/common.c:175
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:208
__syscall_exit_to_user_mode_work kernel/entry/common.c:290 [inline]
syscall_exit_to_user_mode+0x5d/0x250 kernel/entry/common.c:301
do_syscall_64+0x49/0xb0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x61/0xcb
RIP: 0033:0x7f1eadd03587
Code: 07 00 48 83 c4 08 5b 5d c3 66 2e 0f 1f 84 00 00 00 00 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 a6 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 c7 c2 b8 ff ff ff f7 d8 64 89 02 b8
RSP: 002b:00007ffc1020a528 EFLAGS: 00000206 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007f1eadd03587
RDX: 0000000000000000 RSI: 000000000000000a RDI: 00007ffc1020a5e0
RBP: 00007ffc1020a5e0 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000206 R12: 00007ffc1020b650
R13: 00005555573ab6c0 R14: 431bde82d7b634db R15: 00007ffc1020b670
</TASK>
Modules linked in:
CR2: 0000000000000000
---[ end trace 584b94ba3c12e80e ]---
RIP: 0010:0x0
Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6.
RSP: 0018:ffffc90002e676f8 EFLAGS: 00010282
RAX: 1ffffffff152dc4b RBX: ffffea0001bf8900 RCX: ffffffff8a96e258
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffea0001bf8900
RBP: ffffc90002e678f0 R08: ffffffff81ab2159 R09: fffff9400037f121
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88807e046310
R13: 0000000000000001 R14: ffff88807d8bc000 R15: ffff888078e20000
FS: 00005555573aa380(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffd6 CR3: 000000007d8c8000 CR4: 00000000003506f0
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 syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

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