From: Stefan Berger <stefanb@linux.ibm.com>
To: Jarkko Sakkinen <jarkko@kernel.org>,
Michael Ellerman <mpe@ellerman.id.au>,
linux-integrity@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Cc: linux-kernel@vger.kernel.org, rnsastry@linux.ibm.com,
peterhuewe@gmx.de, viparash@in.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 15:08:47 -0400 [thread overview]
Message-ID: <e1b818ae-c932-4d25-98a5-26b258b63365@linux.ibm.com> (raw)
In-Reply-To: <CZRW3GY5O5C0.R5HY5SOFCFJA@kernel.org>
On 3/12/24 11:50, Jarkko Sakkinen wrote:
> On Tue Mar 12, 2024 at 12:35 PM EET, Michael Ellerman wrote:
>> 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
>
> Thanks, I've missed depends-on tag.
>
> Stefan, please add also "Cc: stable@vger.kernel.org" just to make sure
> that I don't forget to add it.
Yeah, once we know whether this is the way forward or not... I posted v2
as RFC to figure this out.
v2's 2/3 patch will only apply to 6.8. To avoid any inconsistencies
between code and bindings we cannot even go further back with this
series (IFF it's the way forward at all). So I am inclined to remove the
Fixes tags. I also find little under Documentation about the Depends-on
tag and what it's supposed to be formatted like -- a commit hash of 1/3
appearing in 2/3 for example? The commit hash is not stable at this
point so I couldn't created it.
> Right, and since these are so small scoped commits, and bug fixes in
> particular, it is also possible to do PR during the release cycle.
>
> BR, Jarkko
next prev parent reply other threads:[~2024-03-12 19:09 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
2024-03-12 15:50 ` Jarkko Sakkinen
2024-03-12 19:08 ` Stefan Berger [this message]
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=e1b818ae-c932-4d25-98a5-26b258b63365@linux.ibm.com \
--to=stefanb@linux.ibm.com \
--cc=jarkko@kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=peterhuewe@gmx.de \
--cc=rnsastry@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).