lkml.org 
[lkml]   [2017]   [Jul]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [RFC Part1 PATCH v3 04/17] x86/mm: Don't attempt to encrypt initrd under SEV
    On Mon, Jul 24, 2017 at 02:07:44PM -0500, Brijesh Singh wrote:
    > From: Tom Lendacky <thomas.lendacky@amd.com>
    >
    > When SEV is active the initrd/initramfs will already have already been
    > placed in memory encyrpted so do not try to encrypt it.
    >
    > Signed-off-by: Tom Lendacky <thomas.lendacky@amd.com>
    > Signed-off-by: Brijesh Singh <brijesh.singh@amd.com>
    > ---
    > arch/x86/kernel/setup.c | 6 ++++--
    > 1 file changed, 4 insertions(+), 2 deletions(-)
    >
    > diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c
    > index 0bfe0c1..01d56a1 100644
    > --- a/arch/x86/kernel/setup.c
    > +++ b/arch/x86/kernel/setup.c
    > @@ -379,9 +379,11 @@ static void __init reserve_initrd(void)
    > * If SME is active, this memory will be marked encrypted by the
    > * kernel when it is accessed (including relocation). However, the
    > * ramdisk image was loaded decrypted by the bootloader, so make
    > - * sure that it is encrypted before accessing it.
    > + * sure that it is encrypted before accessing it. For SEV the
    > + * ramdisk will already be encyrpted, so only do this for SME.
    ^^^^^^^^^
    Please introduce a spellchecker into your patch creation workflow.

    --
    Regards/Gruss,
    Boris.

    SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
    --

    \
     
     \ /
      Last update: 2017-07-26 16:46    [W:4.140 / U:0.288 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site