From: Alan Cox <alan@linux.intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Mark Rutland <mark.rutland@arm.com>
Cc: Alexei Starovoitov <ast@fb.com>,
"David S . Miller" <davem@davemloft.net>,
Daniel Borkmann <daniel@iogearbox.net>,
Jann Horn <jannh@google.com>,
Dan Williams <dan.j.williams@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Elena Reshetova <elena.reshetova@intel.com>,
Network Development <netdev@vger.kernel.org>,
kernel-team <kernel-team@fb.com>,
Will Deacon <will.deacon@arm.com>
Subject: Re: [PATCH bpf] bpf: prevent out-of-bounds speculation
Date: Wed, 17 Jan 2018 14:47:50 +0000 [thread overview]
Message-ID: <1516200470.4184.26.camel@linux.intel.com> (raw)
In-Reply-To: <CA+55aFz0tsreoa=5Ud2noFCpng-dizLBhT9WU9asyhpLfjdcYA@mail.gmail.com>
> (c) isn't actually done in any real CPU's today that I'm aware of
> (unless you want to call the return stack data speculation).
There are processors out there today that data speculate.
For Intel family 6 Core, Knights and Atom today all is good.
Alan
next prev parent reply other threads:[~2018-01-17 14:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
2018-01-08 23:20 ` Alexei Starovoitov
[not found] <20180105042242.1569490-1-ast@kernel.org>
2018-01-17 13:56 ` Alan Cox
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=1516200470.4184.26.camel@linux.intel.com \
--to=alan@linux.intel.com \
--cc=ast@fb.com \
--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 \
--cc=will.deacon@arm.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.