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:   Fri, 17 Feb 2017 10:57:56 -0500
From:   Konrad Rzeszutek Wilk <>
To:     Tom Lendacky <>
        Rik van Riel <>,
        Radim Krčmář <>,
        Toshimitsu Kani <>,
        Arnd Bergmann <>,
        Jonathan Corbet <>,
        Matt Fleming <>,
        "Michael S. Tsirkin" <>,
        Joerg Roedel <>,
        Paolo Bonzini <>,
        Brijesh Singh <>,
        Ingo Molnar <>,
        Alexander Potapenko <>,
        Andy Lutomirski <>,
        "H. Peter Anvin" <>, Borislav Petkov <>,
        Andrey Ryabinin <>,
        Thomas Gleixner <>,
        Larry Woodman <>,
        Dmitry Vyukov <>
Subject: Re: [RFC PATCH v4 26/28] x86: Allow kexec to be used with SME

On Thu, Feb 16, 2017 at 09:47:55AM -0600, Tom Lendacky wrote:
> Provide support so that kexec can be used to boot a kernel when SME is
> enabled.

Is the point of kexec and kdump to ehh, dump memory ? But if the
rest of the memory is encrypted you won't get much, will you?

Would it make sense to include some printk to the user if they
are setting up kdump that they won't get anything out of it?


Powered by blists - more mailing lists