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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 18 May 2017 11:02:12 +0200
From:   Borislav Petkov <>
To:     Tom Lendacky <>
Cc:,,,,,,,,,, Rik van Riel <>,
        Radim Krčmář <>,
        Toshimitsu Kani <>,
        Arnd Bergmann <>,
        Jonathan Corbet <>,
        Matt Fleming <>,
        "Michael S. Tsirkin" <>,
        Joerg Roedel <>,
        Konrad Rzeszutek Wilk <>,
        Paolo Bonzini <>,
        Larry Woodman <>,
        Brijesh Singh <>,
        Ingo Molnar <>,
        Andy Lutomirski <>,
        "H. Peter Anvin" <>,
        Andrey Ryabinin <>,
        Alexander Potapenko <>,
        Dave Young <>,
        Thomas Gleixner <>,
        Dmitry Vyukov <>
Subject: Re: [PATCH v5 17/32] x86/mm: Add support to access boot related data
 in the clear

On Wed, May 17, 2017 at 01:54:39PM -0500, Tom Lendacky wrote:
> I was worried what the compiler might do when CONFIG_EFI is not set,
> but it appears to take care of it. I'll double check though.

There's a efi_enabled() !CONFIG_EFI version too, so should be fine.

> I may introduce a length variable to capture data->len right after
> paddr_next is set and then have just a single memunmap() call before
> the if check.


> I tried that, but calling an "__init" function (early_memremap()) from
> a non "__init" function generated warnings. I suppose I can pass in a
> function for the map and unmap but that looks worse to me (also the
> unmap functions take different arguments).

No, the other way around: the __init function should call the non-init
one and you need the non-init one anyway for memremap_is_setup_data().

> This is like the chicken and the egg scenario. In order to determine if
> an address is setup data I have to explicitly map the setup data chain
> as decrypted. In order to do that I have to supply a flag to explicitly
> map the data decrypted otherwise I wind up back in the
> memremap_is_setup_data() function again and again and again...

Oh, fun.


Good mailing practices for 400: avoid top-posting and trim the reply.

Powered by blists - more mailing lists