All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mykyta Yatsenko <mykyta.yatsenko5@gmail.com>
To: Chengkaitao <pilgrimtao@gmail.com>,
	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: Re: [PATCH v5 4/6] selftests/bpf: Add test case for bpf_list_add_impl
Date: Wed, 04 Mar 2026 15:40:23 +0000	[thread overview]
Message-ID: <87342fzjq0.fsf@gmail.com> (raw)
In-Reply-To: <20260304031606.43884-5-pilgrimtao@gmail.com>

Chengkaitao <pilgrimtao@gmail.com> writes:

> From: Kaitao Cheng <chengkaitao@kylinos.cn>
>
> Extend refcounted_kptr test to exercise bpf_list_add:
> add a second node after the first, then bpf_list_del both nodes.
>
> To verify the validity of bpf_list_add, also expect the verifier
> to reject calls to bpf_list_add made without holding the spin_lock.
>
> Signed-off-by: Kaitao Cheng <chengkaitao@kylinos.cn>
> ---
>  .../testing/selftests/bpf/bpf_experimental.h  |  16 +++
>  .../selftests/bpf/progs/refcounted_kptr.c     | 122 ++++++++++++++++--
>  2 files changed, 124 insertions(+), 14 deletions(-)
>
> diff --git a/tools/testing/selftests/bpf/bpf_experimental.h b/tools/testing/selftests/bpf/bpf_experimental.h
> index 54ec9d307fdc..fdcc7a054095 100644
> --- a/tools/testing/selftests/bpf/bpf_experimental.h
> +++ b/tools/testing/selftests/bpf/bpf_experimental.h
> @@ -110,6 +110,22 @@ extern struct bpf_list_node *bpf_list_pop_back(struct bpf_list_head *head) __ksy
>  extern struct bpf_list_node *bpf_list_del(struct bpf_list_head *head,
>  					  struct bpf_list_node *node) __ksym;
should this be available from vmlinux.h?
>  
> +/* Description
> + *	Insert 'new' after 'prev' in the BPF linked list with head 'head'.
> + *	The bpf_spin_lock protecting the list must be held. 'prev' must already
> + *	be in that list; 'new' must not be in any list. The 'meta' and 'off'
> + *	parameters are rewritten by the verifier, no need for BPF programs to
> + *	set them.
> + * Returns
> + *	0 on success, -EINVAL if head is NULL, prev is not in the list with head,
> + *	or new is already in a list.
> + */
> +extern int bpf_list_add_impl(struct bpf_list_head *head, struct bpf_list_node *new,
> +			     struct bpf_list_node *prev, void *meta, __u64 off) __ksym;
> +
> +/* Convenience macro to wrap over bpf_list_add_impl */
> +#define bpf_list_add(head, new, prev) bpf_list_add_impl(head, new, prev, NULL, 0)
> +
>  /* Description
>   *	Remove 'node' from rbtree with root 'root'
>   * Returns
> diff --git a/tools/testing/selftests/bpf/progs/refcounted_kptr.c b/tools/testing/selftests/bpf/progs/refcounted_kptr.c
> index ac7672cfefb8..5a83274e1d26 100644
> --- a/tools/testing/selftests/bpf/progs/refcounted_kptr.c
> +++ b/tools/testing/selftests/bpf/progs/refcounted_kptr.c
> @@ -367,18 +367,19 @@ long insert_rbtree_and_stash__del_tree_##rem_tree(void *ctx)		\
>  INSERT_STASH_READ(true, "insert_stash_read: remove from tree");
>  INSERT_STASH_READ(false, "insert_stash_read: don't remove from tree");
>  
> -/* Insert node_data into both rbtree and list, remove from tree, then remove
> - * from list via bpf_list_del using the node obtained from the tree.
> +/* Insert one node in tree and list, remove it from tree, add a second
Use kernel comment style: first line is just "/*" then text starts from
the next one.
> + * node after it in list with bpf_list_add, then remove both nodes from
> + * list via bpf_list_del.
>   */
It sounds like the new test is quite different from the previous, why
not add a separate test running new codepaths instead of retrofitting
into the existing test?
>  SEC("tc")
> -__description("test_bpf_list_del: remove an arbitrary node from the list")
> +__description("test_list_add_del: test bpf_list_add/del")
>  __success __retval(0)
> -long test_bpf_list_del(void *ctx)
> +long test_list_add_del(void *ctx)
>  {
> -	long err;
> +	long err = 0;
>  	struct bpf_rb_node *rb;
> -	struct bpf_list_node *l;
> -	struct node_data *n;
> +	struct bpf_list_node *l, *l_1;
> +	struct node_data *n, *n_1, *m_1;
nit: The naming scheme is a little bit confusing.
>  
>  	err = __insert_in_tree_and_list(&head, &root, &lock);
>  	if (err)
> @@ -392,20 +393,48 @@ long test_bpf_list_del(void *ctx)
>  	}
>  
>  	rb = bpf_rbtree_remove(&root, rb);
> -	if (!rb) {
> -		bpf_spin_unlock(&lock);
> +	bpf_spin_unlock(&lock);
> +	if (!rb)
>  		return -5;
> -	}
>  
>  	n = container_of(rb, struct node_data, r);
> +	n_1 = bpf_obj_new(typeof(*n_1));
> +	if (!n_1) {
> +		bpf_obj_drop(n);
> +		return -1;
> +	}
> +	m_1 = bpf_refcount_acquire(n_1);
> +	if (!m_1) {
> +		bpf_obj_drop(n);
> +		bpf_obj_drop(n_1);
> +		return -1;
> +	}
> +
> +	bpf_spin_lock(&lock);
> +	if (bpf_list_add(&head, &n_1->l, &n->l)) {
> +		bpf_spin_unlock(&lock);
> +		bpf_obj_drop(n);
> +		bpf_obj_drop(m_1);
> +		return -8;
> +	}
> +
>  	l = bpf_list_del(&head, &n->l);
> +	l_1 = bpf_list_del(&head, &m_1->l);
>  	bpf_spin_unlock(&lock);
>  	bpf_obj_drop(n);
> -	if (!l)
> -		return -6;
> +	bpf_obj_drop(m_1);
>  
> -	bpf_obj_drop(container_of(l, struct node_data, l));
> -	return 0;
> +	if (l)
Can we do early returns, like
if (!l)
   return -6;
