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/3] Minor BPF cleanups and digest
Date: Sun,  4 Dec 2016 23:19:38 +0100	[thread overview]
Message-ID: <cover.1480889473.git.daniel@iogearbox.net> (raw)

First two patches are minor cleanups, and the third one adds
a prog digest. For details, please see individual patches.
After this one, I have a set with tracepoint support that makes
use of this facility as well.

Thanks!

Daniel Borkmann (3):
  bpf: remove type arg from __is_valid_{,xdp_}access
  bpf, cls: consolidate prog deletion path
  bpf: add prog_digest and expose it via fdinfo/netlink

 include/linux/bpf.h                |  1 +
 include/linux/filter.h             |  7 +++-
 include/uapi/linux/pkt_cls.h       |  1 +
 include/uapi/linux/tc_act/tc_bpf.h |  1 +
 kernel/bpf/core.c                  | 65 ++++++++++++++++++++++++++++++++++++++
 kernel/bpf/syscall.c               | 24 +++++++++++++-
 kernel/bpf/verifier.c              |  2 ++
 net/core/filter.c                  | 15 ++++-----
 net/sched/act_bpf.c                |  9 ++++++
 net/sched/cls_bpf.c                | 38 ++++++++++++----------
 10 files changed, 135 insertions(+), 28 deletions(-)

-- 
1.9.3

             reply	other threads:[~2016-12-04 22:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-04 22:19 Daniel Borkmann [this message]
2016-12-04 22:19 ` [PATCH net-next 1/3] bpf: remove type arg from __is_valid_{,xdp_}access Daniel Borkmann
2016-12-04 22:19 ` [PATCH net-next 2/3] bpf, cls: consolidate prog deletion path Daniel Borkmann
2016-12-04 22:19 ` [PATCH net-next 3/3] bpf: add prog_digest and expose it via fdinfo/netlink Daniel Borkmann
2016-12-05 20:33 ` [PATCH net-next 0/3] Minor BPF cleanups and digest 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.1480889473.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).