linux-kernel - Re: [RFC] #MC mess

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

Message-Id: <3CF4895A-5BCF-4E5C-B8D9-F9019DD02A12@amacapital.net>
Date:   Tue, 18 Feb 2020 15:10:17 -0800
From:   Andy Lutomirski <luto@...capital.net>
To:     "Luck, Tony" <tony.luck@...el.com>
Cc:     Borislav Petkov <bp@...en8.de>,
        Peter Zijlstra <peterz@...radead.org>,
        Steven Rostedt <rostedt@...dmis.org>,
        Andy Lutomirski <luto@...nel.org>, x86-ml <x86@...nel.org>,
        lkml <linux-kernel@...r.kernel.org>
Subject: Re: [RFC] #MC mess



> On Feb 18, 2020, at 10:20 AM, Luck, Tony <tony.luck@...el.com> wrote:
> 
> 
>> 
>> Anything else I'm missing? It is likely...
> 
> +    hw_breakpoint_disable();
> +    static_key_disable(&__tracepoint_read_msr.key);
> +    tracing_off();
> +
>    ist_enter(regs);
> 
> How about some code to turn all those back on for a recoverable (where we actually recovered) #MC?
> 
> 


At the very least, in the user_mode(regs) case, tracing is fine.