[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190109024222.izaveh2jm4mqtihk@ast-mbp>
Date: Tue, 8 Jan 2019 18:42:24 -0800
From: Alexei Starovoitov <alexei.starovoitov@...il.com>
To: Tim Chen <tim.c.chen@...ux.intel.com>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Jiri Kosina <jikos@...nel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Tom Lendacky <thomas.lendacky@....com>,
Ingo Molnar <mingo@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
Josh Poimboeuf <jpoimboe@...hat.com>,
Andrea Arcangeli <aarcange@...hat.com>,
David Woodhouse <dwmw@...zon.co.uk>,
Andi Kleen <ak@...ux.intel.com>,
Dave Hansen <dave.hansen@...el.com>,
Asit Mallick <asit.k.mallick@...el.com>,
Arjan van de Ven <arjan@...ux.intel.com>,
Jon Masters <jcm@...hat.com>,
Waiman Long <longman9394@...il.com>,
Greg KH <gregkh@...uxfoundation.org>,
Borislav Petkov <bp@...en8.de>, linux-kernel@...r.kernel.org,
x86@...nel.org, stable@...r.kernel.org, daniel@...earbox.net,
davem@...emloft.net
Subject: Re: [PATCH] x86/speculation: Add document to describe Spectre and
its mitigations
On Tue, Jan 08, 2019 at 05:41:37PM -0800, Tim Chen wrote:
> On 1/8/19 5:11 PM, Alexei Starovoitov wrote:
>
> >>
> >> Alexi,
> >>
> >> Do you have any suggestions on how to rewrite this two paragraphs? You
> >> are probably the best person to update content for this section.
> >
> > how about moving bpf bits out of this doc and placing them under Documentation/bpf/ ?
> > We can create bpf_security.rst there with specdown mitigations, best practices,
> > useful sysctl and config knobs, etc.
> >
>
> Maybe we can provide some minimum but accurate info here on this category of Spectre attack
> for completeness. We can later provide a link to bpf_security.rst here with more details
> when that becomes available.
>
> Otherwise, I can remove it if you prefer. But people concerned about Spectre will most likely read
> this doc first. I want them to be pointed to the detailed BPF security doc.
since Documentation/ got converted to .rst, the links made it easy to follow
from one doc into another.
I think splitting big doc makes it easier for users to read
and for us to maintain/update.
Powered by blists - more mailing lists