From: Andrea Arcangeli <aarcange@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: YiFei Zhu <zhuyifei1999@gmail.com>,
Linux Containers <containers@lists.linux-foundation.org>,
YiFei Zhu <yifeifz2@illinois.edu>, bpf <bpf@vger.kernel.org>,
kernel list <linux-kernel@vger.kernel.org>,
Aleksa Sarai <cyphar@cyphar.com>,
Andy Lutomirski <luto@amacapital.net>,
David Laight <David.Laight@aculab.com>,
Dimitrios Skarlatos <dskarlat@cs.cmu.edu>,
Giuseppe Scrivano <gscrivan@redhat.com>,
Hubertus Franke <frankeh@us.ibm.com>,
Jack Chen <jianyan2@illinois.edu>, Jann Horn <jannh@google.com>,
Josep Torrellas <torrella@illinois.edu>,
Tianyin Xu <tyxu@illinois.edu>,
Tobin Feldman-Fitzthum <tobin@ibm.com>,
Tycho Andersen <tycho@tycho.pizza>,
Valentin Rothberg <vrothber@redhat.com>,
Will Drewry <wad@chromium.org>, Jiri Kosina <jikos@kernel.org>,
Waiman Long <longman@redhat.com>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Andi Kleen <ak@linux.intel.com>
Subject: [PATCH 0/1] x86: deduplicate the spectre_v2_user documentation
Date: Wed, 4 Nov 2020 19:14:05 -0500 [thread overview]
Message-ID: <20201105001406.13005-1-aarcange@redhat.com> (raw)
In-Reply-To: <20201104234047.GA18850@redhat.com>
Hello,
Could you help checking if this incremental doc cleanup is possible?
After the previous patch is applied, there's still a leftover mention
of seccomp that should be removed in a duped bit of documentation, so
I tentatively referred the original documentation already updated in
sync, instead of keeping the dup around and applying the same update
to the dup.
Note: as far as I can tell spec_store_bypass_disable= documentation is
not duplicated in spectre.rst, that's better in my view. The more dups
we have the more one goes out of sync..
Andrea Arcangeli (1):
x86: deduplicate the spectre_v2_user documentation
Documentation/admin-guide/hw-vuln/spectre.rst | 51 +------------------
1 file changed, 2 insertions(+), 49 deletions(-)
next prev parent reply other threads:[~2020-11-05 0:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 21:57 RFC: default to spec_store_bypass_disable=prctl spectre_v2_user=prctl Andrea Arcangeli
2020-11-04 22:14 ` Kees Cook
2020-11-04 23:22 ` Thomas Gleixner
2020-11-04 23:40 ` Andrea Arcangeli
2020-11-05 0:14 ` Andrea Arcangeli [this message]
2020-11-05 0:14 ` [PATCH 1/1] x86: deduplicate the spectre_v2_user documentation Andrea Arcangeli
2021-09-11 21:13 ` Kees Cook
2020-11-04 23:50 ` [PATCH 1/1] x86: change default to spec_store_bypass_disable=prctl spectre_v2_user=prctl Andrea Arcangeli
2021-09-11 21:13 ` Kees Cook
2021-09-12 2:01 ` Josh Poimboeuf
2021-10-04 17:54 ` Josh Poimboeuf
2021-10-04 19:14 ` Kees Cook
2021-09-12 23:14 ` Waiman Long
2021-07-10 18:05 ` RFC: " Jim Newsome
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=20201105001406.13005-1-aarcange@redhat.com \
--to=aarcange@redhat.com \
--cc=David.Laight@aculab.com \
--cc=ak@linux.intel.com \
--cc=bpf@vger.kernel.org \
--cc=containers@lists.linux-foundation.org \
--cc=cyphar@cyphar.com \
--cc=dskarlat@cs.cmu.edu \
--cc=frankeh@us.ibm.com \
--cc=gscrivan@redhat.com \
--cc=jannh@google.com \
--cc=jianyan2@illinois.edu \
--cc=jikos@kernel.org \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=luto@amacapital.net \
--cc=tglx@linutronix.de \
--cc=tobin@ibm.com \
--cc=torrella@illinois.edu \
--cc=tycho@tycho.pizza \
--cc=tyxu@illinois.edu \
--cc=vrothber@redhat.com \
--cc=wad@chromium.org \
--cc=yifeifz2@illinois.edu \
--cc=zhuyifei1999@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).