Hello,
syzbot found the following issue on:
HEAD commit: b67dc5c9ade9 Linux 6.1.118
git tree: linux-6.1.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=177e0ae8580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=574f3f177f1573fa
dashboard link:
https://syzkaller.appspot.com/bug?extid=a365dd71b3f515463c81
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/7bb54d7e4cde/disk-b67dc5c9.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/884b8b3180c7/vmlinux-b67dc5c9.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/476257459caa/Image-b67dc5c9.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+a365dd...@syzkaller.appspotmail.com
loop2: detected capacity change from 0 to 32768
JBD2: Ignoring recovery information on journal
ocfs2: Mounting device (7,2) on (node local, slot 0) with ordered data mode.
Unable to handle kernel paging request at virtual address dfff800000000001
KASAN: null-ptr-deref in range [0x0000000000000008-0x000000000000000f]
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: 0 PID: 6410 Comm: syz.2.480 Not tainted 6.1.118-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/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+0x2d10/0x5204 fs/ocfs2/dir.c:4288
lr : ocfs2_find_dir_space_id fs/ocfs2/dir.c:3371 [inline]
lr : ocfs2_prepare_dir_for_insert+0x24e0/0x5204 fs/ocfs2/dir.c:4288
sp : ffff8000218865a0
x29: ffff800021886e40 x28: ffff800021886ea0 x27: ffff0000e1216c38
x26: ffff700004310cf0 x25: 1ffff00004310db0 x24: dfff800000000000
x23: ffff800021886d80 x22: 000000000000001c x21: 00000001000001c0
x20: 0000000000000009 x19: 0000000000000000 x18: ffff800021886580
x17: ffff800018aab000 x16: ffff8000121e3a40 x15: 0000000000000002
x14: 0000000000000002 x13: ffff0000cf8f8000 x12: 0000000000040000
x11: 0000000000008ac6 x10: ffff800023438000 x9 : ffff800009e90d08
x8 : 0000000000000001 x7 : 0000000000000000 x6 : ffff800021886da0
x5 : ffff8000218874a0 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+0x2d10/0x5204 fs/ocfs2/dir.c:4288
__ocfs2_prepare_orphan_dir+0x14c/0x300 fs/ocfs2/namei.c:2162
ocfs2_prepare_orphan_dir+0x178/0x460 fs/ocfs2/namei.c:2205
ocfs2_rename+0x20ec/0x3588 fs/ocfs2/namei.c:1457
vfs_rename+0xac8/0xe04 fs/namei.c:4874
do_renameat2+0x9ec/0xe64 fs/namei.c:5027
__do_sys_renameat2 fs/namei.c:5060 [inline]
__se_sys_renameat2 fs/namei.c:5057 [inline]
__arm64_sys_renameat2+0xe0/0xfc fs/namei.c:5057
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
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: cb150295 d343fc08 91002674 f9409bfa (38f86908)
---[ end trace 0000000000000000 ]---
----------------
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