From: David Miller <davem@davemloft.net>
To: daniel@iogearbox.net
Cc: alexei.starovoitov@gmail.com, jannh@google.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] Further robustify putting BPF progs
Date: Fri, 01 Jul 2016 16:05:17 -0400 (EDT) [thread overview]
Message-ID: <20160701.160517.1883958453142988302.davem@davemloft.net> (raw)
In-Reply-To: <cover.1467298256.git.daniel@iogearbox.net>
From: Daniel Borkmann <daniel@iogearbox.net>
Date: Thu, 30 Jun 2016 17:24:42 +0200
> 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.
Series applied, thanks Daniel.
prev parent reply other threads:[~2016-07-01 20:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 15:24 [PATCH net-next 0/2] Further robustify putting BPF progs Daniel Borkmann
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 ` David Miller [this message]
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=20160701.160517.1883958453142988302.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexei.starovoitov@gmail.com \
--cc=daniel@iogearbox.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).