netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Borkmann <daniel@iogearbox.net>
To: davem@davemloft.net
Cc: jakub.kicinski@netronome.com, daniel@iogearbox.net,
	ast@kernel.org, netdev@vger.kernel.org, bpf@vger.kernel.org
Subject: pull-request: bpf 2019-11-02
Date: Sat,  2 Nov 2019 02:27:06 +0100	[thread overview]
Message-ID: <20191102012706.31533-1-daniel@iogearbox.net> (raw)

Hi David,

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

We've added 6 non-merge commits during the last 6 day(s) which contain
a total of 8 files changed, 35 insertions(+), 9 deletions(-).

The main changes are:

1) Fix ppc BPF JIT's tail call implementation by performing a second pass
   to gather a stable JIT context before opcode emission, from Eric Dumazet.

2) Fix build of BPF samples sys_perf_event_open() usage to compiled out
   unavailable test_attr__{enabled,open} checks. Also fix potential overflows
   in bpf_map_{area_alloc,charge_init} on 32 bit archs, from Björn Töpel.

3) Fix narrow loads of bpf_sysctl context fields with offset > 0 on big endian
   archs like s390x and also improve the test coverage, from Ilya Leoshkevich.

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:

Alexei Starovoitov, Andrey Ignatov, Andrii Nakryiko, Jakub Kicinski, KP 
Singh, Song Liu

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

The following changes since commit fc11078dd3514c65eabce166b8431a56d8a667cb:

  Merge git://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf (2019-10-27 12:13:16 -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 7de086909365cd60a5619a45af3f4152516fd75c:

  powerpc/bpf: Fix tail call implementation (2019-11-02 00:32:26 +0100)

----------------------------------------------------------------
Björn Töpel (3):
      perf tools: Make usage of test_attr__* optional for perf-sys.h
      samples/bpf: fix build by setting HAVE_ATTR_TEST to zero
      bpf: Change size to u64 for bpf_map_{area_alloc, charge_init}()

Daniel Borkmann (1):
      bpf, doc: Add Andrii as official reviewer to BPF subsystem

Eric Dumazet (1):
      powerpc/bpf: Fix tail call implementation

Ilya Leoshkevich (1):
      bpf: Allow narrow loads of bpf_sysctl fields with offset > 0

 MAINTAINERS                               |  1 +
 arch/powerpc/net/bpf_jit_comp64.c         | 13 +++++++++++++
 include/linux/bpf.h                       |  4 ++--
 kernel/bpf/cgroup.c                       |  4 ++--
 kernel/bpf/syscall.c                      |  7 +++++--
 samples/bpf/Makefile                      |  1 +
 tools/perf/perf-sys.h                     |  6 ++++--
 tools/testing/selftests/bpf/test_sysctl.c |  8 +++++++-
 8 files changed, 35 insertions(+), 9 deletions(-)

             reply	other threads:[~2019-11-02  1:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-02  1:27 Daniel Borkmann [this message]
2019-11-06  1:38 ` pull-request: bpf 2019-11-02 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=20191102012706.31533-1-daniel@iogearbox.net \
    --to=daniel@iogearbox.net \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=davem@davemloft.net \
    --cc=jakub.kicinski@netronome.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).