BPF List
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Maciej Fijalkowski" <maciej.fijalkowski@intel.com>
Cc: bpf@vger.kernel.org
Subject: Re: [PATCH v3 net 5/6] selftests/xsk: fix too-many-frags multi-buffer Tx test
Date: Wed, 15 Jul 2026 14:08:46 +0000	[thread overview]
Message-ID: <20260715140846.70A2C1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260714140722.111645-6-maciej.fijalkowski@intel.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] A newly added multi-line comment uses the deprecated kernel style where text is placed on the same line as the opening `/*`.
--

--- Patch [5]: [PATCH v3 net 5/6] selftests/xsk: fix too-many-frags multi-buffer Tx test ---
commit 41dfcc558e2b05136aed2feb3d3534323946fd99
Author: Maciej Fijalkowski <maciej.fijalkowski@intel.com>

selftests/xsk: fix too-many-frags multi-buffer Tx test

This commit updates the too-many-frags test to keep oversized Tx descriptors
valid so they can be accounted and reclaimed, while marking the corresponding
Rx packet invalid. It also adds a synchronization packet to verify the Tx
path recovers at the next packet boundary.

> diff --git a/tools/testing/selftests/bpf/prog_tests/test_xsk.c b/tools/testing/selftests/bpf/prog_tests/test_xsk.c
> index 6eb9096d084c0..de17dd48f1764 100644
> --- a/tools/testing/selftests/bpf/prog_tests/test_xsk.c
> +++ b/tools/testing/selftests/bpf/prog_tests/test_xsk.c
[ ... ]
> @@ -2288,24 +2288,30 @@ int testapp_too_many_frags(struct test_spec *test)
[ ... ]
>  	if (pkt_stream_generate_custom(test, pkts, 2 * max_frags + 3)) {
>  		free(pkts);
>  		return TEST_FAILURE;
>  	}
>  
> +	/* The generated Tx stream must keep the too-big packet valid so that
> +	 * __send_pkts() accounts its descriptors in outstanding_tx. The Rx
> +	 * stream, however, must not expect this packet on the wire.
> +	 */

[Severity: Low]
This isn't a bug, but could this multi-line comment be formatted to match
the preferred BPF subsystem style?

The BPF guidelines specify that multi-line comments should have the opening
/* on its own line, rather than having the comment text start on the same
line.

> +	test->ifobj_rx->xsk->pkt_stream->pkts[2].valid = false;
> +	test->ifobj_rx->xsk->pkt_stream->nb_valid_entries--;
>  
>  	ret = testapp_validate_traffic(test);
>  	free(pkts);
>  	return ret;

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260714140722.111645-1-maciej.fijalkowski@intel.com?part=5

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

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-14 14:07 [PATCH v3 net 0/6] xsk: fix AF_XDP multi-buffer Tx descriptor reclaim Maciej Fijalkowski
2026-07-14 14:07 ` [PATCH v3 net 1/6] xsk: fix buffer leak in xsk_drop_skb() for AF_XDP multi-buffer Tx Maciej Fijalkowski
2026-07-16 11:22   ` Jason Xing
2026-07-16 11:25     ` Maciej Fijalkowski
2026-07-16 11:42       ` Jason Xing
2026-07-16 11:52         ` Maciej Fijalkowski
2026-07-16 12:15           ` Jason Xing
2026-07-14 14:07 ` [PATCH v3 net 2/6] xsk: drain continuation descs after overflow in xsk_build_skb() Maciej Fijalkowski
2026-07-14 14:07 ` [PATCH v3 net 3/6] xsk: provide sufficient space in pool->tx_descs Maciej Fijalkowski
2026-07-15 14:08   ` sashiko-bot
2026-07-15 18:59     ` Maciej Fijalkowski
2026-07-16  9:29   ` Jason Xing
2026-07-16 10:47     ` Maciej Fijalkowski
2026-07-16 10:56       ` Jason Xing
2026-07-14 14:07 ` [PATCH v3 net 4/6] xsk: reclaim invalid multi-buffer Tx descs in ZC path Maciej Fijalkowski
2026-07-15 14:08   ` sashiko-bot
2026-07-15 19:03     ` Maciej Fijalkowski
2026-07-16 21:58   ` Jason Xing
2026-07-14 14:07 ` [PATCH v3 net 5/6] selftests/xsk: fix too-many-frags multi-buffer Tx test Maciej Fijalkowski
2026-07-15 14:08   ` sashiko-bot [this message]
2026-07-14 14:07 ` [PATCH v3 net 6/6] selftests/xsk: account invalid multi-buffer Tx descriptors Maciej Fijalkowski
2026-07-15 19:06 ` [PATCH v3 net 0/6] xsk: fix AF_XDP multi-buffer Tx descriptor reclaim Maciej Fijalkowski
2026-07-15 19:47   ` Jason Xing

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=20260715140846.70A2C1F000E9@smtp.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