bpf_obj_drop(l);
if (!l_1)
   return -7;
bpf_obj_drop(l_1);

The point of returning different errors per each error path is to make
it easy to understand where your test errored out by just looking at err.
> +		bpf_obj_drop(container_of(l, struct node_data, l));
> +	else
> +		err = -6;
> +
> +	if (l_1)
> +		bpf_obj_drop(container_of(l_1, struct node_data, l));
> +	else
> +		err = -6;
> +
> +	return err;
>  }
>  
>  SEC("?tc")
> @@ -438,6 +467,71 @@ long list_del_without_lock_fail(void *ctx)
>  	return 0;
>  }
>  
> +SEC("?tc")
> +__failure __msg("bpf_spin_lock at off=32 must be held for bpf_list_head")
> +long list_add_without_lock_fail(void *ctx)
> +{
> +	long err = 0;
> +	struct bpf_rb_node *rb;
> +	struct bpf_list_node *l, *l_1;
> +	struct node_data *n, *n_1, *m_1;
> +
> +	err = __insert_in_tree_and_list(&head, &root, &lock);
> +	if (err)
> +		return err;
> +
> +	bpf_spin_lock(&lock);
> +	rb = bpf_rbtree_first(&root);
> +	if (!rb) {
> +		bpf_spin_unlock(&lock);
> +		return -4;
> +	}
> +
> +	rb = bpf_rbtree_remove(&root, rb);
> +	bpf_spin_unlock(&lock);
> +	if (!rb)
> +		return -5;
> +
> +	n = container_of(rb, struct node_data, r);
> +	n_1 = bpf_obj_new(typeof(*n_1));
> +	if (!n_1) {
> +		bpf_obj_drop(n);
> +		return -1;
> +	}
> +	m_1 = bpf_refcount_acquire(n_1);
> +	if (!m_1) {
> +		bpf_obj_drop(n);
> +		bpf_obj_drop(n_1);
> +		return -1;
> +	}
> +
> +	/* Intentionally no lock: verifier should reject bpf_list_add without lock */
> +	if (bpf_list_add(&head, &n_1->l, &n->l)) {
> +		bpf_obj_drop(n);
> +		bpf_obj_drop(m_1);
> +		return -8;
> +	}
> +
> +	bpf_spin_lock(&lock);
> +	l = bpf_list_del(&head, &n->l);
> +	l_1 = bpf_list_del(&head, &m_1->l);
> +	bpf_spin_unlock(&lock);
> +	bpf_obj_drop(n);
> +	bpf_obj_drop(m_1);
> +
> +	if (l)
> +		bpf_obj_drop(container_of(l, struct node_data, l));
> +	else
> +		err = -6;
> +
> +	if (l_1)
> +		bpf_obj_drop(container_of(l_1, struct node_data, l));
> +	else
> +		err = -6;
> +
> +	return err;
> +}
Do we need this big test just to trigger that verifier error?
> +
>  SEC("tc")
>  __success
>  long rbtree_refcounted_node_ref_escapes(void *ctx)
> -- 
> 2.50.1 (Apple Git-155)

  reply	other threads:[~2026-03-04 15:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-04  3:16 [PATCH v5 0/6] bpf: Extend the bpf_list family of APIs Chengkaitao
2026-03-04  3:16 ` [PATCH v5 1/6] bpf: Introduce the bpf_list_del kfunc Chengkaitao
2026-03-04 15:50   ` Mykyta Yatsenko
2026-03-04  3:16 ` [PATCH v5 2/6] selftests/bpf: Add test cases for bpf_list_del Chengkaitao
2026-03-04 15:43   ` Mykyta Yatsenko
2026-03-04  3:16 ` [PATCH v5 3/6] bpf: add bpf_list_add_impl to insert node after a given list node Chengkaitao
2026-03-04  3:50   ` bot+bpf-ci
2026-03-04  3:16 ` [PATCH v5 4/6] selftests/bpf: Add test case for bpf_list_add_impl Chengkaitao
2026-03-04 15:40   ` Mykyta Yatsenko [this message]
2026-03-08 14:29     ` Chengkaitao
2026-03-04  3:16 ` [PATCH v5 5/6] bpf: add bpf_list_is_first/last/empty kfuncs Chengkaitao
2026-03-04 15:13   ` Mykyta Yatsenko
2026-03-04  3:16 ` [PATCH v5 6/6] selftests/bpf: Add test cases for bpf_list_is_first/is_last/empty Chengkaitao

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=87342fzjq0.fsf@gmail.com \
    --to=mykyta.yatsenko5@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=pilgrimtao@gmail.com \
    --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 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.