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 X-Spam-Level: X-Spam-Status: No, score=-6.7 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6456BC4320A for ; Thu, 26 Aug 2021 16:03:16 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 471456108F for ; Thu, 26 Aug 2021 16:03:16 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242987AbhHZQEC (ORCPT ); Thu, 26 Aug 2021 12:04:02 -0400 Received: from mail.kernel.org ([198.145.29.99]:41944 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S242968AbhHZQEB (ORCPT ); Thu, 26 Aug 2021 12:04:01 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 4CC5460ED3; Thu, 26 Aug 2021 16:03:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1629993793; bh=46VQnXe0S/Xq9TFQRoWCZJdbzW1Ri9/3zb6hlDzYOU8=; h=Subject:From:To:Cc:Date:In-Reply-To:References:From; b=aQ6bQelntSG4ZWXlBZ9qoa2W2JJ15WJQrWl2+VRXeqTMZaOtpL1/fjvg2uX50Ukws 8ASa/vNGkXTKHKiDK5qIizUDXJi6mjGNrei/3qA36L87XQJoNEOr46Utgjhs49ybGD XBhVLwic78YXVx/BIYGf8yTwo6prt+/CNMkHkHqnPyRZG+UPc7JFUUG8AccUO+W74S BzRWw+PydHcp4NXZHZBxapVVeUDMTSOuSEU/13cKxHuV9YByWETYz47xZoCufQIVK2 iSxGFyhYIy2fSL26NS8kxBPATZVN1qospDvawhC97IXLgpIkXrw1pSRGnO6PvAyzqo TQ64838UUc3lA== Message-ID: Subject: Re: [PATCH v13 5/7] tpm: tpm_tis: verify TPM_STS register is valid after locality request From: Jarkko Sakkinen To: amirmizi6@gmail.com, Eyal.Cohen@nuvoton.com, jarkko.sakkinen@linux.intel.com, oshrialkoby85@gmail.com, alexander.steffen@infineon.com, robh+dt@kernel.org, mark.rutland@arm.com, peterhuewe@gmx.de, jgg@ziepe.ca, arnd@arndb.de, gregkh@linuxfoundation.org, benoit.houyere@st.com, eajames@linux.ibm.com, joel@jms.id.au Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-integrity@vger.kernel.org, oshri.alkoby@nuvoton.com, tmaimon77@gmail.com, gcwilson@us.ibm.com, kgoldman@us.ibm.com, Dan.Morav@nuvoton.com, oren.tanami@nuvoton.com, shmulik.hager@nuvoton.com, amir.mizinski@nuvoton.com Date: Thu, 26 Aug 2021 19:03:11 +0300 In-Reply-To: <20210826111908.117278-6-amirmizi6@gmail.com> References: <20210826111908.117278-1-amirmizi6@gmail.com> <20210826111908.117278-6-amirmizi6@gmail.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.36.5-0ubuntu1 MIME-Version: 1.0 Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On Thu, 2021-08-26 at 14:19 +0300, amirmizi6@gmail.com wrote: > From: Amir Mizinski >=20 > Issue could result when the TPM does not update TPM_STS register after > a locality request (TPM_STS Initial value =3D 0xFF) and a TPM_STS registe= r > read occurs (tpm_tis_status(chip)). What does it mean when "issue results"? I don't understand that part. /Jarkko