From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3B3CDC25B47 for ; Fri, 27 Oct 2023 10:57:58 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231493AbjJ0K56 (ORCPT ); Fri, 27 Oct 2023 06:57:58 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48642 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231487AbjJ0K55 (ORCPT ); Fri, 27 Oct 2023 06:57:57 -0400 Received: from mail-vs1-xe32.google.com (mail-vs1-xe32.google.com [IPv6:2607:f8b0:4864:20::e32]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id CB0711B4 for ; Fri, 27 Oct 2023 03:57:54 -0700 (PDT) Received: by mail-vs1-xe32.google.com with SMTP id ada2fe7eead31-457bfdc1cdaso881140137.2 for ; Fri, 27 Oct 2023 03:57:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1698404273; x=1699009073; darn=vger.kernel.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=3zQBT6jRuR5jxYiRAr8syfNhHciQ/BHcE4DZFyhdPwI=; b=PP7jMKs5l7SL5IZXsqTzLeRLyfOLcpy+3xxK0sjSj2gr1UTLLRnankwT5A+w5SwD0J gdsAWOGRAT6DiTXv0BClS3Yl9Wi00+cZACEFYyDhtub68RweVSeuAo7RrHWQj9KY1qH3 85dswXIKUHhDyDKLTdgZi21nZ6z56YsM6/EgkEJb22uL7r1NqfWO0xuwda9WojuJNn6r /eP+ThfBybhRj/5O0jmwnMG98XfKSs9ldeITvRZoqhe/Sov2mGWdQK7BxvNXBi7WJUs6 4zlADIeSrk6+xVCA10IP9WrxJfSMI1FwqIpNzFsyTRUi7FKHDFjncg/gy0vhcq+A7zeM sIXQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1698404273; x=1699009073; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=3zQBT6jRuR5jxYiRAr8syfNhHciQ/BHcE4DZFyhdPwI=; b=ZYylZqiHKaMVWv+IZaGbPsYPxbUfbqhv1NTJvMHEX/7Xry4+m3v/62pNHEIrEZP69K IgQKEW22RhmwHoPObuOnoYihKWqlYs8qmROB1UrXA99rHc1RWtb0CWUkEEI46hTx18oW iLAQkrdF1yYfWEVKiUpVbUGr2I4f5w6bZyaGHzASGyIf9oL31vCGoBIgUT4IQDPelRW/ Kh8e0t+rWhKYvm/2U5y+xIWnu4uwp/k75ye3fdf5ZHWBL6l9U6WzrjtU3xVfyI87iYuN xCguKd5uo2apqJnaqg10gKy7JSyAeQxSjsgTn6RAXDilogagYtoMPVOWoCzIen+YvLzY AAmw== X-Gm-Message-State: AOJu0YzMcmgaVLrKU9mhCir0MapDbi3yaO/ssbfLnyaaLuiebWyq48XY 81Y79xPNMAkxmZSeJV9XUuFwGWcvFAby+fZDP09kF4gNKcDAFumhD58= X-Google-Smtp-Source: AGHT+IHarNLCoFsdKNzL1a48n70a2eNgURLrsseEGHkrmEWYJ6n2/q05I2+4jQ74A/lQL0OqJP835LGQwXLk47ENiWU= X-Received: by 2002:a05:6102:1592:b0:457:dbfc:5c69 with SMTP id g18-20020a056102159200b00457dbfc5c69mr2829666vsv.12.1698404273032; Fri, 27 Oct 2023 03:57:53 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Naresh Kamboju Date: Fri, 27 Oct 2023 16:27:41 +0530 Message-ID: Subject: Re: qemu-arm64: handle_futex_death - kernel/futex/core.c:661 - Unable to handle kernel unknown 43 at virtual address To: Ard Biesheuvel Cc: Mark Rutland , Catalin Marinas , Will Deacon , Oliver Upton , Linux-Next Mailing List , open list , Linux ARM , lkft-triage@lists.linaro.org, Arnd Bergmann , Thomas Gleixner , Ingo Molnar , Anders Roxell , Dan Carpenter , LTP List , Petr Vorel Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-next@vger.kernel.org On Thu, 26 Oct 2023 at 21:09, Ard Biesheuvel wrote: > > On Thu, 26 Oct 2023 at 17:30, Mark Rutland wrote: > > > > On Thu, Oct 26, 2023 at 08:11:26PM +0530, Naresh Kamboju wrote: > > > Following kernel crash noticed on qemu-arm64 while running LTP syscalls > > > set_robust_list test case running Linux next 6.6.0-rc7-next-20231026 and > > > 6.6.0-rc7-next-20231025. > > > > > > BAD: next-20231025 > > > Good: next-20231024 > > > > > > Reported-by: Linux Kernel Functional Testing > > > Reported-by: Naresh Kamboju > > > > > > Log: > > > ---- > > > <1>[ 203.119139] Unable to handle kernel unknown 43 at virtual > > > address 0001ffff9e2e7d78 > > > <1>[ 203.119838] Mem abort info: > > > <1>[ 203.120064] ESR = 0x000000009793002b > > > <1>[ 203.121040] EC = 0x25: DABT (current EL), IL = 32 bits > > > set_robust_list01 1 TPASS : set_robust_list: retval = -1 > > > (expected -1), errno = 22 (expected 22) > > > set_robust_list01 2 TPASS : set_robust_list: retval = 0 > > > (expected 0), errno = 0 (expected 0) > > > <1>[ 203.124496] SET = 0, FnV = 0 > > > <1>[ 203.124778] EA = 0, S1PTW = 0 > > > <1>[ 203.125029] FSC = 0x2b: unknown 43 > > > > It looks like this is fallout from the LPA2 enablement. > > > > According to the latest ARM ARM (ARM DDI 0487J.a), page D19-6475, that "unknown > > 43" (0x2b / 0b101011) is the DFSC for a level -1 translation fault: > > > > 0b101011 When FEAT_LPA2 is implemented: > > Translation fault, level -1. > > > > It's triggered here by an LDTR in a get_user() on a bogus userspace address. > > The exception is expected, and it's supposed to be handled via the exception > > fixups, but the LPA2 patches didn't update the fault_info table entries for all > > the level -1 faults, and so those all get handled by do_bad() and don't call > > fixup_exception(), causing them to be fatal. > > > > It should be relatively simple to update the fault_info table for the level -1 > > faults, but given the other issues we're seeing I think it's probably worth > > dropping the LPA2 patches for the moment. > > > > Thanks for the analysis Mark. > > I agree that this should not be difficult to fix, but given the other > CI problems and identified loose ends, I am not going to object to > dropping this partially or entirely at this point. I'm sure everybody > will be thrilled to go over those 60 patches again after I rebase them > onto v6.7-rc1 :-) I am happy to test any proposed fix patch. - Naresh