[v5.15] BUG: unable to handle kernel paging request in do_xmote

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3c17fc483905 Linux 5.15.171
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1721935f980000
kernel config: https://syzkaller.appspot.com/x/.config?x=4ef7808b17b26971
dashboard link: https://syzkaller.appspot.com/bug?extid=9a789d2aba8a28f2b5f9
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/46bed2db0d85/disk-3c17fc48.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7eb50004f2dc/vmlinux-3c17fc48.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c709f33dca6e/Image-3c17fc48.gz.xz

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

Unable to handle kernel paging request at virtual address dfff800000000097
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
[dfff800000000097] address between user and kernel address ranges
Internal error: Oops: 0000000096000006 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 149 Comm: kworker/1:1H Not tainted 5.15.171-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
Workqueue: glock_workqueue glock_work_func
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : is_system_glock fs/gfs2/glock.c:693 [inline]
pc : do_xmote+0xba0/0x1054 fs/gfs2/glock.c:801
lr : do_xmote+0xb6c/0x1054 fs/gfs2/glock.c:798
sp : ffff80001d737a20
x29: ffff80001d737a60 x28: dfff800000000000 x27: ffff0000d31ac000
x26: ffff0000e58d85a8 x25: dfff800000000000 x24: 00000000000004b8
x23: ffff0000e58d85b0 x22: ffff0000e58d8568 x21: 0000000000000000
x20: dfff800000000000 x19: ffff0000e58d8548 x18: ffff80001d7376a0
x17: 0000000000000000 x16: ffff80000824ebd0 x15: 0000000000000003
x14: 1ffff0000295a06a x13: dfff800000000000 x12: 0000000000000001
x11: 0000000000000000 x10: 0000000000000000 x9 : ffff0000c55751c0
x8 : 0000000000000097 x7 : ffff80000a9630bc x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : ffff80000830598c
x2 : 0000000000000001 x1 : 0000000000004000 x0 : 0000000000000000
Call trace:
is_system_glock fs/gfs2/glock.c:693 [inline]
do_xmote+0xba0/0x1054 fs/gfs2/glock.c:801
run_queue+0x3f8/0x6bc fs/gfs2/glock.c:872
glock_work_func+0x27c/0x470 fs/gfs2/glock.c:1039
process_one_work+0x790/0x11b8 kernel/workqueue.c:2310
worker_thread+0x910/0x1034 kernel/workqueue.c:2457
kthread+0x37c/0x45c kernel/kthread.c:334
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:870
Code: d2d00014 f2fbfff4 9112e118 d343ff08 (38796908)
---[ end trace 719d79a9d5e4dcb9 ]---
----------------
Code disassembly (best guess):
0: d2d00014 mov x20, #0x800000000000 // #140737488355328
4: f2fbfff4 movk x20, #0xdfff, lsl #48
8: 9112e118 add x24, x8, #0x4b8
c: d343ff08 lsr x8, x24, #3
* 10: 38796908 ldrb w8, [x8, x25] <-- 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]

syzbot has found a reproducer for the following issue on:

HEAD commit: 3c17fc483905 Linux 5.15.171
git tree: linux-5.15.y

console output: https://syzkaller.appspot.com/x/log.txt?x=10c37e30580000

kernel config: https://syzkaller.appspot.com/x/.config?x=4ef7808b17b26971
dashboard link: https://syzkaller.appspot.com/bug?extid=9a789d2aba8a28f2b5f9
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13cf38c0580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12b4d35f980000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/46bed2db0d85/disk-3c17fc48.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7eb50004f2dc/vmlinux-3c17fc48.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c709f33dca6e/Image-3c17fc48.gz.xz

mounted in repro: https://storage.googleapis.com/syzbot-assets/c2ff572c9ad9/mount_0.gz

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

Unable to handle kernel paging request at virtual address dfff800000000097
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
[dfff800000000097] address between user and kernel address ranges
Internal error: Oops: 0000000096000006 [#1] PREEMPT SMP
Modules linked in:

CPU: 0 PID: 226 Comm: kworker/0:1H Not tainted 5.15.171-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
Workqueue: glock_workqueue glock_work_func
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : is_system_glock fs/gfs2/glock.c:693 [inline]
pc : do_xmote+0xba0/0x1054 fs/gfs2/glock.c:801
lr : do_xmote+0xb6c/0x1054 fs/gfs2/glock.c:798

sp : ffff80001dea7a20
x29: ffff80001dea7a60 x28: dfff800000000000 x27: ffff0000cc684000
x26: ffff0000d72285a8 x25: dfff800000000000 x24: 00000000000004b8
x23: ffff0000d72285b0 x22: ffff0000d7228568 x21: 0000000000000000
x20: dfff800000000000 x19: ffff0000d7228548 x18: ffff80001dea76a0
x17: 0000000000000000 x16: ffff80000824ebd0 x15: 000000000000bd12

x14: 1ffff0000295a06a x13: dfff800000000000 x12: 0000000000000001

x11: 0000000000000000 x10: 0000000000000000 x9 : ffff0000c67451c0

x8 : 0000000000000097 x7 : ffff80000a9630bc x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : ffff80000830598c
x2 : 0000000000000001 x1 : 0000000000004000 x0 : 0000000000000000
Call trace:
is_system_glock fs/gfs2/glock.c:693 [inline]
do_xmote+0xba0/0x1054 fs/gfs2/glock.c:801
run_queue+0x3f8/0x6bc fs/gfs2/glock.c:872
glock_work_func+0x27c/0x470 fs/gfs2/glock.c:1039
process_one_work+0x790/0x11b8 kernel/workqueue.c:2310
worker_thread+0x910/0x1034 kernel/workqueue.c:2457
kthread+0x37c/0x45c kernel/kthread.c:334
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:870
Code: d2d00014 f2fbfff4 9112e118 d343ff08 (38796908)

---[ end trace 3ebfca443ce8270d ]---

----------------
Code disassembly (best guess):
0: d2d00014 mov x20, #0x800000000000 // #140737488355328
4: f2fbfff4 movk x20, #0xdfff, lsl #48
8: 9112e118 add x24, x8, #0x4b8
c: d343ff08 lsr x8, x24, #3
* 10: 38796908 ldrb w8, [x8, x25] <-- trapping instruction


---

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.