Re: [PATCH v3] Documentation: Add section about CPU vulnerabilities for Spectre

[Tim Chen]

On 6/17/19 3:16 PM, Jonathan Corbet wrote:
> On Mon, 17 Jun 2019 22:21:51 +0200 (CEST)
> Thomas Gleixner <tglx@xxxxxxxxxxxxx> wrote:
> 
>>> +Spectre variant 1 attacks take advantage of speculative execution of
>>> +conditional branches, while Spectre variant 2 attacks use speculative
>>> +execution of indirect branches to leak privileged memory. See [1] [5]
>>> +[7] [10] [11].  
>>
>> It would be great to actually link these [N] to the actual http link at the
>> bottom. No idea what's the best way to do that.
>>
>> Jonathan?
> 
> Append an underscore to the link text, so:
> 
> 	See [1_] [5_] ...
> 	
> Then, when adding the links:
> 
> 	.. _1: https://.../
> 
> There are other ways; see
> 
>     http://docutils.sourceforge.net/docs/user/rst/quickref.html#external-hyperlink-targets 
> 
> for the list.

Jonathan,

I want to actually have a generated reference section.  The method you suggested will generate
the reference link as a footer on the same page that refers to the link.  I haven't quite figured
out how to generate a proper bibliography like reference section with hyperlink after googling
for quite a while.


> 
>> The below renders horribly when converted to HTML
>>
>> You probably want to wrap these into a table
>>
>>> +	nospectre_v2	[X86] Disable all mitigations for the Spectre variant 2
>>> +			(indirect branch prediction) vulnerability. System may
>>> +			allow data leaks with this option, which is equivalent
>>> +			to spectre_v2=off.
>>> +
>>> +
>>> +        spectre_v2=     [X86] Control mitigation of Spectre variant 2
>>> +			(indirect branch speculation) vulnerability.
>>> +			The default operation protects the kernel from
>>> +			user space attacks.  
>>
>> Maybe Jonathan has a better idea.
> 
> The easiest thing is probably a definition list:
> 
> 	nospectre_v2
> 	    [X86] Disable all mitigations for the Spectre variant 2
> 	    (indirect branch prediction) ...
> 
> 	spectrev2=
> 	    ...
> 
> i.e. just move the descriptive text into an indented block below the term
> of interest.
> 

Thanks for this suggestion.

Tim