-----Original Message----- From: Sasha Levin [mailto:sashal@kernel.org] Sent: Wednesday, February 5, 2020 3:45 PM To: Sasha Levin sashal@kernel.org; Roberto Sassu roberto.sassu@huawei.com; zohar@linux.ibm.com; James.Bottomley@HansenPartnership.com Cc: linux-integrity@vger.kernel.org; stable@vger.kernel.org; stable@vger.kernel.org Subject: Re: [PATCH v2 2/8] ima: Switch to ima_hash_algo for boot aggregate

Hi,

[This is an automated email]

This commit has been processed because it contains a -stable tag. The stable tag indicates that it's relevant for the following trees: all

The bot has tested the following trees: v5.5.1, v5.4.17, v4.19.101, v4.14.169, v4.9.212, v4.4.212.

v5.5.1: Build OK! v5.4.17: Build OK! v4.19.101: Failed to apply! Possible dependencies: 100b16a6f290 ("tpm: sort objects in the Makefile") 1ad6640cd614 ("tpm: move tpm1_pcr_extend to tpm1-cmd.c") 70a3199a7101 ("tpm: factor out tpm_get_timeouts()") 879b589210a9 ("tpm: retrieve digest size of unknown algorithms with PCR read")

Hi Sasha

this patch is necessary. However, backporting it won't be that easy as it was part of a patch set. Before this patch, users of the TPM driver could only read the SHA1 PCR bank. The IMA patch needs to read also other PCR banks.

NOTE: The patch will not be queued to stable trees until it is upstream.

How should we proceed with this patch?

This question should be for Jarkko (added in CC), as some patches for the TPM driver must be backported to apply the IMA patch.

Roberto

HUAWEI TECHNOLOGIES Duesseldorf GmbH, HRB 56063 Managing Director: Li Peng, Li Jian, Shi Yanli