WARNING in f2fs_submit_page_bio (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 8034e99d1a01 Linux 4.14.266
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11571674700000
kernel config: https://syzkaller.appspot.com/x/.config?x=647e517ce784ab05
dashboard link: https://syzkaller.appspot.com/bug?extid=268b2623c9f28f189a14
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)

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

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

vfs_write+0x17f/0x4d0 fs/read_write.c:544
SYSC_pwrite64 fs/read_write.c:632 [inline]
SyS_pwrite64+0x116/0x140 fs/read_write.c:619
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
------------[ cut here ]------------
entry_SYSCALL_64_after_hwframe+0x46/0xbb
WARNING: CPU: 0 PID: 11469 at fs/f2fs/checkpoint.c:150 f2fs_is_valid_blkaddr+0x2d9/0x920 fs/f2fs/checkpoint.c:148
RIP: 0033:0x7fc3e98d6027
Kernel panic - not syncing: panic_on_warn set ...

RSP: 002b:00007fc3e8297f00 EFLAGS: 00000293 ORIG_RAX: 0000000000000012
RAX: ffffffffffffffda RBX: 00007fc3e996c9c8 RCX: 00007fc3e98d6027
RDX: 0000000000000020 RSI: 0000000020011200 RDI: 0000000000000004
RBP: 0000000000000026 R08: 0000000000000000 R09: 00007fc3e82981d0
R10: 0000000000004000 R11: 0000000000000293 R12: 0000000000000004
R13: 0000000000000004 R14: 00000000200002f0 R15: 000000000000000a
CPU: 0 PID: 11469 Comm: syz-executor.4 Not tainted 4.14.266-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x281 lib/dump_stack.c:58
panic+0x1f9/0x42d kernel/panic.c:183
__warn.cold+0x20/0x44 kernel/panic.c:547
report_bug+0x208/0x250 lib/bug.c:183
fixup_bug arch/x86/kernel/traps.c:177 [inline]
fixup_bug arch/x86/kernel/traps.c:172 [inline]
do_error_trap+0x195/0x2d0 arch/x86/kernel/traps.c:295
invalid_op+0x1b/0x40 arch/x86/entry/entry_64.S:964
RIP: 0010:f2fs_is_valid_blkaddr+0x2d9/0x920 fs/f2fs/checkpoint.c:150
RSP: 0018:ffff88805680f820 EFLAGS: 00010286
RAX: dffffc0000000000 RBX: ffff888096ca83c0 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffff8880a2786c48 RDI: 0000000000000001
RBP: 0000000000000005 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000400
R13: 0000000000000001 R14: 0000000000001000 R15: 0000000000000200
f2fs_submit_page_bio+0x10a/0x1380 fs/f2fs/data.c:377
read_node_page+0x209/0x2f0 fs/f2fs/node.c:1128
__get_node_page.part.0+0x97/0xea0 fs/f2fs/node.c:1173
__get_node_page fs/f2fs/node.c:37 [inline]
get_node_page+0xdd/0x170 fs/f2fs/node.c:1219
do_read_inode fs/f2fs/inode.c:264 [inline]
f2fs_iget+0x1e8/0x3760 fs/f2fs/inode.c:360
f2fs_fill_super+0x30ac/0x56a0 fs/f2fs/super.c:2622
mount_bdev+0x2b3/0x360 fs/super.c:1134
mount_fs+0x92/0x2a0 fs/super.c:1237
vfs_kern_mount.part.0+0x5b/0x470 fs/namespace.c:1046
vfs_kern_mount fs/namespace.c:1036 [inline]
do_new_mount fs/namespace.c:2572 [inline]
do_mount+0xe65/0x2a10 fs/namespace.c:2902
SYSC_mount fs/namespace.c:3118 [inline]
SyS_mount+0xa8/0x120 fs/namespace.c:3095
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x7fa2a56d858a
RSP: 002b:00007fa2a404bf88 EFLAGS: 00000206 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000020000200 RCX: 00007fa2a56d858a
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007fa2a404bfe0
RBP: 00007fa2a404c020 R08: 00007fa2a404c020 R09: 0000000020000000
R10: 0000000000000000 R11: 0000000000000206 R12: 0000000020000000
R13: 0000000020000100 R14: 00007fa2a404bfe0 R15: 0000000020000040
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.