From: Baoquan He <bhe@redhat.com>
To: akpm@linux-foundation.org
Cc: kexec@lists.infradead.org, "Ondrej Kozina" <okozina@redhat.com>,
"Milan Broz" <gmazyland@gmail.com>,
"Thomas Staudt" <tstaudt@de.ibm.com>,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Kairui Song" <ryncsn@gmail.com>,
"Pingfan Liu" <kernelfans@gmail.com>,
"Dave Young" <dyoung@redhat.com>,
linux-kernel@vger.kernel.org, x86@kernel.org,
"Dave Hansen" <dave.hansen@intel.com>,
"Vitaly Kuznetsov" <vkuznets@redhat.com>,
"Coiby Xu" <coxu@redhat.com>,
dwmw2@infradead.org
Subject: Re: [PATCH v8 0/7] Support kdump with LUKS encryption by reusing LUKS volume keys
Date: Mon, 10 Mar 2025 11:30:12 +0800 [thread overview]
Message-ID: <Z85cxCfnRkLve16D@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20250207080818.129165-1-coxu@redhat.com>
Hi Andrew,
On 02/07/25 at 04:08pm, Coiby Xu wrote:
......snip...
Ping again.
This patchset is adding a generic infrastructure for luks support in
crash dumping, and it adds the support in x86 ARCH. Since the x86
related change is only located in kdump only files, won't impact other
x86 codes. Could you consider pick this into your tree?
And by the way, this is a kdump only fix, not related to KHO (Kexec
HandOver) which David suggested to adapt to earlier. Explained it here
to remove misunderstanding.
Thanks
Baoquan
> Documentation/admin-guide/kdump/kdump.rst | 32 ++
> arch/x86/kernel/crash.c | 26 +-
> arch/x86/kernel/kexec-bzimage64.c | 11 +
> arch/x86/kernel/machine_kexec_64.c | 22 ++
> include/linux/crash_core.h | 7 +-
> include/linux/crash_dump.h | 2 +
> include/linux/kexec.h | 34 ++
> kernel/Kconfig.kexec | 10 +
> kernel/Makefile | 1 +
> kernel/crash_dump_dm_crypt.c | 459 ++++++++++++++++++++++
> kernel/kexec_file.c | 3 +
> 11 files changed, 604 insertions(+), 3 deletions(-)
> create mode 100644 kernel/crash_dump_dm_crypt.c
>
>
> base-commit: bb066fe812d6fb3a9d01c073d9f1e2fd5a63403b
> --
> 2.48.1
>
next prev parent reply other threads:[~2025-03-10 3:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 8:08 [PATCH v8 0/7] Support kdump with LUKS encryption by reusing LUKS volume keys Coiby Xu
2025-02-07 8:08 ` [PATCH v8 1/7] kexec_file: allow to place kexec_buf randomly Coiby Xu
2025-02-07 8:08 ` [PATCH v8 2/7] crash_dump: make dm crypt keys persist for the kdump kernel Coiby Xu
2025-04-23 20:44 ` Arnaud Lefebvre
2025-04-29 9:34 ` Coiby Xu
2025-02-07 8:08 ` [PATCH v8 3/7] crash_dump: store dm crypt keys in kdump reserved memory Coiby Xu
2025-02-07 8:08 ` [PATCH v8 4/7] crash_dump: reuse saved dm crypt keys for CPU/memory hot-plugging Coiby Xu
2025-02-07 8:08 ` [PATCH v8 5/7] crash_dump: retrieve dm crypt keys in kdump kernel Coiby Xu
2025-02-07 8:08 ` [PATCH v8 6/7] x86/crash: pass dm crypt keys to " Coiby Xu
2025-04-23 20:59 ` Arnaud Lefebvre
2025-04-29 9:40 ` Coiby Xu
2025-04-30 14:48 ` Arnaud Lefebvre
2025-05-02 0:13 ` Coiby Xu
2025-02-07 8:13 ` [PATCH v8 7/7] x86/crash: make the page that stores the dm crypt keys inaccessible Coiby Xu
2025-02-11 10:25 ` [PATCH v8 0/7] Support kdump with LUKS encryption by reusing LUKS volume keys Baoquan He
2025-02-12 0:43 ` Coiby Xu
2025-02-24 1:36 ` Baoquan He
2025-03-21 6:54 ` Coiby Xu
2025-03-10 3:30 ` Baoquan He [this message]
2025-04-14 5:44 ` Baoquan He
2025-04-24 0:08 ` Arnaud Lefebvre
2025-04-28 9:02 ` Coiby Xu
2025-04-28 18:40 ` Arnaud Lefebvre
2025-04-28 23:56 ` Coiby Xu
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=Z85cxCfnRkLve16D@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=berrange@redhat.com \
--cc=coxu@redhat.com \
--cc=dave.hansen@intel.com \
--cc=dwmw2@infradead.org \
--cc=dyoung@redhat.com \
--cc=gmazyland@gmail.com \
--cc=kernelfans@gmail.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=okozina@redhat.com \
--cc=ryncsn@gmail.com \
--cc=tstaudt@de.ibm.com \
--cc=vkuznets@redhat.com \
--cc=x86@kernel.org \
/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