[v5.15] general protection fault in gfs2_remove_from_journal

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: f7347f400572 Linux 5.15.180
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16c0a470580000
kernel config: https://syzkaller.appspot.com/x/.config?x=a2f42e34471bc17b
dashboard link: https://syzkaller.appspot.com/bug?extid=be90b9b02750edcc34ea
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: https://storage.googleapis.com/syzbot-assets/3c09658e7170/disk-f7347f40.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/9939817f914d/vmlinux-f7347f40.xz
kernel image: https://storage.googleapis.com/syzbot-assets/18e0f7a4f25f/bzImage-f7347f40.xz

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

general protection fault, probably for non-canonical address 0xdffffc0000000005: 0000 [#1] PREEMPT SMP KASAN
KASAN: null-ptr-deref in range [0x0000000000000028-0x000000000000002f]
CPU: 1 PID: 4173 Comm: syz-executor Not tainted 5.15.180-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
RIP: 0010:gfs2_remove_from_journal+0x3be/0x6a0 fs/gfs2/meta_io.c:351
Code: e1 80 e1 07 80 c1 03 38 c1 7c 2c 4c 89 e7 e8 19 7b 32 fe eb 22 e8 92 87 e8 fd 48 8b 6c 24 10 4c 8d 65 2c 4c 89 e0 48 c1 e8 03 <42> 0f b6 04 28 84 c0 0f 85 8c 01 00 00 41 ff 04 24 48 8d 7d 18 be
RSP: 0018:ffffc90002e9f6c0 EFLAGS: 00010207
RAX: 0000000000000005 RBX: ffff88807ebaa150 RCX: ffff888026c8d940
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000001
RBP: 0000000000000000 R08: ffffffff8398160f R09: ffffed100ee8e1e1
R10: 0000000000000000 R11: dffffc0000000001 R12: 000000000000002c
R13: dffffc0000000000 R14: ffff88805f5b3570 R15: ffff888077470000
FS: 000055557e6a3500(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f749d1016fc CR3: 00000000620ea000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
gfs2_discard fs/gfs2/aops.c:660 [inline]
gfs2_invalidatepage+0x699/0x890 fs/gfs2/aops.c:693
do_invalidatepage mm/truncate.c:157 [inline]
truncate_cleanup_page+0x179/0x440 mm/truncate.c:176
truncate_inode_pages_range+0x2e7/0x1290 mm/truncate.c:325
gfs2_evict_inode+0x924/0x1320 fs/gfs2/super.c:1415
evict+0x529/0x930 fs/inode.c:647
gfs2_put_super+0x31a/0x7c0 fs/gfs2/super.c:603
generic_shutdown_super+0x130/0x310 fs/super.c:475
kill_block_super+0x7a/0xe0 fs/super.c:1427
deactivate_locked_super+0xa0/0x110 fs/super.c:335
cleanup_mnt+0x44e/0x500 fs/namespace.c:1143
task_work_run+0x129/0x1a0 kernel/task_work.c:188
tracehook_notify_resume include/linux/tracehook.h:189 [inline]
exit_to_user_mode_loop+0x106/0x130 kernel/entry/common.c:181
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:214
__syscall_exit_to_user_mode_work kernel/entry/common.c:296 [inline]
syscall_exit_to_user_mode+0x5d/0x240 kernel/entry/common.c:307
do_syscall_64+0x47/0xb0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f329e34a497
Code: a8 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 0f 1f 44 00 00 31 f6 e9 09 00 00 00 66 0f 1f 84 00 00 00 00 00 b8 a6 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 c7 c2 a8 ff ff ff f7 d8 64 89 02 b8
RSP: 002b:00007ffed2a7fc08 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 00007f329e3cb854 RCX: 00007f329e34a497
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007ffed2a7fcc0
RBP: 00007ffed2a7fcc0 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000246 R12: 00007ffed2a80d50
R13: 00007f329e3cb854 R14: 000000000001a6eb R15: 00007ffed2a80d90
</TASK>
Modules linked in:
---[ end trace 9dc044f82aab6422 ]---
RIP: 0010:gfs2_remove_from_journal+0x3be/0x6a0 fs/gfs2/meta_io.c:351
Code: e1 80 e1 07 80 c1 03 38 c1 7c 2c 4c 89 e7 e8 19 7b 32 fe eb 22 e8 92 87 e8 fd 48 8b 6c 24 10 4c 8d 65 2c 4c 89 e0 48 c1 e8 03 <42> 0f b6 04 28 84 c0 0f 85 8c 01 00 00 41 ff 04 24 48 8d 7d 18 be
RSP: 0018:ffffc90002e9f6c0 EFLAGS: 00010207
RAX: 0000000000000005 RBX: ffff88807ebaa150 RCX: ffff888026c8d940
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000001
RBP: 0000000000000000 R08: ffffffff8398160f R09: ffffed100ee8e1e1
R10: 0000000000000000 R11: dffffc0000000001 R12: 000000000000002c
R13: dffffc0000000000 R14: ffff88805f5b3570 R15: ffff888077470000
FS: 000055557e6a3500(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f749d1016fc CR3: 00000000620ea000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: e1 80 loope 0xffffff82
2: e1 07 loope 0xb
4: 80 c1 03 add $0x3,%cl
7: 38 c1 cmp %al,%cl
9: 7c 2c jl 0x37
b: 4c 89 e7 mov %r12,%rdi
e: e8 19 7b 32 fe call 0xfe327b2c
13: eb 22 jmp 0x37
15: e8 92 87 e8 fd call 0xfde887ac
1a: 48 8b 6c 24 10 mov 0x10(%rsp),%rbp
1f: 4c 8d 65 2c lea 0x2c(%rbp),%r12
23: 4c 89 e0 mov %r12,%rax
26: 48 c1 e8 03 shr $0x3,%rax
* 2a: 42 0f b6 04 28 movzbl (%rax,%r13,1),%eax <-- trapping instruction
2f: 84 c0 test %al,%al
31: 0f 85 8c 01 00 00 jne 0x1c3
37: 41 ff 04 24 incl (%r12)
3b: 48 8d 7d 18 lea 0x18(%rbp),%rdi
3f: be .byte 0xbe


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