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 70559C4707B for ; Thu, 18 Jan 2024 12:03:21 +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:MIME-Version:References:In-Reply-To: Message-Id:Date:Subject:Cc:To:From:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=63+jcQzxfhQ5Nud+7FU2Su8LV+YZpoIB3gYbhwU51cU=; b=mW5U91Rqo1tcod IehYE5TiRnZw9yGN69B5+AKvyFZcc0iAtEXkWJPubYa5hcmxY6emAMOruAHxYXCp5/V4m+OK+0ejD tdafbPr0v4kZwOrKqSLylAOPPzYFg0XMvYAL4PM/qwCUYrfNzu5nfeNS8qcD5UtQSeHPT6nwunJHn 5idhRPc5ExU4smMfbcHy2sgUiYwc1TOQKvOkeBU81P35Cf94b69aOrcFlXj2WimkhugbcIckLet/B 2431fKeEnGnfhFMUxl/MhT6FQLF8hQPjgK8eei1HTugEqL/hcpZ8ylFIUTP1rZCm0bjMzcA1+vuAY zT9FBix9kbz1R1I5Waiw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1rQR6d-002gLA-0j; Thu, 18 Jan 2024 12:02:47 +0000 Received: from dfw.source.kernel.org ([139.178.84.217]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1rQR6V-002gI6-2v for linux-arm-kernel@lists.infradead.org; Thu, 18 Jan 2024 12:02:42 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by dfw.source.kernel.org (Postfix) with ESMTP id 4F88660DF9; Thu, 18 Jan 2024 12:02:39 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 7941AC433F1; Thu, 18 Jan 2024 12:02:37 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1705579359; bh=pzYBPEZr8EZ5ZI3pR8S8xbO8dnYY2ubYVtztB9ugQtQ=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=WsTvMYY+b/yJcCjMGHcIelyBji22CmuNo0vgsLCZ7RVjKGKTf9Th9hlJUvdjf7uYK GLx22fJEQd6J4TKG5kOfOeQaGqKQ5yfAjx9vgOeBe/o2uEE5/vyMJQFy1lh8Fjn4iW YyW897KzJKaU9xzPkoOJETMuITjXuvfNJwxXsuERr20AwP7cU2seJzqICWOQG1elNm ViBbGZO1Zu5oAMo7/oB/4rXERKmMi+vhtzomARkDJM88ZFy46B8m10ClIaKA20mmVR RJkdJ5fQ3xkvDlI+08IQfrT5fujXgO5NYwCTE6UwzZUrKtkVMw+K+OGu7XifVuqgbS JDRwpBb+LD7iw== From: Will Deacon To: linux-arm-kernel@lists.infradead.org, Mark Rutland Cc: catalin.marinas@arm.com, kernel-team@android.com, Will Deacon , stable@vger.kernel.org, robh@kernel.org, james.morse@arm.com Subject: Re: [PATCH 0/2] arm64: fix+cleanup for ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD Date: Thu, 18 Jan 2024 12:02:26 +0000 Message-Id: <170557561037.3200718.6656632532505785315.b4-ty@kernel.org> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20240116110221.420467-1-mark.rutland@arm.com> References: <20240116110221.420467-1-mark.rutland@arm.com> MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240118_040239_988687_CBC6E959 X-CRM114-Status: GOOD ( 11.03 ) 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 On Tue, 16 Jan 2024 11:02:19 +0000, Mark Rutland wrote: > While testing an unrelated patch on the arm64 for-next/core branch, I > spotted an issue in the ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD > workaround. The first patch fixes that issue, and the second patch > cleans up the remaining logic. > > The issue has existed since the workaround was introduced in commit: > > [...] Cheers, I picked these up, but you might need to shepherd them through -stable, so please keep an eye out for any "failed to apply" mails. Talking of which, the original workaround didn't make it to any kernels before 6.1: [5.15] https://lore.kernel.org/r/2023100743-evasion-figment-fbcc@gregkh [5.10] https://lore.kernel.org/r/2023100745-statute-component-dd0f@gregkh Please can you or Rob have a crack at that? [1/2] arm64: entry: fix ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD https://git.kernel.org/arm64/c/832dd634bd1b [2/2] arm64: entry: simplify kernel_exit logic https://git.kernel.org/arm64/c/da59f1d051d5 Cheers, -- Will https://fixes.arm64.dev https://next.arm64.dev https://will.arm64.dev _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel