All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vineet Gupta <vineet.gupta@linux.dev>
To: bpf@vger.kernel.org
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	yonghong.song@linux.dev, Vineet Gupta <vineet.gupta@linux.dev>
Subject: [PATCH bpf-next v2 0/4] selftest related fixes
Date: Fri,  7 Aug 2026 13:44:30 -0700	[thread overview]
Message-ID: <20260807204434.1036279-1-vineet.gupta@linux.dev> (raw)

Hi,

This is a set of fixes accumulated during BPF_GCC testing and an in-works
verifier enhancement series for 32-bit tracking.

Changes since v1:

 - 1/4: reworked. Instead of forcing BPF_STX with barrier_var(), select
   the expected message with #ifdef __BPF_FEATURE_ST, per Yonghong. The
   changelog now spells out the two tradeoffs: on a BPF_ST toolchain the
   test no longer reaches map_kptr_match_type(), and __BPF_FEATURE_ST
   means "can emit BPF_ST", not "will" - clang -mcpu=v4 -O0 still emits
   BPF_STX, so the #ifdef is only correct because selftests build at -O2.

 - 2/4: reword the comment above the error-summary walk. With
   --no-error-summary and no --json-summary the loop is skipped
   entirely, not just the printing, which the old wording obscured.
   [bpf-ci]

 - 4/4: the RV64 recipe in README.rst wraps the denylist in \" and
   relies on the guest's second parse of the init script to remove
   them, so %q broke it - the quotes reached test_progs and
   parse_test_list() split them into junk filters. Drop the
   backslashes so the host consumes the quotes, and correct the
   changelog, which wrongly claimed README.rst shows the command
   unquoted. [bpf-ci]

 - 3/4: unchanged.

v1: https://lore.kernel.org/bpf/20260803170251.1898102-1-vineet.gupta@linux.dev

Thx,
-Vineet

Vineet Gupta (4):
  selftests/bpf: map_kptr: expect BPF_ST reject msg on cpuv4 toolchains
  selftests/bpf: add --no-error-summary to skip end-of-run error log
    dump
  selftests/bpf: report failed subtest count in test_progs summary
  selftests/bpf: vmtest.sh: preserve command quoting when running in the
    VM

 tools/testing/selftests/bpf/README.rst        |  4 +-
 .../selftests/bpf/progs/map_kptr_fail.c       |  9 +++
 tools/testing/selftests/bpf/test_progs.c      | 64 +++++++++++++------
 tools/testing/selftests/bpf/test_progs.h      |  3 +-
 tools/testing/selftests/bpf/vmtest.sh         | 13 +++-
 5 files changed, 67 insertions(+), 26 deletions(-)

-- 
2.53.0-Meta


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

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-07 20:44 Vineet Gupta [this message]
2026-08-07 20:44 ` [PATCH bpf-next v2 1/4] selftests/bpf: map_kptr: expect BPF_ST reject msg on cpuv4 toolchains Vineet Gupta
2026-08-07 20:53   ` sashiko-bot
2026-08-07 21:15     ` Vineet Gupta
2026-08-08 19:16     ` Yonghong Song
2026-08-08 19:10   ` Yonghong Song
2026-08-07 20:44 ` [PATCH bpf-next v2 2/4] selftests/bpf: add --no-error-summary to skip end-of-run error log dump Vineet Gupta
2026-08-07 22:05   ` bot+bpf-ci
2026-08-07 20:44 ` [PATCH bpf-next v2 3/4] selftests/bpf: report failed subtest count in test_progs summary Vineet Gupta
2026-08-07 20:44 ` [PATCH bpf-next v2 4/4] selftests/bpf: vmtest.sh: preserve command quoting when running in the VM Vineet Gupta

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=20260807204434.1036279-1-vineet.gupta@linux.dev \
    --to=vineet.gupta@linux.dev \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=yonghong.song@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.