BPF List
 help / color / mirror / Atom feed
From: Tianyi Chen <diannaaav@gmail.com>
To: sashiko-reviews@lists.linux.dev
Cc: bpf@vger.kernel.org
Subject: Re: [PATCH bpf v3] selftests/bpf: Check returned keys in map batch validators
Date: Fri, 11 Sep 2026 11:03:14 +0800	[thread overview]
Message-ID: <20260911030314.195110-1-diannaaav@gmail.com> (raw)
In-Reply-To: <20260911025713.AB5891F000FF@smtp.kernel.org>

These files run under test_maps, not test_progs. They include test_maps.h,
whose CHECK() reports the failure and calls exit(-1). That header does
not provide ASSERT_*(). The suggested ASSERT_GE/LT/LE helpers are defined
in test_progs.h and depend on that runner's failure reporting.

The distinction matters for these range checks: execution must stop
before indexing visited with an invalid returned key. ASSERT_*() returns
a boolean and does not itself stop the caller, so a mechanical replacement
would not preserve that behavior, even after resolving the runner/header
dependencies.

I am retaining CHECK() for this targeted test_maps correctness fix.
Migrating these tests to the test_progs assertion framework would be a
separate change requiring compatible failure reporting and control flow.
The current v3 passed test_maps with no skips on the rebuilt bpf/master
kernel (7.3.0-rc2).

Thanks,
Tianyi

  reply	other threads:[~2026-09-11  3:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-11  2:50 [PATCH bpf v3] selftests/bpf: Check returned keys in map batch validators Tianyi Chen
2026-09-11  2:57 ` sashiko-bot
2026-09-11  3:03   ` Tianyi Chen [this message]
     [not found] ` <fd1233fd7c263a4150672e1af33aaea82d625f727ead53cb681ae69bce1e6322@mail.kernel.org>
2026-09-11 11:57   ` Tianyi Chen

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=20260911030314.195110-1-diannaaav@gmail.com \
    --to=diannaaav@gmail.com \
    --cc=bpf@vger.kernel.org \
    --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