[syzbot] [gfs2?] kernel BUG in __gfs2_glock_put

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 9abbc24128bc Merge branch 'for-next/core' into for-kernelci
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci
console output: https://syzkaller.appspot.com/x/log.txt?x=10af4008180000
kernel config: https://syzkaller.appspot.com/x/.config?x=af5c6c699e57bbb3
dashboard link: https://syzkaller.appspot.com/bug?extid=335b6972be76fa40c22f
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/ce13ec3ed5ad/disk-9abbc241.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/256cbd314121/vmlinux-9abbc241.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0af86fb52109/Image-9abbc241.gz.xz

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

gfs2: fsid=syz:syz.0: G: s:UN n:2/819 f: t:UN d:EX/0 a:0 v:0 r:-128 m:20 p:1
------------[ cut here ]------------
kernel BUG at fs/gfs2/glock.c:282!
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 7508 Comm: kworker/1:0H Tainted: G B 6.8.0-rc5-syzkaller-g9abbc24128bc #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
Workqueue: glock_workqueue glock_work_func
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : __gfs2_glock_put+0x3f4/0x4ec fs/gfs2/glock.c:282
lr : __gfs2_glock_put+0x3f4/0x4ec fs/gfs2/glock.c:282
sp : ffff8000a4737ac0
x29: ffff8000a4737ac0 x28: 1fffe0002666fd6e x27: dfff800000000000
x26: ffff0000c4ff6408 x25: 0000000000000140 x24: 1fffe00025410015
x23: ffff00012a080000 x22: dfff800000000000 x21: 0000000000000140
x20: ffff00013337ed30 x19: ffff00013337ea40 x18: 1fffe00036804796
x17: ffff80008ec8d000 x16: ffff80008ad5bbdc x15: 0000000000000001
x14: 1ffff000148e6e18 x13: 0000000000000000 x12: 0000000000000000
x11: 0000000000000001 x10: 0000000000ff0100 x9 : 82bd4918e7193700
x8 : 82bd4918e7193700 x7 : 1fffe00036804797 x6 : ffff800080297af0
x5 : 0000000000000000 x4 : 0000000000000001 x3 : ffff800082f22fb0
x2 : 0000000000000001 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
__gfs2_glock_put+0x3f4/0x4ec fs/gfs2/glock.c:282
glock_work_func+0x2ac/0x440 fs/gfs2/glock.c:1109
process_one_work+0x694/0x1204 kernel/workqueue.c:2633
process_scheduled_works kernel/workqueue.c:2706 [inline]
worker_thread+0x938/0xef4 kernel/workqueue.c:2787
kthread+0x288/0x310 kernel/kthread.c:388
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:860
Code: aa1f03e0 aa1303e1 52800022 97fff7f7 (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