Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Message-ID: <b3c1f5a0a37419fac51d570cd1c8e521f59cee14.camel@linux.ibm.com>
Subject: Re: ima - wait for tpm load
From:   Mimi Zohar <zohar@linux.ibm.com>
To:     "Jorge Ramirez-Ortiz, Foundries" <jorge@foundries.io>,
        dmitry.kasatkin@gmail.com, jmorris@namei.org, serge@hallyn.com
Cc:     linux-integrity@vger.kernel.org,
        linux-security-module@vger.kernel.org,
        linux-kernel@vger.kernel.org, Jarkko Sakkinen <jarkko@kernel.org>
Date:   Thu, 10 Jun 2021 10:19:58 -0400
In-Reply-To: <20210610071633.GA30216@trex>
References: <20210610071633.GA30216@trex>
Content-Type: text/plain; charset="ISO-8859-15"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Precedence: bulk

[Cc'ing Jarkko]

On Thu, 2021-06-10 at 09:16 +0200, Jorge Ramirez-Ortiz, Foundries
wrote:
> I am enabling IMA on a ZynqMP based platform using an SPI based TPM
> from Infineon.
> 
> The SPI TPM driver is built-in but since the IMA is initalized from a
> late_initcall, IMA never finds the TPM.
> 
> Is there a recomended way to work around this issue?
> 
> fio@uz3cg-dwg:~$ dmesg | grep tpm
> [    3.381181] tpm_tis_spi spi1.1: 2.0 TPM (device-id 0x1B, rev-id 22)
> [    3.423608] tpm tpm0: A TPM error (256) occurred attempting the self test
> [    3.430406] tpm tpm0: starting up the TPM manually
> 
> fio@uz3cg-dwg:~$ dmesg | grep ima
> [    3.525741] ima: No TPM chip found, activating TPM-bypass!
> [    3.531233] ima: Allocated hash algorithm: sha1

Lengthening the TPM timeout, executing the TPM self test have been past
reasons for the TPM not to initialize prior to IMA.

(Missing from this bug report is the kernel version.)

thanks,

Mimi