From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-io1-f78.google.com (mail-io1-f78.google.com [209.85.166.78]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 0B6CC202F88 for ; Thu, 12 Dec 2024 08:48:18 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.166.78 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1733993300; cv=none; b=Q9HzUweD5k1Db/igE3SWRhMtWH7OjJe5MhswjeCD1mbC1QdqOmdcy/jyGkAV9tz70IUj6qB7rfGQHylMlFwrW2p/amdsSPagHAiM1uiG1vCjLOPtmKYepe2Xz4RK6B01UT7k8/SuyAX9OsMkHfItEboIjP9S9pDGkAvJZ9nu0Ns= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1733993300; c=relaxed/simple; bh=Air9fzGVyO8Ot1PpTXrLqKgcov6z/nD6ViHibCZy9hg=; h=MIME-Version:Date:Message-ID:Subject:From:To:Content-Type; b=haFEDUwuhLN69SzNGn7cXuR//f/ltckDKrFffr5hbgZhKbW0CIN5jc5Q1zp1fD79uvG2PZvXPSA3aEr067mtk6M8AogyUi2j18a0fz90fAuwoWp6IzH8Fvk5xRvHvN7ARi05GiMiz3o+BTEa9UChbrNnUlLZK5YTv2NfJDGixqs= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com; arc=none smtp.client-ip=209.85.166.78 Authentication-Results: smtp.subspace.kernel.org; dmarc=fail (p=none dis=none) header.from=syzkaller.appspotmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=M3KW2WVRGUFZ5GODRSRYTGD7.apphosting.bounces.google.com Received: by mail-io1-f78.google.com with SMTP id ca18e2360f4ac-844db15cae6so32353339f.3 for ; Thu, 12 Dec 2024 00:48:18 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1733993298; x=1734598098; h=to:from:subject:message-id:date:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=Ycfgc8QgugyriqRVXVSDYX2PyQfiPiYWZslUUpz5tsQ=; b=ptj5GM6wn08oMdlaOczkcttjAarbGewb4qDd3bfEfXswPEolpBmPEg9m/BN24r3GEV q6xtfsZ9iwu/yU5ox1DcukeCP2JoA9xdHnsuxS65Ip6G1aLPQnJ77X+wqJPxMK2u7ovJ JR/FLf98I+08cEDHnIbvFg/vpuoOrcdaaPRNxIDhtM4Id03NyI1HhVtNS0l4DRwnq7nH 354irKVTDDv6WsPvCeIwcvi4/B/ktH8/PBg5zVdo3viHbAE6hRbdW/iJ37Ky0m32MeDj hUzJ23+ZI0RQFfsoM7V3bVuUl+9tyfrVmgQ2Y/KfPGj8/n7FIeVMg9E7mC4awXPp5Syx WAOA== X-Forwarded-Encrypted: i=1; AJvYcCXEZZmK0LGnHTs8i/SMu3c64UEFFSXFAvQmpoCxAIzXEzfkLLaCHyao/MAhr7KOMbUglVhO9r4=@lists.linux.dev X-Gm-Message-State: AOJu0Yxyh4np8jc06wm0jrML+O3KnDUoSB3faeE42eIwMyXrbudXRBmr iqMhBttYJjBaKryTJ5TDCQR4EVSpzELPIbTm+vusrpJ6iGmv9Im/eKCezhNxiPrc/+PNHqP2Fe3 iIerCBmo0Di3NxuWWJ8Je2/TzVykKrbjI5JDnXhqwvAgh//9++xqSoY8= X-Google-Smtp-Source: AGHT+IEYh/r9P3Q2d590TMg1aUem7Xugr7uvi7+uIQXGql0+VotmkVmcnbxilKgnIKn53sCV1Elnx8Lm494WyNGaIYBb+5zjsXrV Precedence: bulk X-Mailing-List: kvmarm@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Received: by 2002:a05:6e02:1c01:b0:3a7:172f:1299 with SMTP id e9e14a558f8ab-3ac4b434e57mr27238975ab.12.1733993298165; Thu, 12 Dec 2024 00:48:18 -0800 (PST) Date: Thu, 12 Dec 2024 00:48:18 -0800 X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <675aa352.050a0220.1ac542.0018.GAE@google.com> Subject: [syzbot] [kvmarm?] BUG: unable to handle kernel paging request in __hwasan_check_x0_ADDR From: syzbot To: catalin.marinas@arm.com, joey.gouly@arm.com, kvmarm@lists.linux.dev, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, maz@kernel.org, oliver.upton@linux.dev, suzuki.poulose@arm.com, syzkaller-bugs@googlegroups.com, will@kernel.org, yuzenghui@huawei.com Content-Type: text/plain; charset="UTF-8" Hello, syzbot found the following issue on: HEAD commit: 5db899a34f75 Merge remote-tracking branch 'kernel/kvmarm/n.. git tree: git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git fuzzme console output: https://syzkaller.appspot.com/x/log.txt?x=16db78f8580000 kernel config: https://syzkaller.appspot.com/x/.config?x=fde68ab6d6c8c8ab dashboard link: https://syzkaller.appspot.com/bug?extid=67a9ec5b1706e0184581 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 (non-bootable): https://storage.googleapis.com/syzbot-assets/384ffdcca292/non_bootable_disk-5db899a3.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/4938b757ff4a/vmlinux-5db899a3.xz kernel image: https://storage.googleapis.com/syzbot-assets/936938b47987/Image-5db899a3.gz.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+67a9ec5b1706e0184581@syzkaller.appspotmail.com Unable to handle kernel paging request at virtual address efff800000000137 KASAN: probably user-memory-access in range [0x0000000000001370-0x000000000000137f] Mem abort info: ESR = 0x0000000096000005 EC = 0x25: DABT (current EL), IL = 32 bits SET = 0, FnV = 0 EA = 0, S1PTW = 0 FSC = 0x05: level 1 translation fault Data abort info: ISV = 0, ISS = 0x00000005, ISS2 = 0x00000000 CM = 0, WnR = 0, TnD = 0, TagAccess = 0 GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 swapper pgtable: 4k pages, 52-bit VAs, pgdp=0000000044a53000 [efff800000000137] pgd=1000000049992003, p4d=1000000049993003, pud=0000000000000000 Internal error: Oops: 0000000096000005 [#1] PREEMPT SMP Modules linked in: CPU: 0 UID: 0 PID: 6560 Comm: syz.2.929 Not tainted 6.12.0-rc7-syzkaller-g5db899a34f75 #0 Hardware name: linux,dummy-virt (DT) pstate: 80402009 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : __hwasan_check_x0_67043363+0x4/0x30 lr : vgic_get_irq+0x7c/0x3d4 arch/arm64/kvm/vgic/vgic.c:93 sp : ffff80008c597650 x29: ffff80008c597660 x28: 00000000000000e0 x27: 0000000000000004 x26: 0000000000000002 x25: ffff800083a7fe20 x24: 16f0000014accd90 x23: 16f0000014acb9a0 x22: 0000000000000000 x21: a9ff80008c583000 x20: 0000000000000001 x19: efff800000000000 x18: 0000000000000005 x17: 0000000000000000 x16: 0000000000000137 x15: 0000000000000000 x14: 0000000000000002 x13: 0000000000000003 x12: 70f000000a33ba80 x11: 0000000000080000 x10: 0000000000001378 x9 : efff800000000000 x8 : 0000000000000001 x7 : 0000000000000001 x6 : 0000000000000001 x5 : ffff80008c597858 x4 : ffff8000800f2b38 x3 : ffff8000800f7a00 x2 : 0000000000000001 x1 : 0000000000000001 x0 : 0000000000001378 Call trace: __hwasan_check_x0_67043363+0x4/0x30 vgic_mmio_write_invlpi+0xb0/0x174 arch/arm64/kvm/vgic/vgic-mmio-v3.c:546 dispatch_mmio_write+0x2a4/0x308 kvm_iodevice_write include/kvm/iodev.h:54 [inline] __kvm_io_bus_write+0x290/0x340 virt/kvm/kvm_main.c:5852 kvm_io_bus_write+0x100/0x1bc virt/kvm/kvm_main.c:5877 io_mem_abort+0x4b8/0x7a0 arch/arm64/kvm/mmio.c:204 kvm_handle_guest_abort+0xb4c/0x1c64 arch/arm64/kvm/mmu.c:1880 handle_trap_exceptions arch/arm64/kvm/handle_exit.c:351 [inline] handle_exit+0x1a0/0x274 arch/arm64/kvm/handle_exit.c:381 kvm_arch_vcpu_ioctl_run+0xbc0/0x15b0 arch/arm64/kvm/arm.c:1279 kvm_vcpu_ioctl+0x660/0xf78 virt/kvm/kvm_main.c:4475 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:907 [inline] __se_sys_ioctl fs/ioctl.c:893 [inline] __arm64_sys_ioctl+0x108/0x184 fs/ioctl.c:893 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x78/0x1b8 arch/arm64/kernel/syscall.c:49 el0_svc_common+0xe8/0x1b0 arch/arm64/kernel/syscall.c:132 do_el0_svc+0x40/0x50 arch/arm64/kernel/syscall.c:151 el0_svc+0x54/0x14c arch/arm64/kernel/entry-common.c:712 el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:730 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:598 Code: a90efbfd d2800441 143a3ed3 9344dc10 (38706930) ---[ end trace 0000000000000000 ]--- ---------------- Code disassembly (best guess): 0: a90efbfd stp x29, x30, [sp, #232] 4: d2800441 mov x1, #0x22 // #34 8: 143a3ed3 b 0xe8fb54 c: 9344dc10 sbfx x16, x0, #4, #52 * 10: 38706930 ldrb w16, [x9, x16] <-- 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 syzkaller@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