BPF List
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "David Windsor" <dwindsor@gmail.com>
Cc: bpf@vger.kernel.org
Subject: Re: [PATCH bpf 2/2] selftests/bpf: Add XDP dispatcher FineIBT regression test
Date: Wed, 08 Jul 2026 03:08:58 +0000	[thread overview]
Message-ID: <20260708030859.10F8E1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <f6df1bf381517f7ff6927d82de7680e7826adf94.1783479101.git.dwindsor@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The test modifies global host networking state by attaching an XDP program to the loopback interface, but is not serialized or isolated in a network namespace, causing race conditions in concurrent CI test runs.
--

--- Patch [2]: [PATCH bpf 2/2] selftests/bpf: Add XDP dispatcher FineIBT regression test ---
commit 5a870a8bf864ee8b6c4ae366f0fe61e22b615aee
Author: David Windsor <dwindsor@gmail.com>
selftests/bpf: Add XDP dispatcher FineIBT regression test

This commit adds a regression test for the x86 BPF dispatcher's indirect-jump
fallback under FineIBT.

> diff --git a/tools/testing/selftests/bpf/prog_tests/xdp_dispatcher_fineibt.c b/tools/testing/selftests/bpf/prog_tests/xdp_dispatcher_fineibt.c
> new file mode 100644
> index 0000000000000..2d3fc4034eb90
> --- /dev/null
> +++ b/tools/testing/selftests/bpf/prog_tests/xdp_dispatcher_fineibt.c

[ ... ]

> +#define IFINDEX_LO		1
> +
> +void test_xdp_dispatcher_fineibt(void)
> +{

[ ... ]

> +	attached_fd = bpf_program__fd(skel->progs.xdp_dispatcher_attached);
> +	unattached_fd = bpf_program__fd(skel->progs.xdp_dispatcher_unattached);
> +
> +	err = bpf_xdp_attach(IFINDEX_LO, attached_fd, XDP_FLAGS_SKB_MODE, NULL);

[Severity: Medium]
Since this test modifies the global loopback interface by attaching an XDP
program, and lacks the serial_test_ prefix or network namespace isolation,
could this cause flaky failures in other concurrently running tests?

By BPF selftests convention, shouldn't tests that modify global networking
state either be isolated in a dedicated network namespace or use the
serial_test_ prefix to guarantee sequential execution?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/c5a6bff16c0885d3ec756a1cdfb623636d0bdb4a.1783479101.git.dwindsor@gmail.com?part=2

  reply	other threads:[~2026-07-08  3:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-08  2:57 [PATCH bpf 1/2] bpf, x86: Fix FineIBT #CP in BPF dispatcher's indirect-jump fallback David Windsor
2026-07-08  2:57 ` [PATCH bpf 2/2] selftests/bpf: Add XDP dispatcher FineIBT regression test David Windsor
2026-07-08  3:08   ` sashiko-bot [this message]
2026-07-08  3:22   ` Leon Hwang
2026-07-08  3:30 ` [PATCH bpf 1/2] bpf, x86: Fix FineIBT #CP in BPF dispatcher's indirect-jump fallback Leon Hwang
2026-07-08  3:40   ` David Windsor

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=20260708030859.10F8E1F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=dwindsor@gmail.com \
    --cc=sashiko-reviews@lists.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