[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230602213452.GC628@quark.localdomain>
Date: Fri, 2 Jun 2023 14:34:52 -0700
From: Eric Biggers <ebiggers@...nel.org>
To: Coiby Xu <coxu@...hat.com>
Cc: kexec@...ts.infradead.org, Baoquan He <bhe@...hat.com>,
x86@...nel.org, dm-devel@...hat.com,
Pingfan Liu <kernelfans@...il.com>,
linux-kernel@...r.kernel.org, Dave Hansen <dave.hansen@...el.com>,
Kairui Song <ryncsn@...il.com>,
Jan Pazdziora <jpazdziora@...hat.com>,
Thomas Staudt <tstaudt@...ibm.com>,
Vitaly Kuznetsov <vkuznets@...hat.com>,
Dave Young <dyoung@...hat.com>,
Milan Broz <gmazyland@...il.com>
Subject: Re: [PATCH 0/5] Support kdump with LUKS encryption by reusing LUKS
volume key
On Thu, Jun 01, 2023 at 03:24:39PM +0800, Coiby Xu wrote:
> [PATCH 0/5] Support kdump with LUKS encryption by reusing LUKS volume key
The kernel has no concept of LUKS at all. It provides dm-crypt, which LUKS
happens to use. But LUKS is a userspace concept.
This is a kernel patchset, so why does it make sense for it to be talking about
LUKS at all? Perhaps you mean dm-crypt?
- Eric
Powered by blists - more mailing lists