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

0 views
Skip to first unread message

syzbot

unread,
Apr 19, 2024, 7:45:22 PMApr 19
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 6741e066ec76 Linux 6.1.87
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=14198e10980000
kernel config: https://syzkaller.appspot.com/x/.config?x=5d37120947ebed5a
dashboard link: https://syzkaller.appspot.com/bug?extid=84d8457bab87b374f232
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/e09aa9dab3c8/disk-6741e066.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/4176a4f5a4d5/vmlinux-6741e066.xz
kernel image: https://storage.googleapis.com/syzbot-assets/970367753980/Image-6741e066.gz.xz

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

Unable to handle kernel paging request at virtual address dfff800000000097
KASAN: null-ptr-deref in range [0x00000000000004b8-0x00000000000004bf]
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: 51 Comm: kworker/1:1H Not tainted 6.1.87-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
Workqueue: glock_workqueue glock_work_func
pstate: 80401005 (Nzcv daif +PAN -UAO -TCO -DIT +SSBS BTYPE=--)
pc : is_system_glock fs/gfs2/glock.c:725 [inline]
pc : do_xmote+0xb58/0x11d8 fs/gfs2/glock.c:835
lr : do_xmote+0xb24/0x11d8 fs/gfs2/glock.c:832
sp : ffff80001b387a40
x29: ffff80001b387a60 x28: dfff800000000000 x27: dfff800000000000
x26: ffff0000da5b5ac8 x25: ffff0000da5b5a88 x24: 0000000000000013
x23: 00000000000004b8 x22: 0000000000000000 x21: 0000000000000000
x20: ffff0000d15e4000 x19: ffff0000da5b5a68 x18: 1fffe0003686f176
x17: ffff80001584d000 x16: ffff80000825f5e8 x15: 0000000000000000
x14: 1ffff00002b0a0b0 x13: dfff800000000000 x12: 0000000000000001
x11: 0000000000ff0100 x10: 0000000000000000 x9 : ffff80000a38eafc
x8 : 0000000000000097 x7 : ffff80000aa70568 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : ffff80000831e9d0
x2 : 0000000000000001 x1 : 0000000000004000 x0 : 0000000000000000
Call trace:
is_system_glock fs/gfs2/glock.c:725 [inline]
do_xmote+0xb58/0x11d8 fs/gfs2/glock.c:835
run_queue+0x400/0x688 fs/gfs2/glock.c:914
glock_work_func+0x270/0x440 fs/gfs2/glock.c:1084
process_one_work+0x7ac/0x1404 kernel/workqueue.c:2292
worker_thread+0x8e4/0xfec kernel/workqueue.c:2439
kthread+0x250/0x2d8 kernel/kthread.c:376
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:864
Code: d2d0001b f2fbfffb 9112e117 d343fee8 (387c6908)
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
0: d2d0001b mov x27, #0x800000000000 // #140737488355328
4: f2fbfffb movk x27, #0xdfff, lsl #48
8: 9112e117 add x23, x8, #0x4b8
c: d343fee8 lsr x8, x23, #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

unread,
Apr 19, 2024, 10:53:21 PM (14 days ago) Apr 19
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:

HEAD commit: 6741e066ec76 Linux 6.1.87
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=151fbc27180000
kernel config: https://syzkaller.appspot.com/x/.config?x=5d37120947ebed5a
dashboard link: https://syzkaller.appspot.com/bug?extid=84d8457bab87b374f232
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=10688e73180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10583e07180000
mounted in repro: https://storage.googleapis.com/syzbot-assets/5966edc89f6f/mount_0.gz
x26: ffff0000dd3745a8 x25: ffff0000dd374568 x24: 0000000000000013
x23: 00000000000004b8 x22: 0000000000000000 x21: 0000000000000000
x20: ffff0000d6528000 x19: ffff0000dd374548 x18: ffff80001de06ee0
x17: ffff8000188dd000 x16: ffff80000825f5e8 x15: 0000000000000000
x14: 1ffff00002b0a0b0 x13: dfff800000000000 x12: 0000000000000001
x11: 0000000000ff0100 x10: 0000000000000000 x9 : ffff80000a38eafc
x8 : 0000000000000097 x7 : ffff80000aa70568 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : ffff80000831e9d0
x2 : 0000000000000001 x1 : 0000000000004000 x0 : 0000000000000000
Call trace:
is_system_glock fs/gfs2/glock.c:725 [inline]
do_xmote+0xb58/0x11d8 fs/gfs2/glock.c:835
run_queue+0x400/0x688 fs/gfs2/glock.c:914
glock_work_func+0x270/0x440 fs/gfs2/glock.c:1084
process_one_work+0x7ac/0x1404 kernel/workqueue.c:2292
worker_thread+0x8e4/0xfec kernel/workqueue.c:2439
kthread+0x250/0x2d8 kernel/kthread.c:376
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:864
Code: d2d0001b f2fbfffb 9112e117 d343fee8 (387c6908)
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
0: d2d0001b mov x27, #0x800000000000 // #140737488355328
4: f2fbfffb movk x27, #0xdfff, lsl #48
8: 9112e117 add x23, x8, #0x4b8
c: d343fee8 lsr x8, x23, #3
* 10: 387c6908 ldrb w8, [x8, x28] <-- 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.
Reply all
Reply to author
Forward
0 new messages