From: mark gross <mgross@linux.intel.com>
To: Salvatore Bonaccorso <carnil@debian.org>
Cc: Josh Poimboeuf <jpoimboe@redhat.com>,
Borislav Petkov <bp@suse.de>, Tony Luck <tony.luck@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, trivial@kernel.org
Subject: Re: [PATCH] docs: hw-vuln: SRBDS: Fix "Title underline too short" warnings during build
Date: Thu, 11 Jun 2020 11:28:27 -0700 [thread overview]
Message-ID: <20200611182827.GB29107@mtg-dev.jf.intel.com> (raw)
In-Reply-To: <20200609202856.2283975-1-carnil@debian.org>
Ack
Signed-off-by:Mark Gross<mgross@linux.intel.com>
Thanks!
--mark
On Tue, Jun 09, 2020 at 10:28:56PM +0200, Salvatore Bonaccorso wrote:
> Some of the title underlining did not have the correct length causing a few
> warnings when building the htmldocs. Line up each of the title underlinings
> with the text they are under.
>
> Fixes: 7222a1b5b874 ("x86/speculation: Add SRBDS vulnerability and mitigation documentation")
> Cc: Mark Gross <mgross@linux.intel.com>
> Cc: Josh Poimboeuf <jpoimboe@redhat.com>
> Cc: Borislav Petkov <bp@suse.de>
> Cc: Tony Luck <tony.luck@intel.com>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: linux-kernel@vger.kernel.org
> Cc: trivial@kernel.org
> Signed-off-by: Salvatore Bonaccorso <carnil@debian.org>
> ---
> .../hw-vuln/special-register-buffer-data-sampling.rst | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/admin-guide/hw-vuln/special-register-buffer-data-sampling.rst b/Documentation/admin-guide/hw-vuln/special-register-buffer-data-sampling.rst
> index 47b1b3afac99..3b1ce68d2456 100644
> --- a/Documentation/admin-guide/hw-vuln/special-register-buffer-data-sampling.rst
> +++ b/Documentation/admin-guide/hw-vuln/special-register-buffer-data-sampling.rst
> @@ -14,7 +14,7 @@ to the core through the special register mechanism that is susceptible
> to MDS attacks.
>
> Affected processors
> ---------------------
> +-------------------
> Core models (desktop, mobile, Xeon-E3) that implement RDRAND and/or RDSEED may
> be affected.
>
> @@ -59,7 +59,7 @@ executed on another core or sibling thread using MDS techniques.
>
>
> Mitigation mechanism
> --------------------
> +--------------------
> Intel will release microcode updates that modify the RDRAND, RDSEED, and
> EGETKEY instructions to overwrite secret special register data in the shared
> staging buffer before the secret data can be accessed by another logical
> @@ -118,7 +118,7 @@ with the option "srbds=". The option for this is:
> ============= =============================================================
>
> SRBDS System Information
> ------------------------
> +------------------------
> The Linux kernel provides vulnerability status information through sysfs. For
> SRBDS this can be accessed by the following sysfs file:
> /sys/devices/system/cpu/vulnerabilities/srbds
> --
> 2.27.0
>
prev parent reply other threads:[~2020-06-11 18:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 20:28 Salvatore Bonaccorso
2020-06-11 18:28 ` mark gross [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200611182827.GB29107@mtg-dev.jf.intel.com \
--to=mgross@linux.intel.com \
--cc=bp@suse.de \
--cc=carnil@debian.org \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=trivial@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®