linux-kernel - Re: [PATCH v2] Documentation: Use grid table over list table

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: <20240908155043.556286-1-zulinx86@gmail.com>
Date: Sun,  8 Sep 2024 15:50:43 +0000
From: Takahiro Itazuri <zulinx86@...il.com>
To: pawan.kumar.gupta@...ux.intel.com,
	corbet@....net,
	jani.nikula@...ux.intel.com
Cc: bp@...en8.de,
	jpoimboe@...nel.org,
	linux-doc@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	peterz@...radead.org,
	tglx@...utronix.de,
	zulinx86@...il.com
Subject: Re: [PATCH v2] Documentation: Use grid table over list table

On Fri, 6 Sep 2024, Pawan Gupta <pawan.kumar.gupta@...ux.intel.com> wrote:
> On Fri, Sep 06, 2024 at 04:26:49PM +0300, Jani Nikula wrote:
> > On Fri, 06 Sep 2024, Takahiro Itazuri <itazur@...zon.com> wrote:
> > > Using a simple table, a line break in the first column would be
> > > recognized as two rows. To avoid that, list table was used but it
> > > is unreadable for plain text readers. Uses grid table instead.
> > >
> > > Signed-off-by: Takahiro Itazuri <itazur@...zon.com>
> > > ---
> > > Changes in v2:
> > > - Use grid table over list table (applying to not only GDS but also
> > >   other vulnerabilities)
> > > - Link to v1: https://lore.kernel.org/all/20240903132533.26458-1-itazur@amazon.com/
> > 
> > I see that Jon asked you to use a grid table.
> > 
> > But when I look at what's being changed, I can't help but think a
> > definition list [1] might provide the best compromise between readable
> > (and easily editable!) source rst and generated html. I don't think it
> > has to be a *table* in either.

Thank you for your feedback!

Then, I'd prefer list table again because it doesn't change the existing HTML
appearance and it doesn't look much different from the definition list in plain
text format.

For readability/editability in plain text format, a line break can be inserted
between items as follows:

.. list-table::

   * - 'Not affected'
     - Processor not vulnerable.

   * - 'Vulnerable'
     - Processor vulnerable and mitigation disabled.

   * - 'Vulnerable: No microcode'
     - Processor vulnerable and microcode is missing migitation.

   * - 'Mitigation: AVX disabled, no microcode'
     - Processor is vulnerable and microcode is missing mitigation. AVX disbaled as
       mitigation.

   * - 'Mitigation: Microcode'
     - Processor is vulnerable and mitigation is in effect.

   * - 'Mitigation: Microcode (locked)'
     - Processor is vulnerable and mitigation is in effect and cannot be disabled.

   * - 'Unknown: Dependent on hypervisor status'
     - Running on a virtual guest processor that is affected but with no way to
       know if host processor is mitigated or vulnerable.

Thanks,
Taka