From: sashiko-bot@kernel.org
To: "Maciej Fijalkowski" <maciej.fijalkowski@intel.com>
Cc: bpf@vger.kernel.org
Subject: Re: [PATCH v2 net-next 10/14] selftests: xsk: add a hardware mode to xskxceiver
Date: Fri, 09 Oct 2026 11:50:05 +0000 [thread overview]
Message-ID: <sashiko-outbox-165426@kernel.org> (raw)
In-Reply-To: <20261008114909.734364-11-maciej.fijalkowski@intel.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] selftests/xsk: hardware ring software state out of sync on reset failure
--
commit b6f9e6a7023dfe76a4790e608f82c3aef2c3cf4a
Author: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
selftests: xsk: add a hardware mode to xskxceiver
This commit adds a hardware testing mode to the xskxceiver selftest, passing
physical interface parameters over UDP/IPv4. It also introduces an early
return optimization in hw_ring_size_reset to skip restoring hardware rings
if they are already at their default sizes.
> diff --git a/tools/testing/selftests/net/lib/xsk/test_xsk.c b/tools/testing/selftests/net/lib/xsk/test_xsk.c
> index 8d30c39c94c84..542c0579062a4 100644
> --- a/tools/testing/selftests/net/lib/xsk/test_xsk.c
> +++ b/tools/testing/selftests/net/lib/xsk/test_xsk.c
[ ... ]
> @@ -218,6 +291,10 @@ static int set_ring_size(struct ifobject *ifobj)
>
> int hw_ring_size_reset(struct ifobject *ifobj)
> {
> + if (ifobj->ring.tx_pending == ifobj->set_ring.default_tx &&
> + ifobj->ring.rx_pending == ifobj->set_ring.default_rx)
> + return 0;
> +
> ifobj->ring.tx_pending = ifobj->set_ring.default_tx;
> ifobj->ring.rx_pending = ifobj->set_ring.default_rx;
> return set_ring_size(ifobj);
[Severity: Medium]
Does this early-return optimization leave the software state out of sync if
the ioctl fails?
If set_ring_size() fails (for example, due to EBUSY), the underlying hardware
retains its previous, non-default ring size. However, because
ifobj->ring.tx_pending and ifobj->ring.rx_pending were updated optimistically
before the call, they are left permanently reflecting the default values.
With this newly added early return, subsequent attempts to call
hw_ring_size_reset() will read the corrupted software state and immediately
return 0 without attempting to retry the ioctl. Could this leave the network
interface with an incorrect ring size during test case cleanup?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261008114909.734364-1-maciej.fijalkowski@intel.com?part=10
next prev parent reply other threads:[~2026-10-09 11:50 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 11:48 [PATCH v2 net-next 00/14] selftests: net: migrate AF_XDP test suite over to net Maciej Fijalkowski
2026-10-08 11:48 ` [PATCH v2 net-next 01/14] selftests: xsk: factor endpoint work out of pthread wrappers Maciej Fijalkowski
2026-10-08 11:48 ` [PATCH v2 net-next 02/14] selftests: xsk: drop the single-interface loopback mode Maciej Fijalkowski
2026-10-09 9:46 ` Björn Töpel
2026-10-09 12:43 ` Maciej Fijalkowski
2026-10-08 11:48 ` [PATCH v2 net-next 03/14] selftests/bpf: drop the test_progs AF_XDP wrapper Maciej Fijalkowski
2026-10-08 11:48 ` [PATCH v2 net-next 04/14] selftests: net: add a generic rule for BPF skeletons Maciej Fijalkowski
2026-10-08 11:49 ` [PATCH v2 net-next 05/14] selftests: xsk: move the AF_XDP test suite to selftests/net Maciej Fijalkowski
2026-10-09 11:18 ` Björn Töpel
2026-10-09 12:46 ` Maciej Fijalkowski
2026-10-12 8:50 ` netdev-bot+sashiko
2026-10-08 11:49 ` [PATCH v2 net-next 06/14] selftests: xsk: collect interface capabilities in struct xsk_caps Maciej Fijalkowski
2026-10-08 11:49 ` [PATCH v2 net-next 07/14] selftests: xsk: split xskxceiver main() into setup, run and cleanup Maciej Fijalkowski
2026-10-12 8:50 ` netdev-bot+sashiko
2026-10-08 11:49 ` [PATCH v2 net-next 08/14] selftests: xsk: run one test case per xskxceiver invocation Maciej Fijalkowski
2026-10-09 11:25 ` Björn Töpel
2026-10-12 8:50 ` netdev-bot+sashiko
2026-10-08 11:49 ` [PATCH v2 net-next 09/14] selftests: xsk: run the RX and TX endpoints in separate processes Maciej Fijalkowski
2026-10-12 8:50 ` netdev-bot+sashiko
2026-10-08 11:49 ` [PATCH v2 net-next 10/14] selftests: xsk: add a hardware mode to xskxceiver Maciej Fijalkowski
2026-10-09 11:50 ` sashiko-bot [this message]
2026-10-12 8:50 ` netdev-bot+sashiko
2026-10-08 11:49 ` [PATCH v2 net-next 11/14] selftests: xsk: pass non-test traffic to the stack in hardware mode Maciej Fijalkowski
2026-10-12 8:50 ` netdev-bot+sashiko
2026-10-08 11:49 ` [PATCH v2 net-next 12/14] selftests: xsk: share test case definitions with hardware runner Maciej Fijalkowski
2026-10-09 12:12 ` Björn Töpel
2026-10-09 12:52 ` Maciej Fijalkowski
2026-10-08 11:49 ` [PATCH v2 net-next 13/14] selftests: drv-net: test AF_XDP zero-copy with an SKB peer Maciej Fijalkowski
2026-10-08 21:37 ` Jakub Kicinski
2026-10-09 13:13 ` Maciej Fijalkowski
2026-10-09 11:50 ` sashiko-bot
2026-10-12 8:50 ` netdev-bot+sashiko
2026-10-08 11:49 ` [PATCH v2 net-next 14/14] selftests: xsk: document generic and hardware endpoint runs Maciej Fijalkowski
2026-10-08 21:41 ` Jakub Kicinski
2026-10-12 8:50 ` netdev-bot+sashiko
2026-10-08 21:30 ` [PATCH v2 net-next 00/14] selftests: net: migrate AF_XDP test suite over to net Jakub Kicinski
2026-10-09 12:02 ` Björn Töpel
2026-10-09 13:15 ` Maciej Fijalkowski
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=sashiko-outbox-165426@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=maciej.fijalkowski@intel.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