From: Martin KaFai Lau <martin.lau@linux.dev>
To: Amery Hung <ameryhung@gmail.com>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org,
alexei.starovoitov@gmail.com, andrii@kernel.org,
daniel@iogearbox.net, paul.chaignon@gmail.com, kuba@kernel.org,
stfomichev@gmail.com, martin.lau@kernel.org,
mohsin.bashr@gmail.com, noren@nvidia.com, dtatulea@nvidia.com,
saeedm@nvidia.com, tariqt@nvidia.com, mbloch@nvidia.com,
maciej.fijalkowski@intel.com, kernel-team@meta.com
Subject: Re: [PATCH bpf-next v3 5/6] selftests/bpf: Test bpf_xdp_pull_data
Date: Wed, 17 Sep 2025 10:54:46 -0700 [thread overview]
Message-ID: <28df67a9-528d-41e9-8441-722237b9add9@linux.dev> (raw)
In-Reply-To: <20250915224801.2961360-6-ameryhung@gmail.com>
On 9/15/25 3:48 PM, Amery Hung wrote:
> +/* Find sizes of struct skb_shared_info and struct xdp_frame so that
> + * we can calculate the maximum pull lengths for test cases
> + */
> +int find_xdp_sizes(struct test_xdp_pull_data *skel, int frame_sz)
static
> +{
> + LIBBPF_OPTS(bpf_test_run_opts, topts);
> + struct xdp_md ctx = {};
> + int prog_fd, err;
> + __u8 *buf;
> +
> + buf = calloc(frame_sz, sizeof(__u8));
buf is leaked.
> + if (!ASSERT_OK_PTR(buf, "calloc buf"))
> + return -ENOMEM;
> +
> + topts.data_in = buf;
> + topts.data_out = buf;
> + topts.data_size_in = frame_sz;
> + topts.data_size_out = frame_sz;
> + /* Pass a data_end larger than the linear space available to make sure
> + * bpf_prog_test_run_xdp() will fill the linear data area so that
> + * xdp_find_data_hard_end can infer the size of struct skb_shared_info
> + */
> + ctx.data_end = frame_sz;
> + topts.ctx_in = &ctx;
> + topts.ctx_out = &ctx;
> + topts.ctx_size_in = sizeof(ctx);
> + topts.ctx_size_out = sizeof(ctx);
> +
> + prog_fd = bpf_program__fd(skel->progs.xdp_find_sizes);
> + err = bpf_prog_test_run_opts(prog_fd, &topts);
> + ASSERT_OK(err, "bpf_prog_test_run_opts");
> +
> + return err;
> +}
> +
> +/* xdp_pull_data_prog will directly read a marker 0xbb stored at buf[1024]
> + * so caller expecting XDP_PASS should always pass pull_len no less than 1024
> + */
> +void run_test(struct test_xdp_pull_data *skel, int retval,
static
next prev parent reply other threads:[~2025-09-17 17:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 22:47 [PATCH bpf-next v3 0/6] Add kfunc bpf_xdp_pull_data Amery Hung
2025-09-15 22:47 ` [PATCH bpf-next v3 1/6] bpf: Allow bpf_xdp_shrink_data to shrink a frag from head and tail Amery Hung
2025-09-15 22:47 ` [PATCH bpf-next v3 2/6] bpf: Support pulling non-linear xdp data Amery Hung
2025-09-17 0:17 ` Jakub Kicinski
2025-09-17 19:37 ` Amery Hung
2025-09-15 22:47 ` [PATCH bpf-next v3 3/6] bpf: Clear packet pointers after changing packet data in kfuncs Amery Hung
2025-09-15 22:47 ` [PATCH bpf-next v3 4/6] bpf: Support specifying linear xdp packet data size for BPF_PROG_TEST_RUN Amery Hung
2025-09-16 22:59 ` Martin KaFai Lau
2025-09-17 17:23 ` Amery Hung
2025-09-15 22:48 ` [PATCH bpf-next v3 5/6] selftests/bpf: Test bpf_xdp_pull_data Amery Hung
2025-09-17 17:54 ` Martin KaFai Lau [this message]
2025-09-15 22:48 ` [PATCH bpf-next v3 6/6] selftests: drv-net: Pull data before parsing headers Amery Hung
2025-09-17 18:50 ` [PATCH bpf-next v3 0/6] Add kfunc bpf_xdp_pull_data Martin KaFai Lau
2025-09-17 21:22 ` Jakub Kicinski
2025-09-18 6:43 ` Nimrod Oren
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=28df67a9-528d-41e9-8441-722237b9add9@linux.dev \
--to=martin.lau@linux.dev \
--cc=alexei.starovoitov@gmail.com \
--cc=ameryhung@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dtatulea@nvidia.com \
--cc=kernel-team@meta.com \
--cc=kuba@kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=martin.lau@kernel.org \
--cc=mbloch@nvidia.com \
--cc=mohsin.bashr@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=noren@nvidia.com \
--cc=paul.chaignon@gmail.com \
--cc=saeedm@nvidia.com \
--cc=stfomichev@gmail.com \
--cc=tariqt@nvidia.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.