From: Alan Maguire <alan.maguire@oracle.com>
To: qmo@kernel.org
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
kpsingh@kernel.org, sdf@fomichev.me, yonghong.song@linux.dev,
song@kernel.org, haoluo@google.com, jolsa@kernel.org,
ihor.solodrai@linux.dev, john.fastabend@gmail.com,
eddyz87@gmail.com, bpf@vger.kernel.org,
Alan Maguire <alan.maguire@oracle.com>
Subject: [PATCH v2 0/2] Ease BPF signing build requirements
Date: Thu, 20 Nov 2025 08:47:52 +0000 [thread overview]
Message-ID: <20251120084754.640405-1-alan.maguire@oracle.com> (raw)
This series makes it easier to build bpftool and selftests with
signing support, removing reliance on >= openssl v3 (supporting
openssl v1) to build bpftool and not requiring latest xxd to
build verification cert header in selftests.
Changes since v1 [1]:
- Updated patch 2 to add symlink test_progs_verification_cert to .gitignore,
EXTRA_CLEANFILES (AI review bot)
- Added acks to patch 1 (Song, Quentin)
[1] https://lore.kernel.org/bpf/20251114222249.30122-1-alan.maguire@oracle.com/
Alan Maguire (2):
bpftool: Allow bpftool to build with openssl < 3
selftests/bpf: Allow selftests to build with older xxd
tools/bpf/bpftool/sign.c | 6 ++++++
tools/testing/selftests/bpf/.gitignore | 1 +
tools/testing/selftests/bpf/Makefile | 6 ++++--
3 files changed, 11 insertions(+), 2 deletions(-)
--
2.43.5
next reply other threads:[~2025-11-20 8:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 8:47 Alan Maguire [this message]
2025-11-20 8:47 ` [PATCH v2 1/2] bpftool: Allow bpftool to build with openssl < 3 Alan Maguire
2025-11-20 8:47 ` [PATCH v2 2/2] selftests/bpf: Allow selftests to build with older xxd Alan Maguire
2025-11-24 18:30 ` [PATCH v2 0/2] Ease BPF signing build requirements patchwork-bot+netdevbpf
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=20251120084754.640405-1-alan.maguire@oracle.com \
--to=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=ihor.solodrai@linux.dev \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=qmo@kernel.org \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox