netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexei Starovoitov <ast@kernel.org>
To: <davem@davemloft.net>
Cc: <daniel@iogearbox.net>, <netdev@vger.kernel.org>,
	<bpf@vger.kernel.org>, <kernel-team@fb.com>
Subject: pull-request: bpf 2019-03-24
Date: Sun, 24 Mar 2019 19:57:55 -0700	[thread overview]
Message-ID: <20190325025755.1757841-1-ast@kernel.org> (raw)

Hi David,

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

The main changes are:

1) libbpf verision fix up from Daniel.

2) fix liveness propagation from Jakub.

3) fix verbose print of refcounted regs from Martin.

4) fix for large map allocations from Martynas.

5) fix use after free in sanitize_ptr_alu from Xu.

Please consider pulling these changes from:

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

Thanks a lot!

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

The following changes since commit ea239314fe42ace880bdd834256834679346c80e:

  tipc: allow service ranges to be connect()'ed on RDM/DGRAM (2019-03-17 21:32:11 -0700)

are available in the Git repository at:

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

for you to fetch changes up to a7d6ac3761d34bfd4294d7843714c91c600738cf:

  Merge branch 'libbpf-fixup' (2019-03-24 19:49:05 -0700)

----------------------------------------------------------------
Alexei Starovoitov (1):
      Merge branch 'libbpf-fixup'

Daniel Borkmann (2):
      bpf, libbpf: fix version info and add it to shared object
      bpf, libbpf: clarify bump in libbpf version info

Jakub Kicinski (1):
      bpf: verifier: propagate liveness on all frames

Martin KaFai Lau (1):
      bpf: Only print ref_obj_id for refcounted reg

Martynas Pumputis (1):
      bpf: Try harder when allocating memory for large maps

Xu Yu (1):
      bpf: do not restore dst_reg when cur_state is freed

 kernel/bpf/syscall.c                         | 22 ++++++++++-----
 kernel/bpf/verifier.c                        | 35 +++++++++++++++--------
 tools/lib/bpf/Makefile                       | 42 ++++++++++++++++++----------
 tools/lib/bpf/README.rst                     |  1 +
 tools/testing/selftests/bpf/verifier/calls.c | 25 +++++++++++++++++
 5 files changed, 92 insertions(+), 33 deletions(-)

             reply	other threads:[~2019-03-25  2:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-25  2:57 Alexei Starovoitov [this message]
2019-03-25  3:45 ` pull-request: bpf 2019-03-24 David Miller

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=20190325025755.1757841-1-ast@kernel.org \
    --to=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=kernel-team@fb.com \
    --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).