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  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]
Date:   Mon, 29 Apr 2019 22:51:46 +0200
From:   Borislav Petkov <>
To:     Gary R Hook <>
Cc:     Thomas Gleixner <>,
        "Hook, Gary" <>,
        "" <>,
        "" <>,
        "" <>,
        "" <>,
        "" <>,
        "" <>,
        Alexander Potapenko <>
Subject: Re: [PATCH] x86/mm/mem_encrypt: Disable all instrumentation for SME
 early boot code

On Mon, Apr 29, 2019 at 08:16:07PM +0000, Gary R Hook wrote:
> Yes, option 4 would be a combination of using a local copy of strncmp()

Why the local copy?

> and disabling instrumentation (KASAN, KCOV, whatever) for
> arch/x86/lib/cmdline.c when SME is enabled.

I think this should suffice. You only disable instrumentation when
CONFIG_AMD_MEM_ENCRYPT=y and not do any local copies but use the generic



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

Powered by blists - more mailing lists