From: Coiby Xu <coxu@redhat.com>
To: Stefan Berger <stefanb@linux.ibm.com>
Cc: kexec@lists.infradead.org, devicetree@vger.kernel.org,
linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, nayna@linux.ibm.com,
nasastry@in.ibm.com, mpe@ellerman.id.au
Subject: Re: [PATCH v7 0/6] tpm: Preserve TPM measurement log across kexec (ppc64)
Date: Mon, 15 Aug 2022 14:53:25 +0800 [thread overview]
Message-ID: <20220815065325.h3t3igr6nogf7h23@Rk> (raw)
In-Reply-To: <20220815064813.77g6icbkygrbmapa@Rk>
On Mon, Aug 15, 2022 at 02:48:13PM +0800, Coiby Xu wrote:
>I can confirm this patch set fixes an issue that guest kdump kernel
>crashes on POWER9 host by applying it to 5.19.1 (there is a conflict
>when applying this patch set to latest kernel i.e. 6.0.0-rc1).
FYI, here's the error of applying it to 6.0.0-rc1,
[root@localhost linux]# git am ../v7_tpm_log.mbox
Applying: of: check previous kernel's ima-kexec-buffer against memory bounds
error: patch failed: drivers/of/kexec.c:126
error: drivers/of/kexec.c: patch does not apply
Patch failed at 0001 of: check previous kernel's ima-kexec-buffer against memory bounds
hint: Use 'git am --show-current-patch=diff' to see the failed patch
--
Best regards,
Coiby
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Coiby Xu <coxu@redhat.com>
To: Stefan Berger <stefanb@linux.ibm.com>
Cc: kexec@lists.infradead.org, devicetree@vger.kernel.org,
linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, nayna@linux.ibm.com,
nasastry@in.ibm.com, mpe@ellerman.id.au
Subject: Re: [PATCH v7 0/6] tpm: Preserve TPM measurement log across kexec (ppc64)
Date: Mon, 15 Aug 2022 14:53:25 +0800 [thread overview]
Message-ID: <20220815065325.h3t3igr6nogf7h23@Rk> (raw)
In-Reply-To: <20220815064813.77g6icbkygrbmapa@Rk>
On Mon, Aug 15, 2022 at 02:48:13PM +0800, Coiby Xu wrote:
>I can confirm this patch set fixes an issue that guest kdump kernel
>crashes on POWER9 host by applying it to 5.19.1 (there is a conflict
>when applying this patch set to latest kernel i.e. 6.0.0-rc1).
FYI, here's the error of applying it to 6.0.0-rc1,
[root@localhost linux]# git am ../v7_tpm_log.mbox
Applying: of: check previous kernel's ima-kexec-buffer against memory bounds
error: patch failed: drivers/of/kexec.c:126
error: drivers/of/kexec.c: patch does not apply
Patch failed at 0001 of: check previous kernel's ima-kexec-buffer against memory bounds
hint: Use 'git am --show-current-patch=diff' to see the failed patch
--
Best regards,
Coiby
WARNING: multiple messages have this Message-ID (diff)
From: Coiby Xu <coxu@redhat.com>
To: Stefan Berger <stefanb@linux.ibm.com>
Cc: devicetree@vger.kernel.org, nayna@linux.ibm.com,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
nasastry@in.ibm.com, linux-integrity@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v7 0/6] tpm: Preserve TPM measurement log across kexec (ppc64)
Date: Mon, 15 Aug 2022 14:53:25 +0800 [thread overview]
Message-ID: <20220815065325.h3t3igr6nogf7h23@Rk> (raw)
In-Reply-To: <20220815064813.77g6icbkygrbmapa@Rk>
On Mon, Aug 15, 2022 at 02:48:13PM +0800, Coiby Xu wrote:
>I can confirm this patch set fixes an issue that guest kdump kernel
>crashes on POWER9 host by applying it to 5.19.1 (there is a conflict
>when applying this patch set to latest kernel i.e. 6.0.0-rc1).
FYI, here's the error of applying it to 6.0.0-rc1,
[root@localhost linux]# git am ../v7_tpm_log.mbox
Applying: of: check previous kernel's ima-kexec-buffer against memory bounds
error: patch failed: drivers/of/kexec.c:126
error: drivers/of/kexec.c: patch does not apply
Patch failed at 0001 of: check previous kernel's ima-kexec-buffer against memory bounds
hint: Use 'git am --show-current-patch=diff' to see the failed patch
--
Best regards,
Coiby
next prev parent reply other threads:[~2022-08-15 6:55 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 16:42 [PATCH v7 0/6] tpm: Preserve TPM measurement log across kexec (ppc64) Stefan Berger
2022-08-12 16:42 ` Stefan Berger
2022-08-12 16:42 ` Stefan Berger
2022-08-12 16:43 ` [PATCH v7 1/6] of: check previous kernel's ima-kexec-buffer against memory bounds Stefan Berger
2022-08-12 16:43 ` Stefan Berger
2022-08-12 16:43 ` Stefan Berger
2022-08-12 16:43 ` [PATCH v7 2/6] drivers: of: kexec ima: Support 32-bit platforms Stefan Berger
2022-08-12 16:43 ` Stefan Berger
2022-08-12 16:43 ` Stefan Berger
2022-08-12 16:43 ` [PATCH v7 3/6] x86/kexec: Carry forward IMA measurement log on kexec Stefan Berger
2022-08-12 16:43 ` Stefan Berger
2022-08-12 16:43 ` Stefan Berger
2022-08-12 17:10 ` Borislav Petkov
2022-08-12 17:10 ` Borislav Petkov
2022-08-12 17:10 ` Borislav Petkov
2022-08-12 17:14 ` Stefan Berger
2022-08-12 17:14 ` Stefan Berger
2022-08-12 17:14 ` Stefan Berger
2022-08-12 18:28 ` Borislav Petkov
2022-08-12 18:28 ` Borislav Petkov
2022-08-12 18:28 ` Borislav Petkov
2022-08-12 16:43 ` [PATCH v7 4/6] tpm: of: Make of-tree specific function commonly available Stefan Berger
2022-08-12 16:43 ` Stefan Berger
2022-08-12 16:43 ` Stefan Berger
2022-08-14 19:16 ` Jarkko Sakkinen
2022-08-14 19:16 ` Jarkko Sakkinen
2022-08-14 19:16 ` Jarkko Sakkinen
2022-08-14 19:16 ` Jarkko Sakkinen
2022-08-14 19:16 ` Jarkko Sakkinen
2022-08-14 19:16 ` Jarkko Sakkinen
2022-08-12 16:43 ` [PATCH v7 5/6] of: kexec: Refactor IMA buffer related functions to make them reusable Stefan Berger
2022-08-12 16:43 ` Stefan Berger
2022-08-12 16:43 ` Stefan Berger
2022-08-12 16:43 ` [PATCH v7 6/6] tpm/kexec: Duplicate TPM measurement log in of-tree for kexec Stefan Berger
2022-08-12 16:43 ` Stefan Berger
2022-08-12 16:43 ` Stefan Berger
2022-08-22 17:59 ` Rob Herring
2022-08-22 17:59 ` Rob Herring
2022-08-22 17:59 ` Rob Herring
2022-08-15 6:48 ` [PATCH v7 0/6] tpm: Preserve TPM measurement log across kexec (ppc64) Coiby Xu
2022-08-15 6:48 ` Coiby Xu
2022-08-15 6:48 ` Coiby Xu
2022-08-15 6:53 ` Coiby Xu [this message]
2022-08-15 6:53 ` Coiby Xu
2022-08-15 6:53 ` Coiby Xu
2022-08-15 13:32 ` Stefan Berger
2022-08-15 13:32 ` Stefan Berger
2022-08-15 13: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=20220815065325.h3t3igr6nogf7h23@Rk \
--to=coxu@redhat.com \
--cc=devicetree@vger.kernel.org \
--cc=kexec@lists.infradead.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=nasastry@in.ibm.com \
--cc=nayna@linux.ibm.com \
--cc=stefanb@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.