From: Daniel Borkmann <daniel@iogearbox.net>
To: davem@davemloft.net
Cc: alexei.starovoitov@gmail.com, jannh@google.com,
netdev@vger.kernel.org, Daniel Borkmann <daniel@iogearbox.net>
Subject: [PATCH net-next 0/2] Further robustify putting BPF progs
Date: Thu, 30 Jun 2016 17:24:42 +0200 [thread overview]
Message-ID: <cover.1467298256.git.daniel@iogearbox.net> (raw)
This series addresses a potential issue reported to us by Jann Horn
with regards to putting progs. First patch moves progs generally under
RCU destruction and second patch refactors getting of progs to simplify
code a bit. For details, please see individual patches. Note, we think
that addressing this one in net-next should be sufficient.
Thanks!
Daniel Borkmann (2):
bpf: generally move prog destruction to RCU deferral
bpf: refactor bpf_prog_get and type check into helper
include/linux/bpf.h | 8 +++++---
kernel/bpf/arraymap.c | 4 +---
kernel/bpf/syscall.c | 40 ++++++++++++++++++++++------------------
kernel/events/core.c | 2 +-
net/core/filter.c | 13 +------------
net/kcm/kcmsock.c | 8 +-------
net/packet/af_packet.c | 6 +-----
net/sched/act_bpf.c | 7 +------
net/sched/cls_bpf.c | 7 +------
9 files changed, 34 insertions(+), 61 deletions(-)
--
1.9.3
next reply other threads:[~2016-06-30 15:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 15:24 Daniel Borkmann [this message]
2016-06-30 15:24 ` [PATCH net-next 1/2] bpf: generally move prog destruction to RCU deferral Daniel Borkmann
2016-06-30 15:24 ` [PATCH net-next 2/2] bpf: refactor bpf_prog_get and type check into helper Daniel Borkmann
2016-07-01 20:05 ` [PATCH net-next 0/2] Further robustify putting BPF progs 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.1467298256.git.daniel@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=alexei.starovoitov@gmail.com \
--cc=davem@davemloft.net \
--cc=jannh@google.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).