From: Eric Dumazet <eric.dumazet@gmail•com>
To: Jiri Slaby <jslaby@suse•cz>, gregkh@linuxfoundation•org
Cc: stable@vger•kernel.org, ast@kernel•org, netdev@vger•kernel.org,
Daniel Borkmann <daniel@iogearbox•net>
Subject: Re: [PATCH 4.4-stable 6/6] bpf: prevent out-of-bounds speculation
Date: Fri, 12 Jan 2018 08:52:23 -0800 [thread overview]
Message-ID: <1515775943.131759.44.camel@gmail.com> (raw)
In-Reply-To: <20180112161721.8843-7-jslaby@suse.cz>
On Fri, 2018-01-12 at 17:17 +0100, Jiri Slaby wrote:
> From: Alexei Starovoitov <ast@kernel•org>
>
> commit b2157399cc9898260d6031c5bfe45fe137c1fbe7 upstream.
>
> Under speculation, CPUs may mis-predict branches in bounds checks. Thus,
> memory accesses under a bounds check may be speculated even if the
> bounds check fails, providing a primitive for building a side channel.
>
Make sure to also backport
https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git/commit/?id=
bbeb6e4323dad9b5e0ee9f60c223dd532e2403b1
next prev parent reply other threads:[~2018-01-12 16:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 16:17 [PATCH 4.4-stable 0/6] bpf: prevent out-of-bounds speculation Jiri Slaby
2018-01-12 16:17 ` [PATCH 4.4-stable 1/6] bpf: add bpf_patch_insn_single helper Jiri Slaby
2018-01-12 16:17 ` [PATCH 4.4-stable 2/6] bpf: don't (ab)use instructions to store state Jiri Slaby
2018-01-12 16:17 ` [PATCH 4.4-stable 3/6] bpf: move fixup_bpf_calls() function Jiri Slaby
2018-01-12 16:17 ` [PATCH 4.4-stable 4/6] bpf: refactor fixup_bpf_calls() Jiri Slaby
2018-01-12 16:17 ` [PATCH 4.4-stable 5/6] bpf: adjust insn_aux_data when patching insns Jiri Slaby
2018-01-12 16:17 ` [PATCH 4.4-stable 6/6] bpf: prevent out-of-bounds speculation Jiri Slaby
2018-01-12 16:52 ` Eric Dumazet [this message]
2018-01-12 16:28 ` [PATCH 4.4-stable 0/6] " Daniel Borkmann
2018-01-12 16:58 ` [PATCH 4.4-stable 7/7] bpf, array: fix overflow in max_entries and undefined behavior in index_mask Jiri Slaby
2018-01-13 19:49 ` [PATCH 4.4-stable 0/6] bpf: prevent out-of-bounds speculation Greg KH
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=1515775943.131759.44.camel@gmail.com \
--to=eric.dumazet@gmail$(echo .)com \
--cc=ast@kernel$(echo .)org \
--cc=daniel@iogearbox$(echo .)net \
--cc=gregkh@linuxfoundation$(echo .)org \
--cc=jslaby@suse$(echo .)cz \
--cc=netdev@vger$(echo .)kernel.org \
--cc=stable@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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