netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Borkmann <daniel@iogearbox.net>
To: davem@davemloft.net
Cc: kuba@kernel.org, daniel@iogearbox.net, ast@kernel.org,
	andrii@kernel.org, netdev@vger.kernel.org, bpf@vger.kernel.org
Subject: pull-request: bpf 2021-06-15
Date: Tue, 15 Jun 2021 23:39:27 +0200	[thread overview]
Message-ID: <20210615213927.27713-1-daniel@iogearbox.net> (raw)

Hi David, hi Jakub,

The following pull-request contains BPF updates for your *net* tree.

We've added 5 non-merge commits during the last 11 day(s) which contain
a total of 10 files changed, 115 insertions(+), 16 deletions(-).

The main changes are:

1) Fix marking incorrect umem ring as done in libbpf's
   xsk_socket__create_shared() helper, from Kev Jackson.

2) Fix oob leakage under a spectre v1 type confusion
   attack, from Daniel Borkmann.

Please consider pulling these changes from:

  git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git

Thanks a lot!

Also thanks to reporters, reviewers and testers of commits in this pull-request:

Adam Morrison, Alexei Starovoitov, Benedict Schlueter, John Fastabend, 
Ofek Kirzner, Piotr Krysiuk, Yonghong Song

----------------------------------------------------------------

The following changes since commit 1a8024239dacf53fcf39c0f07fbf2712af22864f:

  virtio-net: fix for skb_over_panic inside big mode (2021-06-03 15:29:04 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git 

for you to fetch changes up to 973377ffe8148180b2651825b92ae91988141b05:

  bpf, selftests: Adjust few selftest outcomes wrt unreachable code (2021-06-14 23:06:38 +0200)

----------------------------------------------------------------
Daniel Borkmann (4):
      bpf: Inherit expanded/patched seen count from old aux data
      bpf: Do not mark insn as seen under speculative path verification
      bpf: Fix leakage under speculation on mispredicted branches
      bpf, selftests: Adjust few selftest outcomes wrt unreachable code

Kev Jackson (1):
      libbpf: Fixes incorrect rx_ring_setup_done

 kernel/bpf/verifier.c                              | 68 +++++++++++++++++++---
 tools/lib/bpf/xsk.c                                |  2 +-
 tools/testing/selftests/bpf/test_verifier.c        |  2 +-
 tools/testing/selftests/bpf/verifier/and.c         |  2 +
 tools/testing/selftests/bpf/verifier/bounds.c      | 14 +++++
 tools/testing/selftests/bpf/verifier/dead_code.c   |  2 +
 tools/testing/selftests/bpf/verifier/jmp32.c       | 22 +++++++
 tools/testing/selftests/bpf/verifier/jset.c        | 10 ++--
 tools/testing/selftests/bpf/verifier/unpriv.c      |  2 +
 .../selftests/bpf/verifier/value_ptr_arith.c       |  7 ++-
 10 files changed, 115 insertions(+), 16 deletions(-)

                 reply	other threads:[~2021-06-15 21:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20210615213927.27713-1-daniel@iogearbox.net \
    --to=daniel@iogearbox.net \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --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).