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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 420102835862 Linux 6.1.134
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17152fe4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=8378dd042adba5b4
dashboard link: https://syzkaller.appspot.com/bug?extid=7267542d8b492df8b564
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/a5ee15572a4a/disk-42010283.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/728dbc1d7c01/vmlinux-42010283.xz
kernel image: https://storage.googleapis.com/syzbot-assets/319d47731f5b/Image-42010283.gz.xz

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

resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
do_notify_resume+0x2080/0x2cb8 arch/arm64/kernel/signal.c:1132
prepare_exit_to_user_mode arch/arm64/kernel/entry-common.c:137 [inline]
exit_to_user_mode arch/arm64/kernel/entry-common.c:142 [inline]
el0_svc+0x9c/0x168 arch/arm64/kernel/entry-common.c:638
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
Unable to handle kernel paging request at virtual address dfff800000000005
KASAN: null-ptr-deref in range [0x0000000000000028-0x000000000000002f]
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
[dfff800000000005] address between user and kernel address ranges
Internal error: Oops: 0000000096000006 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 4308 Comm: syz-executor Not tainted 6.1.134-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : gfs2_remove_from_journal+0x3b4/0x880 fs/gfs2/meta_io.c:350
lr : gfs2_remove_from_journal+0x3a8/0x880 fs/gfs2/meta_io.c:350
sp : ffff800021347120
x29: ffff800021347140 x28: dfff800000000000 x27: ffff0000cae11050
x26: ffff0000f342e170 x25: 1fffe0001bea1c7c x24: 0000000000010000
x23: 000000000000002c x22: 0000000000000000 x21: ffff0000df50e3e0
x20: ffff0000f342e150 x19: ffff0000df50e3a0 x18: ffff800021346ea0
x17: ffff800018c59000 x16: ffff80001232ab6c x15: ffff800018739f80
x14: ffff0000d9490a78 x13: dfff800000000000 x12: 0000000000000001
x11: 0000000000ff0100 x10: 0000000000000000 x9 : ffff80000a4483c4
x8 : 0000000000000005 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000020 x4 : 0000000000000000 x3 : ffff80000a4482a4
x2 : ffff0000f342e168 x1 : 0000000000000000 x0 : 0000000000000001
Call trace:
gfs2_remove_from_journal+0x3b4/0x880 fs/gfs2/meta_io.c:350
gfs2_discard fs/gfs2/aops.c:622 [inline]
gfs2_invalidate_folio+0x4bc/0x798 fs/gfs2/aops.c:656
folio_invalidate mm/truncate.c:158 [inline]
truncate_cleanup_folio+0x1b4/0x330 mm/truncate.c:178
truncate_inode_pages_range+0x244/0xf10 mm/truncate.c:368
truncate_inode_pages mm/truncate.c:451 [inline]
truncate_inode_pages_final+0x90/0xc0 mm/truncate.c:486
gfs2_evict_inode+0x380/0xf44 fs/gfs2/super.c:1511
evict+0x418/0x894 fs/inode.c:705
iput_final fs/inode.c:1834 [inline]
iput+0x7c0/0x8a4 fs/inode.c:1860
gfs2_put_super+0x33c/0x754 fs/gfs2/super.c:616
generic_shutdown_super+0x130/0x328 fs/super.c:501
kill_block_super+0x70/0xdc fs/super.c:1470
gfs2_kill_sb+0xc0/0xd4 fs/gfs2/ops_fstype.c:-1
deactivate_locked_super+0xac/0x124 fs/super.c:332
deactivate_super+0xf0/0x110 fs/super.c:363
cleanup_mnt+0x394/0x41c fs/namespace.c:1186
__cleanup_mnt+0x20/0x30 fs/namespace.c:1193
task_work_run+0x240/0x2f0 kernel/task_work.c:203
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
do_notify_resume+0x2080/0x2cb8 arch/arm64/kernel/signal.c:1132
prepare_exit_to_user_mode arch/arm64/kernel/entry-common.c:137 [inline]
exit_to_user_mode arch/arm64/kernel/entry-common.c:142 [inline]
el0_svc+0x9c/0x168 arch/arm64/kernel/entry-common.c:638
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: 9782ae48 a94067f6 9100b2d7 d343fee8 (38fc6908)
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
0: 9782ae48 bl 0xfffffffffe0ab920
4: a94067f6 ldp x22, x25, [sp]
8: 9100b2d7 add x23, x22, #0x2c
c: d343fee8 lsr x8, x23, #3
* 10: 38fc6908 ldrsb 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.