From: Kees Cook <keescook@chromium.org>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: Andrea Arcangeli <aarcange@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
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>, Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH 1/1] x86: change default to spec_store_bypass_disable=prctl spectre_v2_user=prctl
Date: Mon, 4 Oct 2021 12:14:31 -0700 [thread overview]
Message-ID: <202110041214.564BF23@keescook> (raw)
In-Reply-To: <20211004175431.5myyh2wqnxbwqnwh@treble>
On Mon, Oct 04, 2021 at 10:54:31AM -0700, Josh Poimboeuf wrote:
> On Sat, Sep 11, 2021 at 07:01:40PM -0700, Josh Poimboeuf wrote:
> >
> >
> > > On Sep 11, 2021, at 2:13 PM, Kees Cook <keescook@chromium.org> wrote:
> > >
> > > On Wed, Nov 04, 2020 at 06:50:54PM -0500, Andrea Arcangeli wrote:
> > >> Switch the kernel default of SSBD and STIBP to the ones with
> > >> CONFIG_SECCOMP=n (i.e. spec_store_bypass_disable=prctl
> > >> spectre_v2_user=prctl) even if CONFIG_SECCOMP=y.
> > >
> > > Hello x86 maintainers!
> > >
> > > I'd really like to get this landed, so I'll take this via the
> > > seccomp-tree unless someone else speaks up. This keeps falling off
> > > the edge of my TODO list. :)
> >
> > Thanks! You can add my
> >
> > Acked-by: Josh Poimboeuf <jpoimboe@redhat.com>
>
> Hi Kees,
>
> Ping - I don't see this patch in linux-next. Are you planning on grabbing this
> for the next merge window?
Thanks for the reminder! I've pushed this to the seccomp next tree.
--
Kees Cook
next prev parent reply other threads:[~2021-10-04 19:14 UTC|newest]
Thread overview: 21+ 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 21:57 ` Andrea Arcangeli
2020-11-04 22:14 ` Kees Cook
2020-11-04 22:14 ` Kees Cook
2020-11-04 23:22 ` Thomas Gleixner
2020-11-04 23:22 ` Thomas Gleixner
2020-11-04 23:40 ` Andrea Arcangeli
2020-11-04 23:40 ` Andrea Arcangeli
2020-11-05 0:14 ` [PATCH 0/1] x86: deduplicate the spectre_v2_user documentation Andrea Arcangeli
2020-11-05 0:14 ` Andrea Arcangeli
2020-11-05 0:14 ` [PATCH 1/1] " Andrea Arcangeli
2020-11-05 0:14 ` 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
2020-11-04 23:50 ` 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 [this message]
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=202110041214.564BF23@keescook \
--to=keescook@chromium.org \
--cc=David.Laight@aculab.com \
--cc=aarcange@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.