Netdev List
 help / color / mirror / Atom feed
From: Daniel Borkmann <daniel@iogearbox.net>
To: davem@davemloft.net
Cc: daniel@iogearbox.net, ast@kernel.org, netdev@vger.kernel.org,
	bpf@vger.kernel.org
Subject: pull-request: bpf 2019-08-11
Date: Sun, 11 Aug 2019 21:58:34 +0200	[thread overview]
Message-ID: <20190811195834.3430-1-daniel@iogearbox.net> (raw)

Hi David,

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

The main changes are:

1) x64 JIT code generation fix for backward-jumps to 1st insn, from Alexei.

2) Fix buggy multi-closing of BTF file descriptor in libbpf, from Andrii.

3) Fix libbpf_num_possible_cpus() to make it thread safe, from Takshak.

4) Fix bpftool to dump an error if pinning fails, from Jakub.

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 0a062ba725cdad3b167782179ee914a8402a0184:

  Merge tag 'mlx5-fixes-2019-07-25' of git://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux (2019-07-26 14:26:41 -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 4f7aafd78aeaf18a4f6dea9415df60e745c9dfa7:

  Merge branch 'bpf-bpftool-pinning-error-msg' (2019-08-09 17:38:53 +0200)

----------------------------------------------------------------
Alexei Starovoitov (2):
      bpf: fix x64 JIT code generation for jmp to 1st insn
      selftests/bpf: tests for jmp to 1st insn

Andrii Nakryiko (2):
      libbpf: fix erroneous multi-closing of BTF FD
      libbpf: set BTF FD for prog only when there is supported .BTF.ext data

Daniel Borkmann (1):
      Merge branch 'bpf-bpftool-pinning-error-msg'

Jakub Kicinski (2):
      tools: bpftool: fix error message (prog -> object)
      tools: bpftool: add error message on pin failure

Takshak Chahande (1):
      libbpf : make libbpf_num_possible_cpus function thread safe

 arch/x86/net/bpf_jit_comp.c                   |  9 ++++----
 tools/bpf/bpftool/common.c                    |  8 +++++--
 tools/lib/bpf/libbpf.c                        | 33 +++++++++++++++------------
 tools/testing/selftests/bpf/verifier/loops1.c | 28 +++++++++++++++++++++++
 4 files changed, 57 insertions(+), 21 deletions(-)

             reply	other threads:[~2019-08-11 19:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-11 19:58 Daniel Borkmann [this message]
2019-08-11 21:49 ` pull-request: bpf 2019-08-11 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=20190811195834.3430-1-daniel@iogearbox.net \
    --to=daniel@iogearbox.net \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=davem@davemloft.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