Hello,
syzbot found the following issue on:
HEAD commit: c16c81c81336 Linux 5.15.178
git tree: linux-5.15.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=14679bf8580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=3ca28fba9b2e5c5
dashboard link:
https://syzkaller.appspot.com/bug?extid=1c1295145200bdc7a89c
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/3f2947e5e4dc/disk-c16c81c8.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/7034800fdaa8/vmlinux-c16c81c8.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/42337be7c213/Image-c16c81c8.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+1c1295...@syzkaller.appspotmail.com
loop2: detected capacity change from 0 to 32768
ocfs2: Mounting device (7,2) on (node local, slot 0) with ordered data mode.
Unable to handle kernel paging request at virtual address dfff800000000001
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
[dfff800000000001] address between user and kernel address ranges
Internal error: Oops: 0000000096000006 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 4267 Comm: syz.2.30 Not tainted 5.15.178-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : ocfs2_find_dir_space_id fs/ocfs2/dir.c:3408 [inline]
pc : ocfs2_prepare_dir_for_insert+0x2c08/0x5090 fs/ocfs2/dir.c:4288
lr : ocfs2_find_dir_space_id fs/ocfs2/dir.c:3371 [inline]
lr : ocfs2_prepare_dir_for_insert+0x23f8/0x5090 fs/ocfs2/dir.c:4288
sp : ffff8000220067a0
x29: ffff800022007040 x28: 1fffe0001bbe60ef x27: ffff0000ddf30878
x26: ffff700004400d30 x25: ffff800022006980 x24: dfff800000000000
x23: ffff800022006f80 x22: 0000000000000014 x21: 00000001000001c0
x20: 0000000000000009 x19: 0000000000000000 x18: 0000000000000000
x17: 0000000000000002 x16: ffff800009e3ffa0 x15: 0000000000000002
x14: ffff0000cced51c0 x13: 0000000000ff0100 x12: 0000000000080000
x11: 0000000000009036 x10: ffff8000234ca000 x9 : 0000000000009037
x8 : 0000000000000001 x7 : 0000000000000000 x6 : ffff800022006ec0
x5 : ffff8000220072f0 x4 : 0000000000000000 x3 : 0000000000000020
x2 : 0000000000000000 x1 : 0000000000000400 x0 : 0000000000000008
Call trace:
ocfs2_find_dir_space_id fs/ocfs2/dir.c:3408 [inline]
ocfs2_prepare_dir_for_insert+0x2c08/0x5090 fs/ocfs2/dir.c:4288
ocfs2_mknod+0x854/0x24f8 fs/ocfs2/namei.c:294
ocfs2_create+0x184/0x4c8 fs/ocfs2/namei.c:674
lookup_open fs/namei.c:3462 [inline]
open_last_lookups fs/namei.c:3532 [inline]
path_openat+0xf18/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: cb150295 d343fc08 91002674 f9409bfa (38f86908)
---[ end trace 4702748677e9b48c ]---
----------------
Code disassembly (best guess):
0: cb150295 sub x21, x20, x21
4: d343fc08 lsr x8, x0, #3
8: 91002674 add x20, x19, #0x9
c: f9409bfa ldr x26, [sp, #304]
* 10: 38f86908 ldrsb w8, [x8, x24] <-- 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