[syzbot] [gfs2?] general protection fault in gfs2_glock_dq

[syzbot <syzbot+48ae9388c13bf60ba2c9@syzkaller.appspotmail.com>]

Hello,

syzbot found the following issue on:

HEAD commit:    42f7652d3eb5 Linux 6.12-rc4
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12e81a40580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=fc6f8ce8c5369043
dashboard link: https://syzkaller.appspot.com/bug?extid=48ae9388c13bf60ba2c9
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

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

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7feb34a89c2a/non_bootable_disk-42f7652d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/27fd6c638478/vmlinux-42f7652d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a5f529516264/bzImage-42f7652d.xz

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

UDPLite: UDP-Lite is deprecated and scheduled to be removed in 2025, please contact the netdev mailing list
loop0: detected capacity change from 0 to 32768
gfs2: fsid=syz:syz: Trying to join cluster "lock_nolock", "syz:syz"
gfs2: fsid=syz:syz: Now mounting FS (format 1801)...
gfs2: fsid=syz:syz.0: journal 0 mapped with 1 extents in 0ms
gfs2: fsid=syz:syz.0: first mount done, others may mount
loop0: detected capacity change from 32768 to 64
syz.0.0: attempt to access beyond end of device
loop0: rw=1, sector=2972, nr_sectors = 18 limit=64
gfs2: fsid=syz:syz.0: Error 10 writing to journal, jid=0
Oops: general protection fault, probably for non-canonical address 0xdffffc0000000002: 0000 [#1] PREEMPT SMP KASAN NOPTI
KASAN: null-ptr-deref in range [0x0000000000000010-0x0000000000000017]
CPU: 0 UID: 0 PID: 5104 Comm: syz.0.0 Not tainted 6.12.0-rc4-syzkaller #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014
RIP: 0010:gfs2_glock_dq+0x4d/0xa60 fs/gfs2/glock.c:1690
Code: fd 4d 8d 65 10 4c 89 e5 48 c1 ed 03 80 7c 1d 00 00 74 08 4c 89 e7 e8 e2 58 19 fe 49 8b 0c 24 4c 8d 79 10 4d 89 fe 49 c1 ee 03 <41> 80 3c 1e 00 74 0e 48 89 cb 4c 89 ff e8 c1 58 19 fe 48 89 d9 48
RSP: 0018:ffffc9000b53fc38 EFLAGS: 00010202
RAX: ffffffff83e553d4 RBX: dffffc0000000000 RCX: 0000000000000000
RDX: ffffc9000b5f1000 RSI: 000000000000002f RDI: 0000000000000030
RBP: 1ffff920016a7fa6 R08: ffffffff83e500de R09: 1ffff11009e0b0ad
R10: dffffc0000000000 R11: ffffed1009e0b0ae R12: ffffc9000b53fd30
R13: ffffc9000b53fd20 R14: 0000000000000002 R15: 0000000000000010
FS:  00007efc232b86c0(0000) GS:ffff88801fc00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007efc179ff000 CR3: 000000003f0b0000 CR4: 0000000000352ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 gfs2_glock_dq_uninit+0x25/0xb0 fs/gfs2/glock.c:1748
 gfs2_seek_hole+0x16c/0x240 fs/gfs2/inode.c:2150
 gfs2_llseek+0x11e/0x280 fs/gfs2/file.c:79
 vfs_llseek fs/read_write.c:382 [inline]
 ksys_lseek fs/read_write.c:395 [inline]
 __do_sys_lseek fs/read_write.c:406 [inline]
 __se_sys_lseek fs/read_write.c:404 [inline]
 __x64_sys_lseek+0x150/0x1e0 fs/read_write.c:404
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7efc2257dff9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007efc232b8038 EFLAGS: 00000246 ORIG_RAX: 0000000000000008
RAX: ffffffffffffffda RBX: 00007efc22735f80 RCX: 00007efc2257dff9
RDX: 0000000000000004 RSI: 000000000000054c RDI: 0000000000000009
RBP: 00007efc225f0296 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007efc22735f80 R15: 00007ffd8046dd48
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:gfs2_glock_dq+0x4d/0xa60 fs/gfs2/glock.c:1690
Code: fd 4d 8d 65 10 4c 89 e5 48 c1 ed 03 80 7c 1d 00 00 74 08 4c 89 e7 e8 e2 58 19 fe 49 8b 0c 24 4c 8d 79 10 4d 89 fe 49 c1 ee 03 <41> 80 3c 1e 00 74 0e 48 89 cb 4c 89 ff e8 c1 58 19 fe 48 89 d9 48
RSP: 0018:ffffc9000b53fc38 EFLAGS: 00010202
RAX: ffffffff83e553d4 RBX: dffffc0000000000 RCX: 0000000000000000
RDX: ffffc9000b5f1000 RSI: 000000000000002f RDI: 0000000000000030
RBP: 1ffff920016a7fa6 R08: ffffffff83e500de R09: 1ffff11009e0b0ad
R10: dffffc0000000000 R11: ffffed1009e0b0ae R12: ffffc9000b53fd30
R13: ffffc9000b53fd20 R14: 0000000000000002 R15: 0000000000000010
FS:  00007efc232b86c0(0000) GS:ffff88801fc00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007efc179ff000 CR3: 000000003f0b0000 CR4: 0000000000352ef0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
   0:	fd                   	std
   1:	4d 8d 65 10          	lea    0x10(%r13),%r12
   5:	4c 89 e5             	mov    %r12,%rbp
   8:	48 c1 ed 03          	shr    $0x3,%rbp
   c:	80 7c 1d 00 00       	cmpb   $0x0,0x0(%rbp,%rbx,1)
  11:	74 08                	je     0x1b
  13:	4c 89 e7             	mov    %r12,%rdi
  16:	e8 e2 58 19 fe       	call   0xfe1958fd
  1b:	49 8b 0c 24          	mov    (%r12),%rcx
  1f:	4c 8d 79 10          	lea    0x10(%rcx),%r15
  23:	4d 89 fe             	mov    %r15,%r14
  26:	49 c1 ee 03          	shr    $0x3,%r14
* 2a:	41 80 3c 1e 00       	cmpb   $0x0,(%r14,%rbx,1) <-- trapping instruction
  2f:	74 0e                	je     0x3f
  31:	48 89 cb             	mov    %rcx,%rbx
  34:	4c 89 ff             	mov    %r15,%rdi
  37:	e8 c1 58 19 fe       	call   0xfe1958fd
  3c:	48 89 d9             	mov    %rbx,%rcx
  3f:	48                   	rex.W


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