From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Marcus Wichelmann <marcus.wichelmann@hetzner-cloud.de>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
bpf@vger.kernel.org, linux-kselftest@vger.kernel.org
Cc: willemdebruijn.kernel@gmail.com, jasowang@redhat.com,
andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
andrii@kernel.org, eddyz87@gmail.com, mykolal@fb.com,
ast@kernel.org, daniel@iogearbox.net, martin.lau@linux.dev,
song@kernel.org, yonghong.song@linux.dev,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@fomichev.me,
haoluo@google.com, jolsa@kernel.org, shuah@kernel.org,
hawk@kernel.org, marcus.wichelmann@hetzner-cloud.de
Subject: Re: [PATCH bpf-next v3 4/6] selftests/bpf: refactor xdp_context_functional test and bpf program
Date: Tue, 25 Feb 2025 13:32:12 -0500 [thread overview]
Message-ID: <67be0cac4d366_25ccfc294e8@willemb.c.googlers.com.notmuch> (raw)
In-Reply-To: <20250224152909.3911544-5-marcus.wichelmann@hetzner-cloud.de>
Marcus Wichelmann wrote:
> The existing XDP metadata test works by creating a veth pair and
> attaching XDP & TC programs that drop the packet when the condition of
> the test isn't fulfilled. The test then pings through the veth pair and
> succeeds when the ping comes through.
>
> While this test works great for a veth pair, it is hard to replicate for
> tap devices to test the XDP metadata support of them. A similar test for
> the tun driver would either involve logic to reply to the ping request,
> or would have to capture the packet to check if it was dropped or not.
>
> To make the testing of other drivers easier while still maximizing code
> reuse, this commit refactors the existing xdp_context_functional test to
> use a test_result map. Instead of conditionally passing or dropping the
> packet, the TC program is changed to copy the received metadata into the
> value of that single-entry array map. Tests can then verify that the map
> value matches the expectation.
>
> This testing logic is easy to adapt to other network drivers as the only
> remaining requirement is that there is some way to send a custom
> Ethernet packet through it that triggers the XDP & TC programs.
>
> The payload of the Ethernet packet is used as the test data that is
> expected to be passed as metadata from the XDP to the TC program and
> written to the map. It has a fixed size of 32 bytes which is a
> reasonalbe size that should be supported by both drivers. Additional
> packet headers are not necessary for the test and were therefore skipped
> to keep the testing code short.
>
> Signed-off-by: Marcus Wichelmann <marcus.wichelmann@hetzner-cloud.de>
> - SYS(close, "ip addr add " RX_ADDR "/24 dev " RX_NAME);
Why remove the Rx and Tx addresses?
> + /* By default, Linux sends IPv6 multicast listener reports which
> + * interfere with this test. Set the IFF_NOARP flag to ensure
> + * silence on the interface.
> + */
> + SYS(close, "ip link set dev " RX_NAME " arp off");
> SYS(close, "ip link set dev " RX_NAME " up");
>
> skel = test_xdp_meta__open_and_load();
> @@ -154,21 +215,12 @@ void test_xdp_context_functional(void)
> if (!ASSERT_OK(ret, "bpf_tc_hook_create"))
> goto close;
>
> - tc_prog = bpf_object__find_program_by_name(skel->obj, "ing_cls");
> - if (!ASSERT_OK_PTR(tc_prog, "open ing_cls prog"))
> - goto close;
> -
> - tc_opts.prog_fd = bpf_program__fd(tc_prog);
> + tc_opts.prog_fd = bpf_program__fd(skel->progs.ing_cls);
This refactor seems irrelevant to the goal of this patch? Same below.
> ret = bpf_tc_attach(&tc_hook, &tc_opts);
> if (!ASSERT_OK(ret, "bpf_tc_attach"))
> goto close;
>
> - xdp_prog = bpf_object__find_program_by_name(skel->obj, "ing_xdp");
> - if (!ASSERT_OK_PTR(xdp_prog, "open ing_xdp prog"))
> - goto close;
> -
> - ret = bpf_xdp_attach(rx_ifindex,
> - bpf_program__fd(xdp_prog),
> + ret = bpf_xdp_attach(rx_ifindex, bpf_program__fd(skel->progs.ing_xdp),
> 0, NULL);
> if (!ASSERT_GE(ret, 0, "bpf_xdp_attach"))
> goto close;
> @@ -179,9 +231,18 @@ void test_xdp_context_functional(void)
> if (!ASSERT_OK_PTR(nstoken, "setns tx_ns"))
> goto close;
>
> - SYS(close, "ip addr add " TX_ADDR "/24 dev " TX_NAME);
> + SYS(close, "ip link set dev " TX_NAME " arp off");
> SYS(close, "ip link set dev " TX_NAME " up");
> SEC("tc")
> int ing_cls(struct __sk_buff *ctx)
> {
> - __u8 *data, *data_meta, *data_end;
> - __u32 diff = 0;
> + void *data_meta = (void *)(unsigned long)ctx->data_meta;
> + void *data = (void *)(unsigned long)ctx->data;
>
> - data_meta = ctx_ptr(ctx, data_meta);
> - data_end = ctx_ptr(ctx, data_end);
> - data = ctx_ptr(ctx, data);
Similarly: why these changes?
In general, please minimize your patch to the core purpose. Avoid
including "cleanups" or other such refactors. Or justify the choice
explicitly in the commit message.
> -
> - if (data + ETH_ALEN > data_end ||
> - data_meta + round_up(ETH_ALEN, 4) > data)
> + if (data_meta + META_SIZE > data)
> return TC_ACT_SHOT;
>
> - diff |= ((__u32 *)data_meta)[0] ^ ((__u32 *)data)[0];
> - diff |= ((__u16 *)data_meta)[2] ^ ((__u16 *)data)[2];
> + int key = 0;
> +
> + bpf_map_update_elem(&test_result, &key, data_meta, BPF_ANY);
>
> - return diff ? TC_ACT_SHOT : TC_ACT_OK;
> + return TC_ACT_SHOT;
> }
>
> SEC("xdp")
> int ing_xdp(struct xdp_md *ctx)
> {
> - __u8 *data, *data_meta, *data_end;
> - int ret;
> -
> - ret = bpf_xdp_adjust_meta(ctx, -round_up(ETH_ALEN, 4));
> + int ret = bpf_xdp_adjust_meta(ctx, -META_SIZE);
> if (ret < 0)
> return XDP_DROP;
>
> - data_meta = ctx_ptr(ctx, data_meta);
> - data_end = ctx_ptr(ctx, data_end);
> - data = ctx_ptr(ctx, data);
> + void *data_meta = (void *)(unsigned long)ctx->data_meta;
> + void *data = (void *)(unsigned long)ctx->data;
> + void *data_end = (void *)(unsigned long)ctx->data_end;
>
> - if (data + ETH_ALEN > data_end ||
> - data_meta + round_up(ETH_ALEN, 4) > data)
> + void *payload = data + sizeof(struct ethhdr);
> +
> + if (data_meta + META_SIZE > data || payload + META_SIZE > data_end)
> return XDP_DROP;
>
> - __builtin_memcpy(data_meta, data, ETH_ALEN);
> + __builtin_memcpy(data_meta, payload, META_SIZE);
> +
> return XDP_PASS;
> }
>
> --
> 2.43.0
>
next prev parent reply other threads:[~2025-02-25 18:32 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 15:29 [PATCH bpf-next v3 0/6] XDP metadata support for tun driver Marcus Wichelmann
2025-02-24 15:29 ` [PATCH bpf-next v3 1/6] net: tun: enable XDP metadata support Marcus Wichelmann
2025-02-26 5:50 ` Jason Wang
2025-02-24 15:29 ` [PATCH bpf-next v3 2/6] net: tun: enable transfer of XDP metadata to skb Marcus Wichelmann
2025-02-25 18:26 ` Willem de Bruijn
2025-02-26 5:59 ` Jason Wang
2025-02-24 15:29 ` [PATCH bpf-next v3 3/6] selftests/bpf: move open_tuntap to network helpers Marcus Wichelmann
2025-02-25 18:24 ` Willem de Bruijn
2025-02-26 6:31 ` Jason Wang
2025-02-24 15:29 ` [PATCH bpf-next v3 4/6] selftests/bpf: refactor xdp_context_functional test and bpf program Marcus Wichelmann
2025-02-24 17:12 ` Stanislav Fomichev
2025-02-26 15:56 ` Marcus Wichelmann
2025-02-25 15:07 ` Marcus Wichelmann
2025-02-25 18:23 ` Willem de Bruijn
2025-02-26 17:39 ` Marcus Wichelmann
2025-02-25 18:32 ` Willem de Bruijn [this message]
2025-02-26 17:14 ` Marcus Wichelmann
2025-02-24 15:29 ` [PATCH bpf-next v3 5/6] selftests/bpf: add test for XDP metadata support in tun driver Marcus Wichelmann
2025-02-24 17:14 ` Stanislav Fomichev
2025-02-26 18:50 ` Marcus Wichelmann
2025-02-26 19:00 ` Stanislav Fomichev
2025-02-26 19:29 ` Marcus Wichelmann
2025-02-24 15:29 ` [PATCH bpf-next v3 6/6] selftests/bpf: fix file descriptor assertion in open_tuntap helper Marcus Wichelmann
2025-02-25 18:24 ` Willem de Bruijn
2025-02-25 14:55 ` [PATCH bpf-next v3 0/6] XDP metadata support for tun driver Willem de Bruijn
2025-02-25 15:03 ` Marcus Wichelmann
2025-02-25 18:14 ` Willem de Bruijn
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=67be0cac4d366_25ccfc294e8@willemb.c.googlers.com.notmuch \
--to=willemdebruijn.kernel@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=eddyz87@gmail.com \
--cc=edumazet@google.com \
--cc=haoluo@google.com \
--cc=hawk@kernel.org \
--cc=jasowang@redhat.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=marcus.wichelmann@hetzner-cloud.de \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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).