linux-kernel - Re: [PATCH v4 05/15] x86/sev: Use kernel provided SVSM Calling Areas

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <a8d2de1f-700b-73b8-55a4-578cf013dd6f@amd.com>
Date: Wed, 8 May 2024 14:40:06 -0500
From: Tom Lendacky <thomas.lendacky@....com>
To: Borislav Petkov <bp@...en8.de>
Cc: linux-kernel@...r.kernel.org, x86@...nel.org, linux-coco@...ts.linux.dev,
 svsm-devel@...onut-svsm.dev, Thomas Gleixner <tglx@...utronix.de>,
 Ingo Molnar <mingo@...hat.com>, Dave Hansen <dave.hansen@...ux.intel.com>,
 "H. Peter Anvin" <hpa@...or.com>, Andy Lutomirski <luto@...nel.org>,
 Peter Zijlstra <peterz@...radead.org>,
 Dan Williams <dan.j.williams@...el.com>, Michael Roth
 <michael.roth@....com>, Ashish Kalra <ashish.kalra@....com>
Subject: Re: [PATCH v4 05/15] x86/sev: Use kernel provided SVSM Calling Areas

On 5/8/24 14:13, Tom Lendacky wrote:
> On 5/8/24 03:05, Borislav Petkov wrote:
>> On Wed, Apr 24, 2024 at 10:58:01AM -0500, Tom Lendacky wrote:

>>> diff --git a/arch/x86/mm/mem_encrypt_amd.c 
>>> b/arch/x86/mm/mem_encrypt_amd.c
>>> index 422602f6039b..6155020e4d2d 100644
>>> --- a/arch/x86/mm/mem_encrypt_amd.c
>>> +++ b/arch/x86/mm/mem_encrypt_amd.c
>>> @@ -2,7 +2,7 @@
>>>   /*
>>>    * AMD Memory Encryption Support
>>>    *
>>> - * Copyright (C) 2016 Advanced Micro Devices, Inc.
>>> + * Copyright (C) 2016-2024 Advanced Micro Devices, Inc.
>>
>> Are we doing that now?
> 
> Looks like a leftover change... will remove it.

Ah, there is a change in there. I guess I misunderstood your question 
because the change was cutoff from the reply. Anyway, yes, as far as I 
know, we should be doing that.

Thanks,
Tom

> 
> Thanks,
> Tom
> 
>>