From: Ihor Solodrai <ihor.solodrai@linux.dev>
To: Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Eduard Zingerman <eddyz87@gmail.com>
Cc: bpf@vger.kernel.org, linux-kernel@vger.kernel.org, kernel-team@meta.com
Subject: [PATCH bpf v1 0/7] selftests/bpf: Add and use strscpy()
Date: Fri, 20 Feb 2026 10:20:04 -0800 [thread overview]
Message-ID: <20260220182011.802116-1-ihor.solodrai@linux.dev> (raw)
This series introduces a simplified implementation of strscpy() to
selftests/bpf and then replaces strcpy/strncpy usages across the tests
with it.
For context see a discussion that prompted this series [1].
[1] https://lore.kernel.org/bpf/CAADnVQ+9uw2_o388j43EWiAPdMB=3FLx2jq-9zRSvqrv-wgRag@mail.gmail.com/
Suggested-by: Alexei Starovoitov <ast@kernel.org>
Ihor Solodrai (7):
selftests/bpf: Add simple strscpy() implementation
selftests/bpf: Add strscpy_cat()
selftests/bpf: Replace strcpy() calls with strscpy()
selftests/bpf: Replace strncpy() with strscpy()
selftests/bpf: Use strscpy_cat() in the test_loader
selftests/bpf: Use strscpy in bpftool_helpers.c
selftests/bpf: Use memcpy() for bounded non-NULL-terminated copies
tools/testing/selftests/bpf/bpf_util.h | 66 +++++++++++++++----
tools/testing/selftests/bpf/bpftool_helpers.c | 16 +++--
tools/testing/selftests/bpf/cgroup_helpers.c | 2 +-
tools/testing/selftests/bpf/network_helpers.c | 5 +-
.../testing/selftests/bpf/prog_tests/align.c | 2 +-
.../selftests/bpf/prog_tests/bpf_iter.c | 3 +-
.../selftests/bpf/prog_tests/bpf_tcp_ca.c | 2 +-
.../selftests/bpf/prog_tests/ctx_rewrite.c | 6 +-
.../selftests/bpf/prog_tests/flow_dissector.c | 4 +-
.../bpf/prog_tests/queue_stack_map.c | 4 +-
.../selftests/bpf/prog_tests/setget_sockopt.c | 2 +-
.../bpf/prog_tests/skc_to_unix_sock.c | 2 +-
.../selftests/bpf/prog_tests/sockopt_sk.c | 2 +-
.../bpf/prog_tests/task_local_data.h | 2 +-
.../selftests/bpf/prog_tests/tc_redirect.c | 2 +-
.../selftests/bpf/prog_tests/test_veristat.c | 4 +-
tools/testing/selftests/bpf/test_loader.c | 8 +--
tools/testing/selftests/bpf/test_progs.c | 2 +-
tools/testing/selftests/bpf/test_verifier.c | 2 +-
tools/testing/selftests/bpf/xdp_features.c | 3 +-
tools/testing/selftests/bpf/xdp_hw_metadata.c | 4 +-
21 files changed, 93 insertions(+), 50 deletions(-)
--
2.53.0
next reply other threads:[~2026-02-20 18:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 18:20 Ihor Solodrai [this message]
2026-02-20 18:20 ` [PATCH bpf v1 1/7] selftests/bpf: Add simple strscpy() implementation Ihor Solodrai
2026-02-20 18:20 ` [PATCH bpf v1 2/7] selftests/bpf: Add strscpy_cat() Ihor Solodrai
2026-02-20 23:04 ` Alexei Starovoitov
2026-02-20 18:20 ` [PATCH bpf v1 3/7] selftests/bpf: Replace strcpy() calls with strscpy() Ihor Solodrai
2026-02-20 18:20 ` [PATCH bpf v1 4/7] selftests/bpf: Replace strncpy() " Ihor Solodrai
2026-02-20 18:20 ` [PATCH bpf v1 5/7] selftests/bpf: Use strscpy_cat() in the test_loader Ihor Solodrai
2026-02-20 18:20 ` [PATCH bpf v1 6/7] selftests/bpf: Use strscpy in bpftool_helpers.c Ihor Solodrai
2026-02-20 18:20 ` [PATCH bpf v1 7/7] selftests/bpf: Use memcpy() for bounded non-NULL-terminated copies Ihor Solodrai
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=20260220182011.802116-1-ihor.solodrai@linux.dev \
--to=ihor.solodrai@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
/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