bpf.vger.kernel.org archive mirror
 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-05-18
Date: Sat, 18 May 2019 01:14:00 +0200	[thread overview]
Message-ID: <20190517231400.9315-1-daniel@iogearbox.net> (raw)

Hi David,

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

The main changes are:

1) Fix bpftool's raw BTF dump in relation to forward declarations of union/
   structs, and another fix to unexport logging helpers, from Andrii.

2) Fix inode permission check for retrieving bpf programs, from Chenbo.

3) Fix bpftool to raise rlimit earlier as otherwise libbpf's feature probing
   can fail and subsequently it refuses to load an object, from Yonghong.

4) Fix declaration of bpf_get_current_task() in kselftests, from Alexei.

5) Fix up BPF kselftest .gitignore to add generated files, from Stanislav.

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 2407a88a13a2d03ea9b8c86bbdedb3eff80c4b9e:

  Merge branch 'rhashtable-Fix-sparse-warnings' (2019-05-16 09:45:20 -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 9c3ddee1246411a3c9c39bfa5457e49579027f0c:

  bpftool: fix BTF raw dump of FWD's fwd_kind (2019-05-17 14:21:29 +0200)

----------------------------------------------------------------
Alexei Starovoitov (1):
      selftests/bpf: fix bpf_get_current_task

Andrii Nakryiko (2):
      libbpf: move logging helpers into libbpf_internal.h
      bpftool: fix BTF raw dump of FWD's fwd_kind

Chenbo Feng (1):
      bpf: relax inode permission check for retrieving bpf program

Stanislav Fomichev (1):
      selftests/bpf: add test_sysctl and map_tests/tests.h to .gitignore

Yonghong Song (1):
      tools/bpftool: move set_max_rlimit() before __bpf_object__open_xattr()

 kernel/bpf/inode.c                               |  2 +-
 tools/bpf/bpftool/btf.c                          |  4 ++--
 tools/bpf/bpftool/prog.c                         |  4 ++--
 tools/lib/bpf/btf.c                              |  2 +-
 tools/lib/bpf/libbpf.c                           |  1 -
 tools/lib/bpf/libbpf_internal.h                  | 13 +++++++++++++
 tools/lib/bpf/libbpf_util.h                      | 13 -------------
 tools/lib/bpf/xsk.c                              |  2 +-
 tools/testing/selftests/bpf/.gitignore           |  1 +
 tools/testing/selftests/bpf/bpf_helpers.h        |  2 +-
 tools/testing/selftests/bpf/map_tests/.gitignore |  1 +
 11 files changed, 23 insertions(+), 22 deletions(-)
 create mode 100644 tools/testing/selftests/bpf/map_tests/.gitignore

             reply	other threads:[~2019-05-17 23:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-17 23:14 Daniel Borkmann [this message]
2019-05-17 23:40 ` pull-request: bpf 2019-05-18 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=20190517231400.9315-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;
as well as URLs for NNTP newsgroup(s).