[v6.1] BUG: unable to handle kernel paging request in gfs2_glock_dq

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3369c6df2fae Linux 6.1.146
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=117c0fd4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=aafe227a6f76c0c3
dashboard link: https://syzkaller.appspot.com/bug?extid=01b86fba73fa58210336
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
userspace arch: arm64

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c6c6f55858e8/disk-3369c6df.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a99117bdae3d/vmlinux-3369c6df.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9ca71d7a5035/Image-3369c6df.gz.xz

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

Unable to handle kernel paging request at virtual address dfff800000000007
KASAN: null-ptr-deref in range [0x0000000000000038-0x000000000000003f]
Mem abort info:
ESR = 0x0000000096000006
EC = 0x25: DABT (current EL), IL = 32 bits
SET = 0, FnV = 0
EA = 0, S1PTW = 0
FSC = 0x06: level 2 translation fault
Data abort info:
ISV = 0, ISS = 0x00000006
CM = 0, WnR = 0
[dfff800000000007] address between user and kernel address ranges
Internal error: Oops: 0000000096000006 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 5105 Comm: syz.1.175 Not tainted 6.1.146-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
pstate: 804000c5 (Nzcv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : __lock_acquire+0xe0/0x6544 kernel/locking/lockdep.c:4919
lr : lock_acquire+0x20c/0x644 kernel/locking/lockdep.c:5662
sp : ffff800020be77c0
x29: ffff800020be79c0 x28: dfff800000000000 x27: 0000000000000000
x26: ffff80000a18d400 x25: 1ffff00002a160b0 x24: 0000000000000000
x23: 0000000000000000 x22: 0000000000000000 x21: 0000000000000000
x20: 0000000000000038 x19: 0000000000000000 x18: 0000000000000000
x17: ffff8000181e7000 x16: ffff800008042c60 x15: ffff800017cc7fc0
x14: ffff0000d95f8a98 x13: 1ffff00002a160b1 x12: 0000000000080000
x11: 0000000000000ac1 x10: ffff70000417cf18 x9 : ffff8000150b0584
x8 : 0000000000000007 x7 : ffff80000a18d400 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : 0000000000000000
x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000038
Call trace:
__lock_acquire+0xe0/0x6544 kernel/locking/lockdep.c:4919
lock_acquire+0x20c/0x644 kernel/locking/lockdep.c:5662
__raw_spin_lock include/linux/spinlock_api_smp.h:133 [inline]
_raw_spin_lock+0x54/0x6c kernel/locking/spinlock.c:154
spin_lock include/linux/spinlock.h:351 [inline]
gfs2_glock_dq+0x48/0x194 fs/gfs2/glock.c:1709
gfs2_glock_dq_uninit+0x30/0xe8 fs/gfs2/glock.c:1738
gfs2_seek_hole+0x17c/0x23c fs/gfs2/inode.c:2128
gfs2_llseek+0x110/0x258 fs/gfs2/file.c:78
vfs_llseek fs/read_write.c:289 [inline]
ksys_lseek fs/read_write.c:302 [inline]
__do_sys_lseek fs/read_write.c:313 [inline]
__se_sys_lseek fs/read_write.c:311 [inline]
__arm64_sys_lseek+0x13c/0x1c0 fs/read_write.c:311
__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/0x138 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: b0067408 b9474108 340001c8 d343fe88 (387c6908)
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
0: b0067408 adrp x8, 0xce81000
4: b9474108 ldr w8, [x8, #1856]
8: 340001c8 cbz w8, 0x40
c: d343fe88 lsr x8, x20, #3
* 10: 387c6908 ldrb w8, [x8, x28] <-- trapping instruction


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

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