From: Stefan Berger <stefanb@linux.ibm.com>
To: linux-integrity@vger.kernel.org, linux-security-module@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, zohar@linux.ibm.com,
roberto.sassu@huawei.com,
Tushar Sugandhi <tusharsu@linux.microsoft.com>
Subject: Re: [PATCH] ima: Suspend PCR extends and log appends when rebooting
Date: Fri, 11 Oct 2024 11:40:30 -0400 [thread overview]
Message-ID: <50e5cfff-94f8-4a45-a32d-9cce4f48d5b4@linux.ibm.com> (raw)
In-Reply-To: <20241011150522.2697216-1-stefanb@linux.ibm.com>
On 10/11/24 11:05 AM, Stefan Berger wrote:
> To avoid the following types of error messages from the TPM driver, suspend
> PCR extends once the reboot notifier has been called. This avoids trying to
> use the TPM after the TPM subsystem has been shut down.
>
> [111707.685315][ T1] ima: Error Communicating to TPM chip, result: -19
> [111707.685960][ T1] ima: Error Communicating to TPM chip, result: -19
>
> This error could be observed on a ppc64 machine running SuSE Linux.
>
> Signed-off-by: Tushar Sugandhi <tusharsu@linux.microsoft.com>
Some of the code is taken from Tushar's series:
https://lore.kernel.org/linux-integrity/20240214153827.1087657-1-tusharsu@linux.microsoft.com/T/#m2d5f23959510ea2ada534febe03beff4a3f97ac7
See patch 6/8.
Tushar's series is still needed for carrying the log across kexec
properly since without it it can still happen that the state of the PCR
10 does not match with the IMA log if a new measurements is taken after
the freezing of the log (currently at 'kexec load') and before the
'kexec exec'.
next prev parent reply other threads:[~2024-10-11 15:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 15:05 [PATCH] ima: Suspend PCR extends and log appends when rebooting Stefan Berger
2024-10-11 15:40 ` Stefan Berger [this message]
2024-11-05 17:29 ` Paul Moore
2024-11-11 19:12 ` Mimi Zohar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50e5cfff-94f8-4a45-a32d-9cce4f48d5b4@linux.ibm.com \
--to=stefanb@linux.ibm.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=roberto.sassu@huawei.com \
--cc=tusharsu@linux.microsoft.com \
--cc=zohar@linux.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox