From: Philo Lu <lulie@linux.alibaba.com>
To: Martin KaFai Lau <martin.lau@linux.dev>
Cc: ast@kernel.org, daniel@iogearbox.net, john.fastabend@gmail.com,
andrii@kernel.org, eddyz87@gmail.com, song@kernel.org,
yonghong.song@linux.dev, kpsingh@kernel.org, sdf@fomichev.me,
haoluo@google.com, jolsa@kernel.org, xuanzhuo@linux.alibaba.com,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next] bpf: Add rcu ptr in btf_id_sock_common_types
Date: Wed, 9 Oct 2024 10:23:48 +0800 [thread overview]
Message-ID: <2e3f676a-ef03-4618-852d-ceb3b620a640@linux.alibaba.com> (raw)
In-Reply-To: <80cb3d4b-cebb-4f08-865d-354110a54467@linux.dev>
On 2024/10/9 03:05, Martin KaFai Lau wrote:
> On 10/8/24 1:09 AM, Philo Lu wrote:
>> Sometimes sk is dereferenced as an rcu ptr, such as skb->sk in tp_btf,
>> which is a valid type of sock common. Then helpers like bpf_skc_to_*()
>> can be used with skb->sk.
>>
>> For example, the following prog will be rejected without this patch:
>> ```
>> SEC("tp_btf/tcp_bad_csum")
>> int BPF_PROG(tcp_bad_csum, struct sk_buff* skb)
>> {
>> struct sock *sk = skb->sk;
>> struct tcp_sock *tp;
>>
>> if (!sk)
>> return 0;
>> tp = bpf_skc_to_tcp_sock(sk);
>
> If the use case is for reading the fields in tp, please use the
> bpf_core_cast from the libbpf's bpf_core_read.h. bpf_core_cast is using
> the bpf_rdonly_cast kfunc underneath.
>
Thank you! This works for me so this patch is unnecessary then.
Just curious is there any technical issue to include rcu_ptr into
btf_id_sock_common_types? AFAICT rcu_ptr should also be a valid ptr
type, and then btf_id_sock_common_types will behave like (PTR_TO_BTF_ID
+ &btf_sock_ids[BTF_SOCK_TYPE_SOCK_COMMON]) in bpf_func_proto.
Thanks.
--
Philo
next prev parent reply other threads:[~2024-10-09 2:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-08 8:09 [PATCH bpf-next] bpf: Add rcu ptr in btf_id_sock_common_types Philo Lu
2024-10-08 19:05 ` Martin KaFai Lau
2024-10-09 2:23 ` Philo Lu [this message]
2024-10-10 22:07 ` Martin KaFai Lau
2024-10-11 1:46 ` Philo Lu
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=2e3f676a-ef03-4618-852d-ceb3b620a640@linux.alibaba.com \
--to=lulie@linux.alibaba.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--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=martin.lau@linux.dev \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=xuanzhuo@linux.alibaba.com \
--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