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: <8B866DA6-ED68-4681-8D83-A23E8F18E77C@alien8.de>
Date:   Wed, 06 Jan 2021 15:57:55 +0100
From:   Boris Petkov <bp@...en8.de>
To:     Peter Zijlstra <peterz@...radead.org>, x86@...nel.org
CC:     linux-kernel@...r.kernel.org, peterz@...radead.org,
        rdunlap@...radead.org, jpoimboe@...hat.com, sfr@...b.auug.org.au,
        tony.luck@...el.com
Subject: Re: [RFC][PATCH 6/6] x86/mce: Dont use noinstr for now

On January 6, 2021 3:36:25 PM GMT+01:00, Peter Zijlstra <peterz@...radead.org> wrote:
>Instead of using noinstr, kill instrumentation for all of mce/. This
>switches MCE over to a best-effort but non-validated mode. Doing
>better will require a significant investment of time and effort.

Another thing that we could do is carve out only the stuff which needs to be noinstr into a separate compilation unit and disable tracing only for that while keeping the rest traceable. Need to try it to see how ugly it'll get...

-- 
Sent from a small device: formatting sux and brevity is inevitable. 

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