netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Borkmann <daniel@iogearbox.net>
To: davem@davemloft.net
Cc: alexei.starovoitov@gmail.com, netdev@vger.kernel.org,
	Daniel Borkmann <daniel@iogearbox.net>
Subject: [PATCH net-next 0/6] BPF cleanups and misc updates
Date: Sat, 26 Nov 2016 01:28:03 +0100	[thread overview]
Message-ID: <cover.1480119395.git.daniel@iogearbox.net> (raw)

This patch set adds couple of cleanups in first few patches,
exposes owner_prog_type for array maps as well as mlocked mem
for maps in fdinfo, allows for mount permissions in fs and
fixes various outstanding issues in selftests and samples.

Thanks!

Daniel Borkmann (6):
  bpf: drop unnecessary context cast from BPF_PROG_RUN
  bpf: drop useless bpf_fd member from cls/act
  bpf: reuse dev_is_mac_header_xmit for redirect
  bpf: add owner_prog_type and accounted mem to array map's fdinfo
  bpf: allow for mount options to specify permissions
  bpf: fix multiple issues in selftest suite and samples

 .../net/ethernet/netronome/nfp/nfp_net_common.c    |  2 +-
 include/linux/filter.h                             |  6 +--
 include/linux/if_arp.h                             | 16 +++++++
 kernel/bpf/inode.c                                 | 54 +++++++++++++++++++++-
 kernel/bpf/syscall.c                               | 17 ++++++-
 kernel/events/core.c                               |  2 +-
 kernel/seccomp.c                                   |  2 +-
 net/core/filter.c                                  | 14 ++----
 net/sched/act_bpf.c                                |  7 ---
 net/sched/act_mirred.c                             | 15 +-----
 net/sched/cls_bpf.c                                |  9 +---
 samples/bpf/Makefile                               |  1 +
 samples/bpf/test_lru_dist.c                        |  5 +-
 samples/bpf/tracex2_user.c                         |  4 +-
 samples/bpf/tracex3_user.c                         |  6 ++-
 samples/bpf/xdp1_user.c                            |  4 +-
 tools/testing/selftests/bpf/bpf_util.h             | 38 +++++++++++++++
 tools/testing/selftests/bpf/test_lru_map.c         |  8 +++-
 tools/testing/selftests/bpf/test_maps.c            |  7 +--
 tools/testing/selftests/bpf/test_verifier.c        |  2 +-
 20 files changed, 160 insertions(+), 59 deletions(-)
 create mode 100644 tools/testing/selftests/bpf/bpf_util.h

-- 
1.9.3

             reply	other threads:[~2016-11-26  0:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-26  0:28 Daniel Borkmann [this message]
2016-11-26  0:28 ` [PATCH net-next 1/6] bpf: drop unnecessary context cast from BPF_PROG_RUN Daniel Borkmann
2016-11-26  0:28 ` [PATCH net-next 2/6] bpf: drop useless bpf_fd member from cls/act Daniel Borkmann
2016-11-26  0:28 ` [PATCH net-next 3/6] bpf: reuse dev_is_mac_header_xmit for redirect Daniel Borkmann
2016-11-26  0:28 ` [PATCH net-next 4/6] bpf: add owner_prog_type and accounted mem to array map's fdinfo Daniel Borkmann
2016-11-26  0:28 ` [PATCH net-next 5/6] bpf: allow for mount options to specify permissions Daniel Borkmann
2016-11-26  0:28 ` [PATCH net-next 6/6] bpf: fix multiple issues in selftest suite and samples Daniel Borkmann
2016-11-28  1:39 ` [PATCH net-next 0/6] BPF cleanups and misc updates 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=cover.1480119395.git.daniel@iogearbox.net \
    --to=daniel@iogearbox.net \
    --cc=alexei.starovoitov@gmail.com \
    --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).