[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <C011ADB3-3B49-4865-B988-9F682F462F32@intel.com>
Date: Mon, 6 Dec 2021 21:48:18 +0000
From: "Bae, Chang Seok" <chang.seok.bae@...el.com>
To: "Lutomirski, Andy" <luto@...nel.org>
CC: Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...nel.org>, Borislav Petkov <bp@...e.de>,
X86 ML <x86@...nel.org>,
Herbert Xu <herbert@...dor.apana.org.au>,
"Williams, Dan J" <dan.j.williams@...el.com>,
"Hansen, Dave" <dave.hansen@...el.com>,
"Shankar, Ravi V" <ravi.v.shankar@...el.com>,
Linux Crypto Mailing List <linux-crypto@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH v2 00/11] x86: Support Intel Key Locker
On May 18, 2021, at 10:10, Andy Lutomirski <luto@...nel.org> wrote:
> On 5/17/21 11:21 AM, Bae, Chang Seok wrote:
>> On May 15, 2021, at 11:01, Andy Lutomirski <luto@...nel.org> wrote:
>>>
>>> I have high-level questions:
>>>
>>> What is the expected use case?
>>
>> The wrapping key here is only used for new AES instructions.
>>
>> I’m aware of their potential use cases for encrypting file system or disks.
>
> I would like to understand what people are actually going to do with
> this. Give me a user story or two, please. If it turns out to be
> useless, I would rather not merge it.
Hi Andy,
V3 was posted here with both cover letter and code changes to address this:
https://lore.kernel.org/lkml/20211124200700.15888-1-chang.seok.bae@intel.com/
Appreciate, if you can comment on the use case at least.
Thanks,
Chang
Powered by blists - more mailing lists