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 878EBC25B50 for ; Fri, 20 Jan 2023 23:23:51 +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=aVaHnQS+OFZiipWOQ4l/wpFpfKB329JgEmdYZLrI2uE=; b=2ic2QUCYzTHet6 nkTN8fQZBpmtsdnsJJ3rwLO7W4yYjRdng1SSeGVBao2Ts3LZOIB8Tc9DlNDPR4PTb4nW61GJLICHE FBPR2RBn/63aBXzKsaqtXmmpBu4S+aj/RqCd32nJ9wnO09/rAO0+VeD7zRcHDBpn/yMWEYpK1tnub 0pKlxs9cdDejzoIyuZ+o0SDJpGnZLqKSLxHlsIkTRlDnmkvYC2tZQzZPF0ZJPaJAbZopWuEW3ry8X gXoXHSHOEGCvaooSUomba9K1zVSy2cBRCyD6yfeHpDPD0fj7RsVbp9adANc3r5rKG49rD62Jbk7sf sQxsOY2csMxOHLHhKwzQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1pJ0ik-00CjNo-2b; Fri, 20 Jan 2023 23:22:54 +0000 Received: from dfw.source.kernel.org ([2604:1380:4641:c500::1]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1pJ0ig-00CjN0-Kw for linux-arm-kernel@lists.infradead.org; Fri, 20 Jan 2023 23:22:52 +0000 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id D9CA8620DB; Fri, 20 Jan 2023 23:22:46 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id EEBF0C433D2; Fri, 20 Jan 2023 23:22:45 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1674256966; bh=83cPcQUs7BSJFn4vO+wZXpuOZAFI49/x5VAKkojA3S4=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=oYi7F9B7JZZ7V3zQ3g0DG0hXSafUSpEg4Ga/ZUMJYz7f/gJN/g8U34TLKi4kPoXWN 02cffmL9+8d7855C2SjoAHXKVlH8axIORbxzoWhWNkVc9TVBKfbFHquvaUEf1pLLTO ZgeVI9D1eK0PJ/Ft9olEQMk1sKjmS/aVwcmMlvIDShgKCT5AQ3trhhNELg9QX0L0Q0 XtB2Ds6z3qIxdDk7rkrOqL1qheiUVm8uVRWVoSWQkS5ZPiWEkwJXhG2clcWqZe2xm5 TePwrExpmz+knSkoR0X2y1e1WZcQPvFGGKSCt+C7oeqqpiyfnT6x8OonNCw8o/QRhf w9Wl4JJOLPy8Q== Date: Fri, 20 Jan 2023 23:22:43 +0000 From: Jarkko Sakkinen To: Ard Biesheuvel Cc: linux-arm-kernel@lists.infradead.org, linux-efi@vger.kernel.org, will@kernel.org, catalin.marinas@arm.com, stable@vger.kernel.org, Peter Jones , Matthew Garrett , Nathan Chancellor Subject: Re: [PATCH] efi: tpm: Avoid READ_ONCE() for accessing the event log Message-ID: References: <20230109095948.2471205-1-ardb@kernel.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20230109095948.2471205-1-ardb@kernel.org> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20230120_152250_762848_66C9C8C8 X-CRM114-Status: GOOD ( 25.00 ) 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 Mon, Jan 09, 2023 at 10:59:48AM +0100, Ard Biesheuvel wrote: > Nathan reports that recent kernels built with LTO will crash when doing > EFI boot using Fedora's GRUB and SHIM. The culprit turns out to be a > misaligned load from the TPM event log, which is annotated with > READ_ONCE(), and under LTO, this gets translated into a LDAR instruction > which does not tolerate misaligned accesses. > > Interestingly, this does not happen when booting the same kernel > straight from the UEFI shell, and so the fact that the event log may > appear misaligned in memory may be caused by a bug in GRUB or SHIM. > > However, using READ_ONCE() to access firmware tables is slightly unusual > in any case, and here, we only need to ensure that 'event' is not > dereferenced again after it gets unmapped, so a compiler barrier should > be sufficient, and works around the reported issue. > > Cc: > Cc: Peter Jones > Cc: Jarkko Sakkinen > Cc: Matthew Garrett > Reported-by: Nathan Chancellor > Link: https://github.com/ClangBuiltLinux/linux/issues/1782 > Signed-off-by: Ard Biesheuvel > --- > include/linux/tpm_eventlog.h | 6 ++++-- > 1 file changed, 4 insertions(+), 2 deletions(-) > > diff --git a/include/linux/tpm_eventlog.h b/include/linux/tpm_eventlog.h > index 20c0ff54b7a0d313..0abcc85904cba874 100644 > --- a/include/linux/tpm_eventlog.h > +++ b/include/linux/tpm_eventlog.h > @@ -198,8 +198,10 @@ static __always_inline int __calc_tpm2_event_size(struct tcg_pcr_event2_head *ev > * The loop below will unmap these fields if the log is larger than > * one page, so save them here for reference: > */ > - count = READ_ONCE(event->count); > - event_type = READ_ONCE(event->event_type); > + count = event->count; > + event_type = event->event_type; > + > + barrier(); > > /* Verify that it's the log header */ > if (event_header->pcr_idx != 0 || > -- > 2.39.0 > Reviewed-by: Jarkko Sakkinen BR, Jarkko _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel