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 A8F27C5479D for ; Mon, 9 Jan 2023 17:55:02 +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=hoYQp0YMQznaUw0ZTXHJHUOqHTCHmD3oaBSH4CPlbGU=; b=ti8hknIuA+FNAl AcyfFD9fFzpOI/M3Gz6DvOaosyJ+HtMHO3cd5CLA5K9l02F7SWyn5LdGvhXxJbYYq35bKCPfh7jkE KwSeXczD7iQB+EEuJ9tUkxQSmIQDkCPswbAH/OekfP3iLeL55vtry52Y2LGX52ocYPSZdwrZKVLTW hxXaRl2I8tAa9AGYkWgvP01yBbqaRN8uwadMI0gX9uwf7UNabPTgw1S5GDpfDX8AHNH3q8KjHXuUV 1Wf9voAy7PGvuaUCMaKyolqgHZ5oJqe/pyyDG+NMkjU74FDMVBV3be/QWqHiFRSgonzRnn0jEAtbd xrraZzBePX9ogD1CbbhA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1pEwL2-0032iw-DC; Mon, 09 Jan 2023 17:53:37 +0000 Received: from sin.source.kernel.org ([145.40.73.55]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1pEwGW-0030Vq-FM for linux-arm-kernel@lists.infradead.org; Mon, 09 Jan 2023 17:48:58 +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 sin.source.kernel.org (Postfix) with ESMTPS id 78C69CE1133; Mon, 9 Jan 2023 17:48:51 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 2B1B7C433D2; Mon, 9 Jan 2023 17:48:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1673286529; bh=D8cQ+OGv0sXy1dauhM+2T07eNZflfR99gYeS8JBaXLE=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=lX+5Zs8Ym6sOug7E6fmehWpQp2RZClTaoVO4WZsX0ldH1AhYEC+e0zFWr9Iig9d9D q+Z+xDe+QkMcHy3OxOTL/pMvLLsdlPqL+84omXePaMcp3xBKj2fcWg1o3+MfJd5t1c kchPFA+jZHuMLU3o/Kyh7h1KtwiL665cBe83VavePmZ9HFdMgF1eI7DfNlgHQxaH6v EeoS6orRQChY9+X6BdVcjg9ewErF+HNTqjZAgPR1G6jkWHFRcx60+hnUpi6e9QjWWT jUTsyuanc7nFHpI8xKspNYYZy1rwmRE6JnS3lVb+ExFubzErkT5h9lpbKoRQul05ye KRkquLRB1M//Q== Date: Mon, 9 Jan 2023 10:48:47 -0700 From: Nathan Chancellor 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 , Jarkko Sakkinen , Matthew Garrett 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-20230109_094856_735077_4B1DC286 X-CRM114-Status: GOOD ( 27.24 ) 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 Based on the thread, I tested this patch without barrier() and my machine boots up just fine now with an LTO kernel. Thanks a lot for the analysis and fix! Tested-by: Nathan Chancellor > --- > 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 > _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel