linux-kernel - Re: [PATCH 5.18 01/11] Documentation: Add documentation for Processor MMIO Stale Data

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <94468546-5571-b61f-0d98-8501626e30e3@gmail.com>
Date:   Wed, 15 Jun 2022 08:06:37 +0700
From:   Bagas Sanjaya <bagasdotme@...il.com>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        linux-kernel@...r.kernel.org
Cc:     stable@...r.kernel.org,
        Pawan Gupta <pawan.kumar.gupta@...ux.intel.com>,
        Borislav Petkov <bp@...e.de>,
        Thomas Gleixner <tglx@...utronix.de>,
        Linux Doc Mailing List <linux-doc@...r.kernel.org>
Subject: Re: [PATCH 5.18 01/11] Documentation: Add documentation for Processor
 MMIO Stale Data

On 6/15/22 01:40, Greg Kroah-Hartman wrote:
> +  .. list-table::
> +
> +     * - 'Not affected'
> +       - The processor is not vulnerable
> +     * - 'Vulnerable'
> +       - The processor is vulnerable, but no mitigation enabled
> +     * - 'Vulnerable: Clear CPU buffers attempted, no microcode'
> +       - The processor is vulnerable, but microcode is not updated. The
> +         mitigation is enabled on a best effort basis.
> +     * - 'Mitigation: Clear CPU buffers'
> +       - The processor is vulnerable and the CPU buffer clearing mitigation is
> +         enabled.
> +
> +If the processor is vulnerable then the following information is appended to
> +the above information:
> +
> +  ========================  ===========================================
> +  'SMT vulnerable'          SMT is enabled
> +  'SMT disabled'            SMT is disabled
> +  'SMT Host state unknown'  Kernel runs in a VM, Host SMT state unknown
> +  ========================  ===========================================
> +

Why is list-table used in sysfs table instead of usual ASCII table in SMT
vulnerabilities list above? I think using ASCII table in both cases is enough
for the purpose.

-- 
An old man doll... just what I always wanted! - Clara