From: Baoquan He <bhe@redhat.com>
To: Coiby Xu <coxu@redhat.com>
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>,
"Jan Pazdziora" <jpazdziora@redhat.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>,
"Greg KH" <gregkh@linuxfoundation.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
"Borislav Petkov" <bp@alien8.de>,
"Dave Hansen" <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH v6 6/7] x86/crash: pass dm crypt keys to kdump kernel
Date: Thu, 26 Dec 2024 11:48:04 +0800 [thread overview]
Message-ID: <Z2zR9ND4u9j5QMBU@MiWiFi-R3L-srv> (raw)
In-Reply-To: <pe6aibukdppy2p762d2qakuvxafg3ra4n7geind7w6kohaf4t6@kuzkekrbyhcn>
On 12/23/24 at 09:16am, Coiby Xu wrote:
> On Wed, Dec 11, 2024 at 08:55:52PM +0800, Baoquan He wrote:
> > On 10/29/24 at 01:52pm, Coiby Xu wrote:
......
> > > diff --git a/arch/x86/kernel/kexec-bzimage64.c b/arch/x86/kernel/kexec-bzimage64.c
> > > index 68530fad05f7..9c94428927bd 100644
> > > --- a/arch/x86/kernel/kexec-bzimage64.c
> > > +++ b/arch/x86/kernel/kexec-bzimage64.c
> > > @@ -76,6 +76,10 @@ static int setup_cmdline(struct kimage *image, struct boot_params *params,
> > > if (image->type == KEXEC_TYPE_CRASH) {
> > > len = sprintf(cmdline_ptr,
> > > "elfcorehdr=0x%lx ", image->elf_load_addr);
> > > +
> > > + if (image->dm_crypt_keys_addr != 0)
> > > + len += sprintf(cmdline_ptr + len,
> > > + "dmcryptkeys=0x%lx ", image->dm_crypt_keys_addr);
> > > }
> > > memcpy(cmdline_ptr + len, cmdline, cmdline_len);
> > > cmdline_len += len;
> > > @@ -441,6 +445,9 @@ static void *bzImage64_load(struct kimage *image, char *kernel,
> > > ret = crash_load_segments(image);
> > > if (ret)
> > > return ERR_PTR(ret);
> > > + ret = crash_load_dm_crypt_keys(image);
> > > + if (ret)
> > > + pr_debug("Either no dm crypt key or error to retrieve the dm crypt key\n");
> >
> > If it's error, do we need change ti to pr_debug?
>
> Thanks for raising the concern! I think it's OK to let
> crash_load_dm_crypt_keys fail since disk encryption may not be used for
> kdump, thus pr_debug is sufficient. Or have I misunderstood your comment?
If crash_load_dm_crypt_keys() returned error, shouldn't we handle them
separately? If disk encryption is not used, we return a specific value
to indicate that, surely no need to pr_err(). However, if disk
encryption is used for kdump but error is caused and failed
crash_load_dm_crypt_keys(), why don't we error out for the case?
Maybe below change can be made to differentiate them?
diff --git a/kernel/crash_dump_dm_crypt.c b/kernel/crash_dump_dm_crypt.c
index f72a88b7d106..327f84ea57c5 100644
--- a/kernel/crash_dump_dm_crypt.c
+++ b/kernel/crash_dump_dm_crypt.c
@@ -400,7 +400,7 @@ int crash_load_dm_crypt_keys(struct kimage *image)
if (key_count <= 0) {
kexec_dprintk("No dm-crypt keys\n");
- return -EINVAL;
+ return -ENOENT;
}
next prev parent reply other threads:[~2024-12-26 3:48 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 5:52 [PATCH v6 0/7] Support kdump with LUKS encryption by reusing LUKS volume keys Coiby Xu
2024-10-29 5:52 ` Coiby Xu
2024-10-29 5:52 ` [PATCH v6 1/7] kexec_file: allow to place kexec_buf randomly Coiby Xu
2024-10-29 5:52 ` Coiby Xu
2024-11-29 1:38 ` Baoquan He
2024-12-02 10:04 ` Coiby Xu
2024-10-29 5:52 ` [PATCH v6 2/7] crash_dump: make dm crypt keys persist for the kdump kernel Coiby Xu
2024-10-29 5:52 ` Coiby Xu
2024-10-29 5:52 ` [PATCH v6 3/7] crash_dump: store dm crypt keys in kdump reserved memory Coiby Xu
2024-10-29 5:52 ` Coiby Xu
2024-10-29 14:41 ` kernel test robot
2024-10-29 14:41 ` kernel test robot
2024-11-01 7:16 ` Coiby Xu
2024-11-01 7:16 ` Coiby Xu
2024-12-11 12:58 ` Baoquan He
2024-12-23 1:05 ` Coiby Xu
2024-10-29 5:52 ` [PATCH v6 4/7] crash_dump: reuse saved dm crypt keys for CPU/memory hot-plugging Coiby Xu
2024-10-29 5:52 ` Coiby Xu
2024-12-11 13:08 ` Baoquan He
2024-12-23 0:41 ` Coiby Xu
2024-10-29 5:52 ` [PATCH v6 5/7] crash_dump: retrieve dm crypt keys in kdump kernel Coiby Xu
2024-10-29 5:52 ` Coiby Xu
2024-10-29 5:52 ` [PATCH v6 6/7] x86/crash: pass dm crypt keys to " Coiby Xu
2024-10-29 5:52 ` Coiby Xu
2024-12-11 12:55 ` Baoquan He
2024-12-23 1:16 ` Coiby Xu
2024-12-26 3:48 ` Baoquan He [this message]
2025-01-03 2:24 ` Coiby Xu
2024-10-29 5:52 ` [PATCH v6 7/7] x86/crash: make the page that stores the dm crypt keys inaccessible Coiby Xu
2024-10-29 5:52 ` Coiby Xu
2024-11-04 6:17 ` [PATCH v6 0/7] Support kdump with LUKS encryption by reusing LUKS volume keys Baoquan He
2024-11-04 6:17 ` Baoquan He
2024-12-03 17:53 ` David Woodhouse
2024-12-11 1:33 ` Baoquan He
2024-12-14 2:24 ` Baoquan He
2024-12-23 1:19 ` 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=Z2zR9ND4u9j5QMBU@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=berrange@redhat.com \
--cc=bp@alien8.de \
--cc=coxu@redhat.com \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=dyoung@redhat.com \
--cc=gmazyland@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=jpazdziora@redhat.com \
--cc=kernelfans@gmail.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=okozina@redhat.com \
--cc=ryncsn@gmail.com \
--cc=tglx@linutronix.de \
--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 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.