From: Yonghong Song <yhs@meta.com>
To: John Fastabend <john.fastabend@gmail.com>,
Yonghong Song <yhs@fb.com>,
bpf@vger.kernel.org
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>
Subject: Re: [PATCH bpf-next v7 4/4] selftests/bpf: Add tests for bpf_rcu_read_lock()
Date: Mon, 21 Nov 2022 20:09:22 -0800 [thread overview]
Message-ID: <e577e7de-c5e9-fcbe-bafa-2b9b761b655f@meta.com> (raw)
In-Reply-To: <637c2d1826988_18ed920851@john.notmuch>
On 11/21/22 5:59 PM, John Fastabend wrote:
> Yonghong Song wrote:
>> Add a few positive/negative tests to test bpf_rcu_read_lock()
>> and its corresponding verifier support. The new test will fail
>> on s390x and aarch64, so an entry is added to each of their
>> respective deny lists.
>>
>> Signed-off-by: Yonghong Song <yhs@fb.com>
>
> [...]
>
>> +SEC("?fentry.s/" SYS_PREFIX "sys_nanosleep")
>> +int nested_rcu_region(void *ctx)
>> +{
>> + struct task_struct *task, *real_parent;
>> +
>> + /* nested rcu read lock regions */
>> + task = bpf_get_current_task_btf();
>> + bpf_rcu_read_lock();
>> + bpf_rcu_read_lock();
>> + real_parent = task->real_parent;
>> + (void)bpf_task_storage_get(&map_a, real_parent, 0, 0);
>> + bpf_rcu_read_unlock();
>> + bpf_rcu_read_unlock();
>> + return 0;
>> +}
>
> I think you also need the nested imbalance case is this
> handled? It looks like the active_rcu is just a bool?
Currently we don't support nested bpf_rcu_read_lock()
regions. So the error will appear for the second
bpf_rcu_read_lock() in the above code, regardless of
the eventual balance or not-balance.
>
> +SEC("?fentry.s/" SYS_PREFIX "sys_nanosleep")
> +int nested_rcu_region(void *ctx)
> +{
> + struct task_struct *task, *real_parent;
> +
> + /* nested rcu read lock regions */
> + task = bpf_get_current_task_btf();
> + bpf_rcu_read_lock();
> + bpf_rcu_read_lock();
> + real_parent = task->real_parent;
> + (void)bpf_task_storage_get(&map_a, real_parent, 0, 0);
> + // imbalance unlock()
> + bpf_rcu_read_unlock();
> + return 0;
> +}
prev parent reply other threads:[~2022-11-22 4:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 17:05 [PATCH bpf-next v7 0/4] bpf: Add bpf_rcu_read_lock() support Yonghong Song
2022-11-21 17:05 ` [PATCH bpf-next v7 1/4] compiler_types: Define __rcu as __attribute__((btf_type_tag("rcu"))) Yonghong Song
2022-11-21 17:05 ` [PATCH bpf-next v7 2/4] bpf: Abstract out functions to check sleepable helpers Yonghong Song
2022-11-22 17:06 ` KP Singh
2022-11-21 17:05 ` [PATCH bpf-next v7 3/4] bpf: Add kfunc bpf_rcu_read_lock/unlock() Yonghong Song
2022-11-21 19:41 ` Martin KaFai Lau
2022-11-21 20:01 ` Yonghong Song
2022-11-21 22:56 ` Martin KaFai Lau
2022-11-21 23:42 ` Yonghong Song
2022-11-22 2:03 ` John Fastabend
2022-11-22 4:16 ` Yonghong Song
2022-11-22 5:48 ` Alexei Starovoitov
2022-11-22 6:32 ` Yonghong Song
2022-11-21 17:05 ` [PATCH bpf-next v7 4/4] selftests/bpf: Add tests for bpf_rcu_read_lock() Yonghong Song
2022-11-22 1:59 ` John Fastabend
2022-11-22 4:09 ` Yonghong Song [this message]
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=e577e7de-c5e9-fcbe-bafa-2b9b761b655f@meta.com \
--to=yhs@meta.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox