From: Daniel Borkmann <daniel@iogearbox.net>
To: davem@davemloft.net
Cc: daniel@iogearbox.net, ast@kernel.org, netdev@vger.kernel.org
Subject: pull-request: bpf 2018-08-05
Date: Sun, 5 Aug 2018 02:26:11 +0200 [thread overview]
Message-ID: <20180805002611.19611-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 percpu_array dump by using correct roundup to next
multiple of 8 for the value size, from Yonghong.
2) Fix in AF_XDP's __xsk_rcv_zc() to not returning frames back to
allocator since driver will recycle frame anyway in case of an
error, from Jakub.
3) Fix up BPF test_lwt_seg6local test cases to final iproute2
syntax, from Mathieu.
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 61f4b23769f0cc72ae62c9a81cf08f0397d40da8:
netlink: Don't shift with UB on nlk->ngroups (2018-07-30 12:42:22 -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 8c85cbdf371f9ddf256ecc5d9548b26ee8fcfe2f:
selftests/bpf: update test_lwt_seg6local.sh according to iproute2 (2018-08-03 10:19:33 +0200)
----------------------------------------------------------------
Jakub Kicinski (1):
net: xsk: don't return frames via the allocator on error
Mathieu Xhonneux (1):
selftests/bpf: update test_lwt_seg6local.sh according to iproute2
Yonghong Song (1):
tools/bpftool: fix a percpu_array map dump problem
net/xdp/xsk.c | 4 +---
tools/bpf/bpftool/map.c | 14 +++++++++-----
tools/testing/selftests/bpf/test_lwt_seg6local.sh | 6 +++---
3 files changed, 13 insertions(+), 11 deletions(-)
next reply other threads:[~2018-08-05 2:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-05 0:26 Daniel Borkmann [this message]
2018-08-05 0:53 ` pull-request: bpf 2018-08-05 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=20180805002611.19611-1-daniel@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ast@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