WARNING in gfs2_rbm_from_block

[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=16daf21b880000
kernel config: https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link: https://syzkaller.appspot.com/bug?extid=e2124d980d57ca9ad4c6
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=143b22d7880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16927b8f880000

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
mounted in repro: https://storage.googleapis.com/syzbot-assets/66c873fc7fbe/mount_0.gz

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

gfs2: fsid=syz:syz.0: journal 0 mapped with 3 extents
gfs2: fsid=syz:syz.0: jid=0, already locked for use
gfs2: fsid=syz:syz.0: jid=0: Looking at journal...
gfs2: fsid=syz:syz.0: jid=0: Done
gfs2: fsid=syz:syz.0: first mount done, others may mount
WARNING: CPU: 0 PID: 8101 at fs/gfs2/rgrp.c:274 gfs2_rbm_from_block+0x26b/0x2f0 fs/gfs2/rgrp.c:274
Kernel panic - not syncing: panic_on_warn set ...

CPU: 0 PID: 8101 Comm: syz-executor103 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:gfs2_rbm_from_block+0x26b/0x2f0 fs/gfs2/rgrp.c:274
Code: 3c 01 00 00 45 31 f6 29 c3 41 89 5c 24 08 e8 9c 84 57 fe 44 89 f0 48 83 c4 08 5b 5d 41 5c 41 5d 41 5e 41 5f c3 e8 85 84 57 fe <0f> 0b 41 be ea ff ff ff eb da e8 a6 63 8d fe e9 7f fe ff ff e8 cc
RSP: 0018:ffff8880b05f7920 EFLAGS: 00010293
RAX: ffff8880b3e740c0 RBX: ffffffffffffffff RCX: ffffffff830afeee
RDX: 0000000000000000 RSI: ffffffff830b00eb RDI: 0000000000000007
RBP: 1ffff110160bef2d R08: 0000000000000000 R09: 00000000ffffffff
R10: 0000000000000007 R11: 0000000000000000 R12: ffff8880b05f7988
R13: ffff8880a57cef00 R14: 0000000000000012 R15: 0000000000000013
gfs2_check_blk_type+0x103/0x2e0 fs/gfs2/rgrp.c:2557
gfs2_inode_lookup+0x727/0xa50 fs/gfs2/inode.c:165
gfs2_lookup_by_inum+0x44/0x170 fs/gfs2/inode.c:225
gfs2_get_dentry fs/gfs2/export.c:140 [inline]
gfs2_fh_to_dentry fs/gfs2/export.c:163 [inline]
gfs2_fh_to_dentry+0x20c/0x290 fs/gfs2/export.c:147
exportfs_decode_fh+0x126/0x7e0 fs/exportfs/expfs.c:433
do_handle_to_path fs/fhandle.c:152 [inline]
handle_to_path fs/fhandle.c:207 [inline]
do_handle_open+0x2f4/0x650 fs/fhandle.c:223
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7f5b0bf747a9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 51 14 00 00 90 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 c0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffc16d7a2a8 EFLAGS: 00000246 ORIG_RAX: 0000000000000130
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f5b0bf747a9
RDX: 0000000000000000 RSI: 0000000020000100 RDI: 0000000000000004
RBP: 00007f5b0bf34040 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000000124d6 R11: 0000000000000246 R12: 00007f5b0bf340d0
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
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 can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches