netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Borkmann <daniel@iogearbox.net>
To: Jakub Sitnicki <jakub@cloudflare.com>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org, kernel-team@cloudflare.com
Subject: Re: [PATCH bpf-next v3 0/2] Atomic flow dissector updates
Date: Fri, 11 Oct 2019 23:24:44 +0200	[thread overview]
Message-ID: <20191011212444.GB21131@pc-63.home> (raw)
In-Reply-To: <20191011082946.22695-1-jakub@cloudflare.com>

On Fri, Oct 11, 2019 at 10:29:44AM +0200, Jakub Sitnicki wrote:
> This patch set changes how bpf(BPF_PROG_ATTACH) operates on flow dissector
> hook when there is already a program attached. After this change the user
> is allowed to update the program in a single syscall. Please see the first
> patch for rationale.

Applied, thanks!

      parent reply	other threads:[~2019-10-11 21:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-11  8:29 [PATCH bpf-next v3 0/2] Atomic flow dissector updates Jakub Sitnicki
2019-10-11  8:29 ` [PATCH bpf-next v3 1/2] flow_dissector: Allow updating the flow dissector program atomically Jakub Sitnicki
2019-10-11  8:29 ` [PATCH bpf-next v3 2/2] selftests/bpf: Check that flow dissector can be re-attached Jakub Sitnicki
2019-10-11 21:24 ` Daniel Borkmann [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=20191011212444.GB21131@pc-63.home \
    --to=daniel@iogearbox.net \
    --cc=bpf@vger.kernel.org \
    --cc=jakub@cloudflare.com \
    --cc=kernel-team@cloudflare.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).