From: Alan Cox <alan@linux.intel.com>
To: Alexei Starovoitov <ast@kernel.org>,
"David S . Miller" <davem@davemloft.net>
Cc: Daniel Borkmann <daniel@iogearbox.net>,
Jann Horn <jannh@google.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Dan Williams <dan.j.williams@intel.com>,
Mark Rutland <mark.rutland@arm.com>,
Peter Zijlstra <peterz@infradead.org>,
Elena Reshetova <elena.reshetova@intel.com>,
netdev@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH bpf] bpf: prevent out-of-bounds speculation
Date: Wed, 17 Jan 2018 13:56:14 +0000 [thread overview]
Message-ID: <1516197374.4184.5.camel@linux.intel.com> (raw)
In-Reply-To: <20180105042242.1569490-1-ast@kernel.org>
> That fixes bpf side of "Variant 1: bounds check bypass (CVE-2017-
> 5753)" on
> all architectures with and without JIT.
For Intel we believe this is true for all family 6 Core, Atom and
Knights processors. If that ceases to be the case in future then Intel
will provide guidance beforehand.
For non x86 you need to check what level of data speculation anyone is
doing. I know some Power did data speculation. Your statement may well
be true but it would be nice to see AMD, ARM, Power, Sparc etc acks on
it.
Alan
next parent reply other threads:[~2018-01-17 13:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180105042242.1569490-1-ast@kernel.org>
2018-01-17 13:56 ` Alan Cox [this message]
[not found] <20180105042811.1590965-1-ast@fb.com>
2018-01-05 17:53 ` [PATCH bpf] bpf: prevent out-of-bounds speculation Mark Rutland
2018-01-08 17:05 ` Mark Rutland
2018-01-08 18:49 ` Linus Torvalds
2018-01-09 10:21 ` Will Deacon
2018-01-10 19:47 ` Will Deacon
2018-01-10 22:29 ` Alexei Starovoitov
2018-02-05 15:38 ` Will Deacon
2018-01-09 15:04 ` Mark Rutland
2018-01-17 14:47 ` Alan Cox
2018-01-08 23:20 ` Alexei Starovoitov
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=1516197374.4184.5.camel@linux.intel.com \
--to=alan@linux.intel.com \
--cc=ast@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=elena.reshetova@intel.com \
--cc=jannh@google.com \
--cc=kernel-team@fb.com \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).