[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <gqjk6msau5knzo3azmbckastomox3lra4pe6kda4rd7dua53yc@t2zt3mxh5d26>
Date: Mon, 23 Dec 2024 09:19:41 +0800
From: Coiby Xu <coxu@...hat.com>
To: Baoquan He <bhe@...hat.com>
Cc: kexec@...ts.infradead.org, Ondrej Kozina <okozina@...hat.com>,
Milan Broz <gmazyland@...il.com>, Thomas Staudt <tstaudt@...ibm.com>,
Daniel P . Berrangé <berrange@...hat.com>, Kairui Song <ryncsn@...il.com>,
Jan Pazdziora <jpazdziora@...hat.com>, Pingfan Liu <kernelfans@...il.com>,
Dave Young <dyoung@...hat.com>, linux-kernel@...r.kernel.org, x86@...nel.org,
Dave Hansen <dave.hansen@...el.com>, Vitaly Kuznetsov <vkuznets@...hat.com>,
Greg KH <gregkh@...uxfoundation.org>
Subject: Re: [PATCH v6 0/7] Support kdump with LUKS encryption by reusing
LUKS volume keys
On Sat, Dec 14, 2024 at 10:24:26AM +0800, Baoquan He wrote:
>Hi Coiby,
Hi Baoquan,
>
>On 10/29/24 at 01:52pm, 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:
>
>Other than those small concerns, and the lkp reported issue, the overral
>series looks good to me. Thanks for the effort.
Thanks for carefully reviewing the patches and the suggestions to
improve the patch set!
>
>Thanks
>Baoquan
>
--
Best regards,
Coiby
Powered by blists - more mailing lists