netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: daniel@iogearbox.net
Cc: ast@kernel.org, netdev@vger.kernel.org
Subject: Re: pull-request: bpf 2018-01-09
Date: Wed, 10 Jan 2018 11:17:49 -0500 (EST)	[thread overview]
Message-ID: <20180110.111749.2156886424917193035.davem@davemloft.net> (raw)
In-Reply-To: <20180109220321.9973-1-daniel@iogearbox.net>

From: Daniel Borkmann <daniel@iogearbox.net>
Date: Tue,  9 Jan 2018 23:03:21 +0100

> The following pull-request contains BPF updates for your *net* tree.
> 
> The main changes are:
> 
> 1) Prevent out-of-bounds speculation in BPF maps by masking the
>    index after bounds checks in order to fix spectre v1, and
>    add an option BPF_JIT_ALWAYS_ON into Kconfig that allows for
>    removing the BPF interpreter from the kernel in favor of
>    JIT-only mode to make spectre v2 harder, from Alexei.
> 
> 2) Remove false sharing of map refcount with max_entries which
>    was used in spectre v1, from Daniel.
> 
> 3) Add a missing NULL psock check in sockmap in order to fix
>    a race, from John.
> 
> 4) Fix test_align BPF selftest case since a recent change in
>    verifier rejects the bit-wise arithmetic on pointers
>    earlier but test_align update was missing, from Alexei.
> 
> Please consider pulling these changes from:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git

Pulled, thanks Daniel.

      reply	other threads:[~2018-01-10 16:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-09 22:03 pull-request: bpf 2018-01-09 Daniel Borkmann
2018-01-10 16:17 ` David Miller [this message]

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=20180110.111749.2156886424917193035.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=ast@kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=netdev@vger.kernel.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).