All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin KaFai Lau <martin.lau@linux.dev>
To: Yonghong Song <yhs@fb.com>
Cc: Alexei Starovoitov <ast@kernel.org>,
	Andrii Nakryiko <andrii@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	kernel-team@fb.com, Martin KaFai Lau <martin.lau@kernel.org>,
	bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next v8 4/4] selftests/bpf: Add tests for bpf_rcu_read_lock()
Date: Tue, 22 Nov 2022 16:56:51 -0800	[thread overview]
Message-ID: <201c1603-cb3e-7893-c411-e7949ef8e9d3@linux.dev> (raw)
In-Reply-To: <20221122195340.1783247-1-yhs@fb.com>

On 11/22/22 11:53 AM, Yonghong Song wrote:
> +SEC("?fentry.s/" SYS_PREFIX "sys_nanosleep")
> +int task_acquire(void *ctx)
> +{
> +	struct task_struct *task, *real_parent;
> +
> +	task = bpf_get_current_task_btf();
> +	bpf_rcu_read_lock();
> +	real_parent = task->real_parent;
> +	/* acquire a reference which can be used outside rcu read lock region */
> +	real_parent = bpf_task_acquire(real_parent);
Does the bpf_task_acquire() kfunc need a change to do refcount_inc_not_zero() 
and KF_RET_NULL?

Also, some more 'skip' checks in prog_tests/rcu_read_lock.c is needed for gcc. 
This is failing in gcc CI:

https://github.com/kernel-patches/bpf/actions/runs/3527747280/jobs/5917628248#step:6:5624

   ; bpf_rcu_read_lock();
   2: (85) call bpf_rcu_read_lock#26650
   ; real_parent = task->real_parent;
   3: (79) r1 = *(u64 *)(r6 +1416)       ; R1_w=ptr_task_struct(off=0,imm=0) 
R6_w=trusted_ptr_task_struct(off=0,imm=0)
   ; real_parent = bpf_task_acquire(real_parent);
   4: (85) call bpf_task_acquire#26666
   R1 must be referenced or trusted	
   processed 5 insns (limit 1000000) max_states_per_insn 0 total_states 0 
peak_states 0 mark_read 0
   -- END PROG LOAD LOG --
   libbpf: prog 'task_acquire': failed to load: -22

> +	bpf_rcu_read_unlock();
> +	(void)bpf_task_storage_get(&map_a, real_parent, 0, 0);
> +	bpf_task_release(real_parent);
> +	return 0;
> +}
> +
> +SEC("?fentry.s/" SYS_PREFIX "sys_nanosleep")
> +int no_lock(void *ctx)
> +{
> +	struct task_struct *task, *real_parent;
> +
> +	/* no bpf_rcu_read_lock(), old code still works */
> +	task = bpf_get_current_task_btf();
> +	real_parent = task->real_parent;
> +	bpf_printk("pid %u\n", real_parent->pid);

nit. Can bpf_printk be avoided here?

Others lgtm.


  reply	other threads:[~2022-11-23  0:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-22 19:53 [PATCH bpf-next v8 0/4] bpf: Add bpf_rcu_read_lock() support Yonghong Song
2022-11-22 19:53 ` [PATCH bpf-next v8 1/4] compiler_types: Define __rcu as __attribute__((btf_type_tag("rcu"))) Yonghong Song
2022-11-22 19:53 ` [PATCH bpf-next v8 2/4] bpf: Introduce might_sleep field in bpf_func_proto Yonghong Song
2022-11-22 19:53 ` [PATCH bpf-next v8 3/4] bpf: Add kfunc bpf_rcu_read_lock/unlock() Yonghong Song
2022-11-23  0:24   ` Martin KaFai Lau
2022-11-23  1:06     ` Yonghong Song
2022-11-23  1:19       ` Martin KaFai Lau
2022-11-23  1:24         ` Yonghong Song
2022-11-22 19:53 ` [PATCH bpf-next v8 4/4] selftests/bpf: Add tests for bpf_rcu_read_lock() Yonghong Song
2022-11-23  0:56   ` Martin KaFai Lau [this message]
2022-11-23  1:13     ` Yonghong Song
2022-11-23  1:39       ` Martin KaFai Lau
2022-11-23  1:52         ` Martin KaFai Lau
     [not found]           ` <SN6PR1501MB20649F820B6FFE58166817E5CA0C9@SN6PR1501MB2064.namprd15.prod.outlook.com>
2022-11-23 23:13             ` Martin KaFai Lau

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=201c1603-cb3e-7893-c411-e7949ef8e9d3@linux.dev \
    --to=martin.lau@linux.dev \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=kernel-team@fb.com \
    --cc=martin.lau@kernel.org \
    --cc=yhs@fb.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.