From: Shung-Hsi Yu <shung-hsi.yu@suse.com>
To: bpf@vger.kernel.org, Andrii Nakryiko <andrii@kernel.org>,
Ihor Solodrai <ihor.solodrai@linux.dev>
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Eduard Zingerman <eddyz87@gmail.com>,
Paul Chaignon <paul.chaignon@gmail.com>
Subject: BPF CI for Stable
Date: Fri, 5 Jun 2026 15:45:58 +0800 [thread overview]
Message-ID: <aiJ2X7ut4lky47aV@u94a> (raw)
Hi,
Following up on the LSF/MM/BPF 2026 session "BPF in Stable Kernels, an
Update"[1]. Since the event, 6.1 coverage has also been added[2] (thanks
to Paul). With a collaborator on my side, it seem like a good time to
ask:
Is it possible to get BPF CI for stable in its own repository under a
GitHub organization (e.g. libbpf/stable-bpf-ci)?
Currently it lives as a personal repo that is fork of libbpf/libbpf[3].
As someone (I think it was Andrii) pointed out during the session, the
vast files currently in my fork are not needed at all. The GitHub Action
workflow only needs the .github/, plus the supplement files under ci/.
Technically BPF CI for stable can also simply be merged back to
libbpf/libbpf, but that felt less ideal because:
- kbuilder-debian container image currently doesn't work when testing
stable kernels (I haven't look at reason of failure, might not be hard
to fix)
- actions that tests stable kernel will be mixed with actions targeting
libbpf itself
- BPF CI for stable will have to contain version-specific tweaks (e.g.
[4])
None of the above are fatal flaws that prevent libbf/libbpf to host
files that run BPF selftests on stable kernel, so I'd say having a
standalone repository is more of a personal preference.
OTOH we can also try kernel-patches/bpf-like approach and have a
kernel-patches/stable, providing proper, fully-fledged BPF CI for stable
that tests incoming patchset to stable (not sure if Daniel was asking
about this during the session). But I find this to be much more work.
The current approach of applying queued patches from stable-queue[5],
while comes with quite some delay between the moment patch is proposed
to stable mailing vs the moment said patch gets tested, seem like a
workable compromise.
Thanks,
Shung-Hsi
1: https://speakerdeck.com/shunghsiyu/bpf-in-stable-kernels-an-update
2: https://github.com/shunghsiyu/libbpf/pull/5
3: https://github.com/shunghsiyu/libbpf/
4: https://github.com/shunghsiyu/libbpf/tree/master/ci/diffs/6.1
5: https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/
next reply other threads:[~2026-06-05 7:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-05 7:45 Shung-Hsi Yu [this message]
2026-06-05 17:12 ` BPF CI for Stable Ihor Solodrai
2026-06-10 8:18 ` Shung-Hsi Yu
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=aiJ2X7ut4lky47aV@u94a \
--to=shung-hsi.yu@suse.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=ihor.solodrai@linux.dev \
--cc=paul.chaignon@gmail.com \
/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.