From: Michael Ellerman <mpe@ellerman.id.au>
To: Stefan Berger <stefanb@linux.ibm.com>,
Jarkko Sakkinen <jarkko@kernel.org>,
linux-integrity@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Cc: peterhuewe@gmx.de, viparash@in.ibm.com,
linux-kernel@vger.kernel.org, rnsastry@linux.ibm.com
Subject: Re: [PATCH 2/2] tpm: of: If available Use linux,sml-log to get the log and its size
Date: Tue, 12 Mar 2024 21:35:43 +1100 [thread overview]
Message-ID: <877ci74u0w.fsf@mail.lhotse> (raw)
In-Reply-To: <663a3834-056e-4dda-99dd-16ee8734100e@linux.ibm.com>
Stefan Berger <stefanb@linux.ibm.com> writes:
> On 3/7/24 15:00, Jarkko Sakkinen wrote:
>> On Thu Mar 7, 2024 at 9:57 PM EET, Jarkko Sakkinen wrote:
>>> in short summary: s/Use/use/
>>>
>>> On Wed Mar 6, 2024 at 5:55 PM EET, Stefan Berger wrote:
>>>> If linux,sml-log is available use it to get the TPM log rather than the
>>>> pointer found in linux,sml-base. This resolves an issue on PowerVM and KVM
>>>> on Power where after a kexec the memory pointed to by linux,sml-base may
>>>> have been corrupted. Also, linux,sml-log has replaced linux,sml-base and
>>>> linux,sml-size on these two platforms.
>>>>
>>>> Signed-off-by: Stefan Berger <stefanb@linux.ibm.com>
>>>
>>> So shouldn't this have a fixed tag, or not?
>>
>> In English: do we want this to be backported to stable kernel releases or not?
>
> Ideally, yes. v3 will have 3 patches and all 3 of them will have to be
> backported *together* and not applied otherwise if any one of them
> fails. Can this be 'guaranteed'?
You can use Depends-on: <previous commit SHA> to indicate the relationship.
cheers
next prev parent reply other threads:[~2024-03-12 10:36 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 15:55 [PATCH 0/2] Preserve TPM log across kexec Stefan Berger
2024-03-06 15:55 ` [PATCH 1/2] powerpc/prom_init: Replace linux,sml-base/sml-size with linux,sml-log Stefan Berger
2024-03-07 10:41 ` Michael Ellerman
2024-03-07 15:11 ` Stefan Berger
2024-03-07 20:39 ` Conor Dooley
2024-03-07 21:15 ` Stefan Berger
2024-03-07 21:29 ` Conor Dooley
2024-03-07 21:52 ` Rob Herring
2024-03-08 12:23 ` Stefan Berger
2024-03-08 20:57 ` Rob Herring
2024-03-08 21:26 ` Stefan Berger
2024-03-12 10:32 ` Michael Ellerman
2024-03-12 16:22 ` Rob Herring
2024-03-12 19:15 ` Stefan Berger
2024-03-07 20:11 ` Jarkko Sakkinen
2024-03-06 15:55 ` [PATCH 2/2] tpm: of: If available Use linux,sml-log to get the log and its size Stefan Berger
2024-03-07 10:42 ` Michael Ellerman
2024-03-07 15:00 ` Stefan Berger
2024-03-07 11:35 ` Conor Dooley
2024-03-07 19:57 ` Jarkko Sakkinen
2024-03-07 20:00 ` Jarkko Sakkinen
2024-03-08 12:17 ` Stefan Berger
2024-03-11 20:09 ` Jarkko Sakkinen
2024-03-12 10:35 ` Michael Ellerman [this message]
2024-03-12 15:50 ` Jarkko Sakkinen
2024-03-12 19:08 ` Stefan Berger
2024-03-06 16:08 ` [PATCH 0/2] Preserve TPM log across kexec Stefan Berger
2024-03-07 21:42 ` Rob Herring
2024-03-07 22:32 ` Stefan Berger
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=877ci74u0w.fsf@mail.lhotse \
--to=mpe@ellerman.id.au \
--cc=jarkko@kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=peterhuewe@gmx.de \
--cc=rnsastry@linux.ibm.com \
--cc=stefanb@linux.ibm.com \
--cc=viparash@in.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;
as well as URLs for NNTP newsgroup(s).