WARNING in f2fs_submit_page_bio (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3f8a27f9e27b Linux 4.19.211
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1324fb19880000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=12176fc97b0a02a9d99a
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/98c0bdb4abb3/disk-3f8a27f9.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ea228ff02669/vmlinux-3f8a27f9.xz

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

__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2ef lib/dump_stack.c:118
fail_dump lib/fault-inject.c:51 [inline]
should_fail.cold+0xa/0xf lib/fault-inject.c:149
__should_failslab+0x115/0x180 mm/failslab.c:32
should_failslab+0x5/0x10 mm/slab_common.c:1590
slab_pre_alloc_hook mm/slab.h:424 [inline]
slab_alloc mm/slab.c:3383 [inline]
kmem_cache_alloc+0x3f/0x370 mm/slab.c:3557
WARNING: CPU: 1 PID: 32319 at fs/f2fs/checkpoint.c:166 f2fs_is_valid_blkaddr+0x35d/0xa20 fs/f2fs/checkpoint.c:166
mempool_alloc+0x146/0x350 mm/mempool.c:385
Kernel panic - not syncing: panic_on_warn set ...

bio_alloc_bioset+0x389/0x5e0 block/bio.c:489
bio_alloc include/linux/bio.h:437 [inline]
submit_bh_wbc+0x141/0x760 fs/buffer.c:3064
submit_bh fs/buffer.c:3096 [inline]
ll_rw_block+0x1ed/0x220 fs/buffer.c:3146
__block_write_begin_int+0x95a/0x17b0 fs/buffer.c:2008
ext4_da_write_begin+0x4e1/0x10e0 fs/ext4/inode.c:3109
generic_perform_write+0x1f8/0x4d0 mm/filemap.c:3170
__generic_file_write_iter+0x24b/0x610 mm/filemap.c:3295
ext4_file_write_iter+0x2fe/0xf20 fs/ext4/file.c:272
call_write_iter include/linux/fs.h:1821 [inline]
new_sync_write fs/read_write.c:474 [inline]
__vfs_write+0x51b/0x770 fs/read_write.c:487
vfs_write+0x1f3/0x540 fs/read_write.c:549
ksys_write+0x12b/0x2a0 fs/read_write.c:599
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7f22c85845a9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 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:00007f22c6ab5168 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007f22c86a5120 RCX: 00007f22c85845a9
RDX: 000000000000001a RSI: 00000000200002c0 RDI: 0000000000000008
RBP: 00007f22c6ab51d0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001
R13: 00007ffe442b5c4f R14: 00007f22c6ab5300 R15: 0000000000022000
CPU: 1 PID: 32319 Comm: syz-executor.2 Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2ef lib/dump_stack.c:118
panic+0x26a/0x50e kernel/panic.c:186
__warn.cold+0x20/0x5a kernel/panic.c:541
report_bug+0x262/0x2b0 lib/bug.c:183
fixup_bug arch/x86/kernel/traps.c:178 [inline]
fixup_bug arch/x86/kernel/traps.c:173 [inline]
do_error_trap+0x1d7/0x310 arch/x86/kernel/traps.c:296
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:1038
RIP: 0010:f2fs_is_valid_blkaddr+0x35d/0xa20 fs/f2fs/checkpoint.c:166
Code: 7a 06 00 00 48 8b 7d 00 44 89 e1 48 c7 c2 40 1a a8 88 48 c7 c6 e0 18 a8 88 e8 bf fa fd ff 48 c7 c7 80 1a a8 88 e8 fe 34 de 04 <0f> 0b 45 31 ed e9 3f fe ff ff e8 84 03 4d fe 48 8d bd 40 01 00 00
RSP: 0018:ffff888045c57740 EFLAGS: 00010282
RAX: 0000000000000024 RBX: 0000000000000005 RCX: 0000000000000000
RDX: 0000000000040000 RSI: ffffffff814dff01 RDI: ffffed1008b8aeda
RBP: ffff88804709d1c0 R08: 0000000000000024 R09: 0000000000000000
R10: 0000000000000005 R11: 0000000000000000 R12: 0000000000100100
R13: ffff8880abf85c80 R14: 0000000000004000 R15: 0000000000000200
f2fs_submit_page_bio+0x138/0x1580 fs/f2fs/data.c:450
read_node_page+0x496/0x630 fs/f2fs/node.c:1303
__get_node_page.part.0+0x9b/0x14b0 fs/f2fs/node.c:1348
__get_node_page fs/f2fs/node.c:38 [inline]
f2fs_get_node_page+0x109/0x1a0 fs/f2fs/node.c:1394
do_read_inode fs/f2fs/inode.c:306 [inline]
f2fs_iget+0x22a/0x4ce0 fs/f2fs/inode.c:439
f2fs_fill_super+0x34b4/0x7050 fs/f2fs/super.c:3056
mount_bdev+0x2fc/0x3b0 fs/super.c:1158
mount_fs+0xa3/0x310 fs/super.c:1261
vfs_kern_mount.part.0+0x68/0x470 fs/namespace.c:961
vfs_kern_mount fs/namespace.c:951 [inline]
do_new_mount fs/namespace.c:2492 [inline]
do_mount+0x115c/0x2f50 fs/namespace.c:2822
ksys_mount+0xcf/0x130 fs/namespace.c:3038
__do_sys_mount fs/namespace.c:3052 [inline]
__se_sys_mount fs/namespace.c:3049 [inline]
__x64_sys_mount+0xba/0x150 fs/namespace.c:3049
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7f8b32dc4ada
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:00007f8b31335f88 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000020000200 RCX: 00007f8b32dc4ada
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007f8b31335fe0
RBP: 00007f8b31336020 R08: 00007f8b31336020 R09: 0000000020000000
R10: 0000000000000000 R11: 0000000000000202 R12: 0000000020000000
R13: 0000000020000100 R14: 00007f8b31335fe0 R15: 00000000200007c0
Kernel Offset: disabled
Rebooting in 86400 seconds..


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

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.