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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 571F0C07545 for ; Wed, 25 Oct 2023 18:04:45 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=pTyZMGi3wNldzD7HD7IdcIN9Q/j93Tmp3gyy7jondNE=; b=mlDgsO8tBZgtfW 3polnNuEemTBotR1Bqr3LQzUl3BQm64AHsLC5DxSina/XpCNpdWLJPjJuOngK/rJreb8M/WuxurFc 5/VS+muaPpC8D3ecISm+F1gx+7FPQXTnnXlRannE5rB3Agy8CuIocvf8dmArO4/e0oYVVm3UlTKDy QfORU0PFpfUagMiTddaPuQm3gOUlvNd2hE7bUKrkb3xDmGQiwbKxIZ58ocF+geKFsWmofQBSSyXLq l7slj93yr2pspta/TDNLqumC3bzHFPSeBvS4dBXIluFy+esCjgOnNUTo4PWMOB8fsx+CqT0rbuJGn 3WMmWbe54DdTI83o4Dyg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1qviEl-00CpQ2-1G; Wed, 25 Oct 2023 18:04:11 +0000 Received: from foss.arm.com ([217.140.110.172]) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1qviEh-00CpOn-1O for linux-arm-kernel@lists.infradead.org; Wed, 25 Oct 2023 18:04:09 +0000 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 767E02F4; Wed, 25 Oct 2023 11:04:43 -0700 (PDT) Received: from FVFF77S0Q05N.cambridge.arm.com (FVFF77S0Q05N.cambridge.arm.com [10.1.32.180]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id A712A3F738; Wed, 25 Oct 2023 11:04:00 -0700 (PDT) Date: Wed, 25 Oct 2023 19:01:53 +0100 From: Mark Rutland To: Nathan Chancellor Cc: catalin.marinas@arm.com, will@kernel.org, ndesaulniers@google.com, trix@redhat.com, linux-arm-kernel@lists.infradead.org, llvm@lists.linux.dev, patches@lists.linux.dev Subject: Re: [PATCH] arm64: Restrict CPU_BIG_ENDIAN to GNU as or LLVM IAS 15.x or newer Message-ID: References: <20231025-disable-arm64-be-ias-b4-llvm-15-v1-1-b25263ed8b23@kernel.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20231025-disable-arm64-be-ias-b4-llvm-15-v1-1-b25263ed8b23@kernel.org> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20231025_110407_559497_0A1EA5A1 X-CRM114-Status: GOOD ( 25.73 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org Hi Nathan, On Wed, Oct 25, 2023 at 10:21:28AM -0700, Nathan Chancellor wrote: > A recent refactoring in the arm64 tree exposed an assembler bug in LLVM > with regards to the generation of NOPs for arm64 big endian, resulting > in near-immediate crashes on boot in QEMU. Could we please put a bit more detail into the commit message about what exactly went wrong and how this was detected? I know that can be found from the github links below, but having to go chase that is a bit of a pain. Would you be happy with the below? I've also added a Cc stable, since this is a potential state corruption issue. Assuming you're happy with that text: Acked-by: Mark Rutland Mark. ---->8---- Prior to LLVM 15.0.0, LLVM's integrated assemble would incorrectly byte-swap NOP when compiling for big-endian, and the resulting series of bytes happened to match the encoding of FNMADD S21, S30, S0, S0. This went unnoticed until commit: 34f66c4c4d5518c1 ("arm64: Use a positive cpucap for FP/SIMD") Prior to that commit, the kernel would always enable the use of FPSIMD early in boot when __cpu_setup() initialized CPACR_EL1, and so usage of FNMADD within the kernel was not detected, but could result in the corruption of user or kernel FPSIMD state. After that commit, the instructions happen to trap during boot prior to FPSIMD being detected and enabled, e.g. | Unhandled 64-bit el1h sync exception on CPU0, ESR 0x000000001fe00000 -- ASIMD | CPU: 0 PID: 0 Comm: swapper Not tainted 6.6.0-rc3-00013-g34f66c4c4d55 #1 | Hardware name: linux,dummy-virt (DT) | pstate: 400000c9 (nZcv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--) | pc : __pi_strcmp+0x1c/0x150 | lr : populate_properties+0xe4/0x254 | sp : ffffd014173d3ad0 | x29: ffffd014173d3af0 x28: fffffbfffddffcb8 x27: 0000000000000000 | x26: 0000000000000058 x25: fffffbfffddfe054 x24: 0000000000000008 | x23: fffffbfffddfe000 x22: fffffbfffddfe000 x21: fffffbfffddfe044 | x20: ffffd014173d3b70 x19: 0000000000000001 x18: 0000000000000005 | x17: 0000000000000010 x16: 0000000000000000 x15: 00000000413e7000 | x14: 0000000000000000 x13: 0000000000001bcc x12: 0000000000000000 | x11: 00000000d00dfeed x10: ffffd414193f2cd0 x9 : 0000000000000000 | x8 : 0101010101010101 x7 : ffffffffffffffc0 x6 : 0000000000000000 | x5 : 0000000000000000 x4 : 0101010101010101 x3 : 000000000000002a | x2 : 0000000000000001 x1 : ffffd014171f2988 x0 : fffffbfffddffcb8 | Kernel panic - not syncing: Unhandled exception | CPU: 0 PID: 0 Comm: swapper Not tainted 6.6.0-rc3-00013-g34f66c4c4d55 #1 | Hardware name: linux,dummy-virt (DT) | Call trace: | dump_backtrace+0xec/0x108 | show_stack+0x18/0x2c | dump_stack_lvl+0x50/0x68 | dump_stack+0x18/0x24 | panic+0x13c/0x340 | el1t_64_irq_handler+0x0/0x1c | el1_abort+0x0/0x5c | el1h_64_sync+0x64/0x68 | __pi_strcmp+0x1c/0x150 | unflatten_dt_nodes+0x1e8/0x2d8 | __unflatten_device_tree+0x5c/0x15c | unflatten_device_tree+0x38/0x50 | setup_arch+0x164/0x1e0 | start_kernel+0x64/0x38c | __primary_switched+0xbc/0xc4 Restrict CONFIG_CPU_BIG_ENDIAN to a known good assembler, which is either GNU as or LLVM's IAS 15.0.0 and newer, which contains the linked commit. Closes: https://github.com/ClangBuiltLinux/linux/issues/1948 Link: https://github.com/llvm/llvm-project/commit/1379b150991f70a5782e9a143c2ba5308da1161c Signed-off-by: Nathan Chancellor Cc: stable@vger.kernel.org > Restrict CONFIG_CPU_BIG_ENDIAN to a known good assembler, which is > either GNU as or LLVM's IAS 15.0.0 and newer, which contains the linked > commit. > > Closes: https://github.com/ClangBuiltLinux/linux/issues/1948 > Link: https://github.com/llvm/llvm-project/commit/1379b150991f70a5782e9a143c2ba5308da1161c > Signed-off-by: Nathan Chancellor > --- > arch/arm64/Kconfig | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig > index adf2f8a327be..92d33ece4c45 100644 > --- a/arch/arm64/Kconfig > +++ b/arch/arm64/Kconfig > @@ -1360,6 +1360,8 @@ choice > config CPU_BIG_ENDIAN > bool "Build big-endian kernel" > depends on !LD_IS_LLD || LLD_VERSION >= 130000 > + # https://github.com/llvm/llvm-project/commit/1379b150991f70a5782e9a143c2ba5308da1161c > + depends on AS_IS_GNU || AS_VERSION >= 150000 > help > Say Y if you plan on running a kernel with a big-endian userspace. > > > --- > base-commit: 22e877699642285c47f5d7d83b2d59815c29ebe8 > change-id: 20231025-disable-arm64-be-ias-b4-llvm-15-b6f30f3f24be > > Best regards, > -- > Nathan Chancellor > _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel