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]
Date:   Thu, 18 Apr 2019 01:19:41 +0200 (CEST)
From:   Thomas Gleixner <>
To:     Fenghua Yu <>
cc:     Ingo Molnar <>, Borislav Petkov <>,
        H Peter Anvin <>,
        Paolo Bonzini <>,
        Dave Hansen <>,
        Ashok Raj <>,
        Peter Zijlstra <>,
        Ravi V Shankar <>,
        Xiaoyao Li <>,
        Christopherson Sean J <>,
        Kalle Valo <>,
        Michael Chan <>,
        linux-kernel <>,
        x86 <>,,,
Subject: Re: [PATCH v7 18/21] x86/clearcpuid: Support feature flag string in
 kernel option clearcpuid

On Wed, 17 Apr 2019, Fenghua Yu wrote:

> The kernel option clearcpuid currently only takes feature bit which
> can be changed from kernel to kernel.
> Extend clearcpuid to use cap flag string, which is defined in
> x86_cap_flags[] and won't be changed from kernel to kernel.
> And user can easily get the cap flag string from /proc/cpuinfo.

If your machine dies because init triggers #AC then please explain how that
easily can be read from /proc/cpuinfo and how the sysadmin can figure out
what the heck he needs to write on the kernel command line.

The whole 'clearcpuid' thing should have never been merged. It's a pure
testing/debugging thing. And no, we are not going to proliferate it and
extend it for dubious value. Quite the contrary, we should simply rip it

Add a simple 'noac' or whatever command line option, which is documented
proper and can easily be mapped to a #AC crash during boot.



Powered by blists - more mailing lists