All of lore.kernel.org
 help / color / mirror / Atom feed
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>
Subject: Re: [PATCH v7 0/7] Support kdump with LUKS encryption by reusing LUKS volume keys
Date: Fri, 7 Feb 2025 11:01:15 +0800	[thread overview]
Message-ID: <Z6V3e3yPQyhaRBCN@fedora> (raw)
In-Reply-To: <20250116065825.1041558-1-coxu@redhat.com>

Hi Coiby,

On 01/16/25 at 02:58pm, Coiby Xu wrote:
> LUKS is the standard for Linux disk encryption, widely adopted by users,
> and in some cases, such as Confidential VMs, it is a requirement. With 
> kdump enabled, when the first kernel crashes, the system can boot into
> the kdump/crash kernel to dump the memory image (i.e., /proc/vmcore) 
> to a specified target. However, there are two challenges when dumping
> vmcore to a LUKS-encrypted device:

This v7 series looks good to me, other than Randy's concern. Do you plan
to repost to update the document?

Thanks
Baoquan


  parent reply	other threads:[~2025-02-07  3:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-16  6:58 [PATCH v7 0/7] Support kdump with LUKS encryption by reusing LUKS volume keys Coiby Xu
2025-01-16  6:58 ` [PATCH v7 1/7] kexec_file: allow to place kexec_buf randomly Coiby Xu
2025-01-16  6:58 ` [PATCH v7 2/7] crash_dump: make dm crypt keys persist for the kdump kernel Coiby Xu
2025-01-16  7:04   ` Randy Dunlap
2025-01-16  7:32     ` Coiby Xu
2025-01-16  6:58 ` [PATCH v7 3/7] crash_dump: store dm crypt keys in kdump reserved memory Coiby Xu
2025-01-16  6:58 ` [PATCH v7 4/7] crash_dump: reuse saved dm crypt keys for CPU/memory hot-plugging Coiby Xu
2025-01-16  7:28 ` [PATCH v7 5/7] crash_dump: retrieve dm crypt keys in kdump kernel Coiby Xu
2025-01-16  7:30 ` [PATCH v7 6/7] x86/crash: pass dm crypt keys to " Coiby Xu
2025-01-16  7:31 ` [PATCH v7 7/7] x86/crash: make the page that stores the dm crypt keys inaccessible Coiby Xu
2025-02-07  3:01 ` Baoquan He [this message]
2025-02-07  7:57   ` [PATCH v7 0/7] Support kdump with LUKS encryption by reusing LUKS volume keys 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=Z6V3e3yPQyhaRBCN@fedora \
    --to=bhe@redhat.com \
    --cc=berrange@redhat.com \
    --cc=coxu@redhat.com \
    --cc=dave.hansen@intel.com \
    --cc=dyoung@redhat.com \
    --cc=gmazyland@gmail.com \
    --cc=jpazdziora@redhat.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 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.