Hello,
syzbot found the following issue on:
HEAD commit: 3a5928702e71 Linux 5.15.167
git tree: linux-5.15.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=16b69b80580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=171882977b524c53
dashboard link:
https://syzkaller.appspot.com/bug?extid=dea26bb7ef49ab312263
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/22ee27cb312d/disk-3a592870.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/90bf6a3e3d20/vmlinux-3a592870.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/096dd2c73ac3/Image-3a592870.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+dea26b...@syzkaller.appspotmail.com
Unable to handle kernel paging request at virtual address dfff800000000104
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
[dfff800000000104] address between user and kernel address ranges
Internal error: Oops: 0000000096000006 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 5500 Comm: syz.0.254 Not tainted 5.15.167-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
pstate: 00400005 (nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : diIAGRead fs/jfs/jfs_imap.c:2665 [inline]
pc : diRead+0x140/0xa40 fs/jfs/jfs_imap.c:316
lr : diRead+0x138/0xa40 fs/jfs/jfs_imap.c:315
sp : ffff800020d17410
x29: ffff800020d17460 x28: dfff800000000000 x27: 1ffff000041a2eca
x26: ffff0000ddb03bd8 x25: ffff7000041a2ea4 x24: 0000000000000820
x23: ffff0000ddb000c8 x22: ffff0000ddb00430 x21: ffff0000ddb03bf0
x20: 0000000000000000 x19: 0000000000000004 x18: ffff800020d17148
x17: 0000000000000000 x16: ffff800011ac2570 x15: 00000000fffffffe
x14: 1ffff0000295806a x13: dfff800000000000 x12: 0000000000000001
x11: 0000000000000001 x10: 0000000000000000 x9 : 0000000000000000
x8 : 0000000000000104 x7 : ffff8000098b40e0 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : ffff8000082e3f1c
x2 : 0000000000000001 x1 : 0000000000000008 x0 : 0000000000000001
Call trace:
diIAGRead fs/jfs/jfs_imap.c:2665 [inline]
diRead+0x140/0xa40 fs/jfs/jfs_imap.c:316
jfs_iget+0x88/0x364 fs/jfs/inode.c:35
jfs_lookup+0x1e8/0x39c fs/jfs/namei.c:1467
lookup_open fs/namei.c:3440 [inline]
open_last_lookups fs/namei.c:3532 [inline]
path_openat+0xd9c/0x26cc fs/namei.c:3739
do_filp_open+0x1a8/0x3b4 fs/namei.c:3769
do_sys_openat2+0x128/0x3e0 fs/open.c:1253
do_sys_open fs/open.c:1269 [inline]
__do_sys_openat fs/open.c:1285 [inline]
__se_sys_openat fs/open.c:1280 [inline]
__arm64_sys_openat+0x1f0/0x240 fs/open.c:1280
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
Code: f85802d4 97a8bf15 91208298 d343ff08 (387c6908)
---[ end trace e4fbc2cff937a170 ]---
----------------
Code disassembly (best guess):
0: f85802d4 ldur x20, [x22, #-128]
4: 97a8bf15 bl 0xfffffffffea2fc58
8: 91208298 add x24, x20, #0x820
c: d343ff08 lsr x8, x24, #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