linux-kernel - Re: AMD SME + KASAN = doom

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] [day] [month] [year] [list]

Message-Id: <E41B9DFC-F407-4C6A-BCFB-6E3E6B72BA0C@lca.pw>
Date:   Sat, 13 Jun 2020 13:03:18 -0400
From:   Qian Cai <cai@....pw>
To:     Borislav Petkov <bp@...e.de>
Cc:     Thomas.Lendacky@....com, brijesh.singh@....com, tglx@...utronix.de,
        glider@...gle.com, peterz@...radead.org, dvyukov@...gle.com,
        kasan-dev@...glegroups.com, linux-kernel@...r.kernel.org
Subject: Re: AMD SME + KASAN = doom



> On Jun 13, 2020, at 11:54 AM, Borislav Petkov <bp@...e.de> wrote:
> 
> $ head arch/x86/mm/Makefile
> # SPDX-License-Identifier: GPL-2.0
> # Kernel does not boot with instrumentation of tlb.c and mem_encrypt*.c
> KCOV_INSTRUMENT_tlb.o                   := n
> KCOV_INSTRUMENT_mem_encrypt.o           := n
> KCOV_INSTRUMENT_mem_encrypt_identity.o  := n
> 
> KASAN_SANITIZE_mem_encrypt.o            := n
> KASAN_SANITIZE_mem_encrypt_identity.o   := n
> 
> so something else needs to be de-KASAN-ed too.

Okay, I’ll try to figure out what else needs to be done.

> 
> For now flip your Subject: AMD SME - KASAN = boot.

Which is a bit of shame because KASAN is proved useful for testing and at the same time SME could flags some issues with drivers like megasas_raid (where the driver will do a  firmware dump during the boot which I plan to debug more a bit later).