From: Chengkaitao <pilgrimtao@gmail.com>
To: martin.lau@linux.dev, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, eddyz87@gmail.com, song@kernel.org,
yonghong.song@linux.dev, john.fastabend@gmail.com,
kpsingh@kernel.org, sdf@fomichev.me, haoluo@google.com,
jolsa@kernel.org, shuah@kernel.org, chengkaitao@kylinos.cn,
linux-kselftest@vger.kernel.org
Cc: bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v6 0/5] bpf: Extend the bpf_list family of APIs
Date: Wed, 4 Mar 2026 22:34:54 +0800 [thread overview]
Message-ID: <20260304143459.78059-1-pilgrimtao@gmail.com> (raw)
From: Kaitao Cheng <chengkaitao@kylinos.cn>
In BPF, a list can only be used to implement a stack structure.
Due to an incomplete API set, only FIFO or LIFO operations are
supported. The patches enhance the BPF list API, making it more
list-like.
Four new kfuncs have been added:
bpf_list_del: remove a node from the list
bpf_list_add_impl: insert a node after a given list node
bpf_list_node_is_edge: check if a node is the first or last in the list
bpf_list_empty: check if the list is empty
refactor kfunc checks to table-driven approach, and add test cases for
the aforementioned kfuncs.
Changes in v6:
- Merge [patch v5 (2,4,6)/6] into [patch v6 4/5]
- If list_head was 0-initialized, init it
- refactor kfunc checks to table-driven approach
Changes in v5:
- Fix bpf_obj leak on bpf_list_add_impl error
Changes in v4:
- [patch v3 1/6] Revert to version v1
- Change the parameters of bpf_list_add_impl to (head, new, prev, ...)
Changes in v3:
- Add a new lock_rec member to struct bpf_reference_state for lock
holding detection.
- Add test cases to verify that the verifier correctly restricts calls
to bpf_list_del when the spin_lock is not held.
Changes in v2:
- Remove the head parameter from bpf_list_del
- Add bpf_list_add/is_first/is_last/empty to API and test cases
Link to v5:
https://lore.kernel.org/all/20260304031606.43884-1-pilgrimtao@gmail.com/
Link to v4:
https://lore.kernel.org/all/20260303135219.33726-1-pilgrimtao@gmail.com/
Link to v3:
https://lore.kernel.org/all/20260302124028.82420-1-pilgrimtao@gmail.com/
Link to v2:
https://lore.kernel.org/all/20260225092651.94689-1-pilgrimtao@gmail.com/
Link to v1:
https://lore.kernel.org/all/20260209025250.55750-1-pilgrimtao@gmail.com/
Kaitao Cheng (5):
bpf: Introduce the bpf_list_del kfunc.
bpf: Add bpf_list_add_impl to insert node after a given list node
bpf: Add bpf_list_is_edge/empty kfuncs
selftests/bpf: Add test cases for bpf_list_del/add/is_edge/empty
bpf/verifier: refactor kfunc checks to table-driven approach
kernel/bpf/helpers.c | 98 ++++++++++
kernel/bpf/verifier.c | 103 +++++++---
.../testing/selftests/bpf/bpf_experimental.h | 39 ++++
.../selftests/bpf/progs/refcounted_kptr.c | 182 ++++++++++++++++++
4 files changed, 398 insertions(+), 24 deletions(-)
--
2.50.1 (Apple Git-155)
next reply other threads:[~2026-03-04 14:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 14:34 Chengkaitao [this message]
2026-03-04 14:34 ` [PATCH v6 1/5] bpf: Introduce the bpf_list_del kfunc Chengkaitao
2026-03-06 0:00 ` Kumar Kartikeya Dwivedi
2026-03-06 0:14 ` Kumar Kartikeya Dwivedi
2026-03-06 0:28 ` Kumar Kartikeya Dwivedi
2026-03-04 14:34 ` [PATCH v6 2/5] bpf: Add bpf_list_add_impl to insert node after a given list node Chengkaitao
2026-03-06 0:36 ` Kumar Kartikeya Dwivedi
2026-03-04 14:34 ` [PATCH v6 3/5] bpf: Add bpf_list_is_edge/empty kfuncs Chengkaitao
2026-03-04 15:08 ` bot+bpf-ci
2026-03-06 0:47 ` Kumar Kartikeya Dwivedi
2026-03-04 14:34 ` [PATCH v6 4/5] selftests/bpf: Add test cases for bpf_list_del/add/is_edge/empty Chengkaitao
2026-03-06 0:52 ` Kumar Kartikeya Dwivedi
2026-03-04 14:34 ` [PATCH v6 5/5] bpf/verifier: refactor kfunc checks to table-driven approach Chengkaitao
2026-03-04 15:08 ` bot+bpf-ci
2026-03-04 15:59 ` Leon Hwang
2026-03-04 15:51 ` [PATCH v6 0/5] bpf: Extend the bpf_list family of APIs Leon Hwang
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=20260304143459.78059-1-pilgrimtao@gmail.com \
--to=pilgrimtao@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=chengkaitao@kylinos.cn \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--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