BPF List
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Tianyi Chen" <hi@tychen.cc>, bpf@vger.kernel.org
Subject: Re: [PATCH bpf 2/2] selftests/bpf: Cover RHASH batch cursor loss
Date: Sat, 07 Nov 2026 13:22:28 +0000	[thread overview]
Message-ID: <sashiko-outbox-202908@kernel.org> (raw)
In-Reply-To: <4b4cccc3b706a54ef42ba3c09b40954883661e6a.1794056839.git.hi@tychen.cc>

Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] selftests/bpf: standalone rhash_batch.c file instead of
  extending rhash.c
--

commit bf9586f48a54e730e2740cce0745ca08b2ddac63
Author: Tianyi Chen <hi@tychen.cc>

selftests/bpf: Cover RHASH batch cursor loss

This commit adds BPF selftests covering normal completion, missing input
cursors, and concurrent deletions for BPF_MAP_TYPE_RHASH batch lookup and
lookup-and-delete operations.

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

[ ... ]

> +void test_rhash_batch(void)
> +{
> +	if (test__start_subtest("lookup"))
> +		test_batch(false, false);
> +	if (test__start_subtest("lookup_delete"))
> +		test_batch(true, false);
> +	if (test__start_subtest("lost_lookup_cursor"))
> +		test_batch(false, true);
> +	if (test__start_subtest("lost_delete_cursor"))
> +		test_batch(true, true);
> +	if (test__start_subtest("concurrent_delete"))
> +		test_concurrent_delete();
> +}

[Severity: Low]
This isn't a bug, but could these subtests be added to test_rhash() in
tools/testing/selftests/bpf/prog_tests/rhash.c instead of introducing a
separate file?  rhash.c already houses userspace map syscall and iteration
subtests for BPF_MAP_TYPE_RHASH, and rhash_batch.c does not load a separate
BPF program skeleton.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1794056839.git.hi@tychen.cc?part=2

      reply	other threads:[~2026-11-07 13:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-07 13:11 [PATCH bpf 0/2] bpf: Fix RHASH batch cursor loss Tianyi Chen
2026-11-07 13:11 ` [PATCH bpf 1/2] bpf: Report lost RHASH batch traversal keys as EAGAIN Tianyi Chen
2026-11-09 18:53   ` Mykyta Yatsenko
2026-11-07 13:11 ` [PATCH bpf 2/2] selftests/bpf: Cover RHASH batch cursor loss Tianyi Chen
2026-11-07 13:22   ` sashiko-bot [this message]

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-202908@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=hi@tychen.cc \
    --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