[v6.1] kernel BUG in gfs2_withdraw

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: e4d90d63d385 Linux 6.1.119
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11ed20df980000
kernel config: https://syzkaller.appspot.com/x/.config?x=393f8074c5fb7ad6
dashboard link: https://syzkaller.appspot.com/bug?extid=b5670e57ae64c7037216
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/3986cbf4f35a/disk-e4d90d63.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d2963d16cebb/vmlinux-e4d90d63.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a877a1a23701/Image-e4d90d63.gz.xz

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

bh = 2 (magic number)
function = gfs2_meta_buffer, file = fs/gfs2/meta_io.c, line = 492
gfs2: fsid=}.0: about to withdraw this file system
------------[ cut here ]------------
kernel BUG at fs/gfs2/util.c:352!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 9563 Comm: syz.4.906 Not tainted 6.1.119-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : gfs2_withdraw+0x1338/0x140c fs/gfs2/util.c:352
lr : gfs2_withdraw+0x1338/0x140c fs/gfs2/util.c:352
sp : ffff800021216c00
x29: ffff800021216d20 x28: ffff800021216c80 x27: ffff700004242d90
x26: dfff800000000000 x25: 1fffe0001876d057 x24: 000000000000076e
x23: 0000000000000000 x22: ffff0000c3b68340 x21: ffff0000c3b680a8
x20: ffff0000c3b682bc x19: ffff0000c3b68000 x18: 1fffe000367a0576
x17: ffff800015a7d000 x16: ffff800012325074 x15: ffff0001b3d02bbc
x14: 1ffff00002b500b2 x13: dfff800000000000 x12: 0000000000080000
x11: 0000000000029c61 x10: ffff800028799000 x9 : ffff80000a49b37c
x8 : 0000000000029c62 x7 : ffff800008277348 x6 : 0000000000000000
x5 : 0000000000000080 x4 : 0000000000000001 x3 : ffff800008585a08
x2 : 0000000000000001 x1 : 0000000000000004 x0 : 0000000000000000
Call trace:
gfs2_withdraw+0x1338/0x140c fs/gfs2/util.c:352
gfs2_meta_check_ii+0x80/0x9c fs/gfs2/util.c:511
gfs2_metatype_check_i fs/gfs2/util.h:126 [inline]
gfs2_meta_buffer+0x2c8/0x394 fs/gfs2/meta_io.c:492
__fillup_metapath+0x144/0x2a0 fs/gfs2/bmap.c:330
lookup_metapath fs/gfs2/bmap.c:357 [inline]
__gfs2_iomap_get+0x514/0x1058 fs/gfs2/bmap.c:904
gfs2_iomap_get fs/gfs2/bmap.c:1396 [inline]
gfs2_block_map+0x254/0x7c0 fs/gfs2/bmap.c:1211
gfs2_write_alloc_required+0x2dc/0x544 fs/gfs2/bmap.c:2320
gfs2_jdesc_check+0x19c/0x264 fs/gfs2/super.c:114
init_journal+0xb78/0x2054 fs/gfs2/ops_fstype.c:804
init_inodes+0xe0/0x2d8 fs/gfs2/ops_fstype.c:889
gfs2_fill_super+0x16fc/0x1ef8 fs/gfs2/ops_fstype.c:1246
get_tree_bdev+0x360/0x54c fs/super.c:1366
gfs2_get_tree+0x54/0x1b4 fs/gfs2/ops_fstype.c:1327
vfs_get_tree+0x90/0x274 fs/super.c:1573
do_new_mount+0x278/0x8fc fs/namespace.c:3056
path_mount+0x590/0xe5c fs/namespace.c:3386
do_mount fs/namespace.c:3399 [inline]
__do_sys_mount fs/namespace.c:3607 [inline]
__se_sys_mount fs/namespace.c:3584 [inline]
__arm64_sys_mount+0x45c/0x594 fs/namespace.c:3584
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
Code: f94013e0 97936455 17ffff55 97815d25 (d4210000)
---[ end trace 0000000000000000 ]---


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

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: e4d90d63d385 Linux 6.1.119
git tree: linux-6.1.y

console output: https://syzkaller.appspot.com/x/log.txt?x=102715e8580000

kernel config: https://syzkaller.appspot.com/x/.config?x=393f8074c5fb7ad6
dashboard link: https://syzkaller.appspot.com/bug?extid=b5670e57ae64c7037216
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17fa3d30580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16f3bf78580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/3986cbf4f35a/disk-e4d90d63.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d2963d16cebb/vmlinux-e4d90d63.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a877a1a23701/Image-e4d90d63.gz.xz

mounted in repro: https://storage.googleapis.com/syzbot-assets/23861e57e99e/mount_0.gz

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

gfs2: fsid=}: Trying to join cluster "lock_nolock", "}"
gfs2: fsid=}: Now mounting FS (format 1801)...
gfs2: fsid=}.0: fatal: invalid metadata block

bh = 2 (magic number)
function = gfs2_meta_buffer, file = fs/gfs2/meta_io.c, line = 492
gfs2: fsid=}.0: about to withdraw this file system
------------[ cut here ]------------
kernel BUG at fs/gfs2/util.c:352!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:

CPU: 1 PID: 4293 Comm: syz-executor291 Not tainted 6.1.119-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : gfs2_withdraw+0x1338/0x140c fs/gfs2/util.c:352
lr : gfs2_withdraw+0x1338/0x140c fs/gfs2/util.c:352

sp : ffff800021676c00
x29: ffff800021676d20 x28: ffff800021676c80 x27: ffff7000042ced90
x26: dfff800000000000 x25: 1fffe0001a0df857 x24: 000000000000076e
x23: 0000000000000000 x22: ffff0000d06fc340 x21: ffff0000d06fc0a8
x20: ffff0000d06fc2bc x19: ffff0000d06fc000 x18: ffff8000216761c0
x17: 0000000000000000 x16: ffff800012325074 x15: 0000000000000000
x14: 00000000ffffffff x13: 0000000000000001 x12: 0000000000000001
x11: 0000000000ff0100 x10: 0000000000000000 x9 : ffff80000a49b37c
x8 : ffff0000d3828000 x7 : 0000000000000001 x6 : 0000000000000001
x5 : ffff800021676518 x4 : ffff800015b630e0 x3 : ffff800008585a08

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.