bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin KaFai Lau <kafai@fb.com>
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 4/4] selftests/bpf: Test updating flow_dissector link with same program
Date: Thu, 25 Jun 2020 22:52:24 -0700	[thread overview]
Message-ID: <20200626055224.ublxa7oxkpkhdwjp@kafai-mbp.dhcp.thefacebook.com> (raw)
In-Reply-To: <20200625141357.910330-5-jakub@cloudflare.com>

On Thu, Jun 25, 2020 at 04:13:57PM +0200, Jakub Sitnicki wrote:
> This case, while not particularly useful, is worth covering because we
> expect the operation to succeed as opposed when re-attaching the same
> program directly with PROG_ATTACH.
> 
> While at it, update the tests summary that fell out of sync when tests
> extended to cover links.
Acked-by: Martin KaFai Lau <kafai@fb.com>

      reply	other threads:[~2020-06-26  5:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-25 14:13 [PATCH bpf-next v3 0/4] bpf, netns: Prepare for multi-prog attachment Jakub Sitnicki
2020-06-25 14:13 ` [PATCH bpf-next v3 1/4] flow_dissector: Pull BPF program assignment up to bpf-netns Jakub Sitnicki
2020-06-26  1:38   ` Martin KaFai Lau
2020-06-25 14:13 ` [PATCH bpf-next v3 2/4] bpf, netns: Keep attached programs in bpf_prog_array Jakub Sitnicki
2020-06-25 20:50   ` Andrii Nakryiko
2020-06-26  9:45     ` Jakub Sitnicki
2020-06-26 22:13       ` Andrii Nakryiko
2020-06-26 22:15         ` Andrii Nakryiko
2020-06-26  5:41   ` Martin KaFai Lau
2020-06-26 10:40     ` Jakub Sitnicki
2020-06-25 14:13 ` [PATCH bpf-next v3 3/4] bpf, netns: Keep a list of attached bpf_link's Jakub Sitnicki
2020-06-26  5:43   ` Martin KaFai Lau
2020-06-25 14:13 ` [PATCH bpf-next v3 4/4] selftests/bpf: Test updating flow_dissector link with same program Jakub Sitnicki
2020-06-26  5:52   ` Martin KaFai Lau [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=20200626055224.ublxa7oxkpkhdwjp@kafai-mbp.dhcp.thefacebook.com \
    --to=kafai@fb.com \
    --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).