From: Martin KaFai Lau <martin.lau@linux.dev>
To: Joanne Koong <joannelkoong@gmail.com>
Cc: andrii@kernel.org, daniel@iogearbox.net, ast@kernel.org,
martin.lau@kernel.org, kuba@kernel.org, memxor@gmail.com,
toke@redhat.com, netdev@vger.kernel.org, kernel-team@fb.com,
bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next v6 1/3] bpf: Add skb dynptrs
Date: Fri, 9 Sep 2022 16:12:31 -0700 [thread overview]
Message-ID: <cd8d201b-74f7-4045-ad2f-6d26ed608d1e@linux.dev> (raw)
In-Reply-To: <20220907183129.745846-2-joannelkoong@gmail.com>
On 9/7/22 11:31 AM, Joanne Koong wrote:
> For bpf prog types that don't support writes on skb data, the dynptr is
> read-only (bpf_dynptr_write() will return an error and bpf_dynptr_data()
> will return NULL; for a read-only data slice, there will be a separate
> API bpf_dynptr_data_rdonly(), which will be added in the near future).
>
I just caught up on the v4 discussion about loadtime-vs-runtime error on
write. From a user perspective, I am not concerned on which error.
Either way, I will quickly find out the packet header is not changed.
For the dynptr init helper bpf_dynptr_from_skb(), the user does not need
to know its skb is read-only or not and uses the same helper. The
verifier in this case uses its knowledge on the skb context and uses
bpf_dynptr_from_skb_rdonly_proto or bpf_dynptr_from_skb_rdwr_proto
accordingly.
Now for the slice helper, the user needs to remember its skb is read
only (or not) and uses bpf_dynptr_data() vs bpf_dynptr_data_rdonly()
accordingly. Yes, if it only needs to read, the user can always stay
with bpf_dynptr_data_rdonly (which is not the initially supported one
though). However, it is still unnecessary burden and surprise to user.
It is likely it will silently turn everything into bpf_dynptr_read()
against the user intention. eg:
if (bpf_dynptr_from_skb(skb, 0, &dynptr))
return 0;
ip6h = bpf_dynptr_data(&dynptr, 0, sizeof(*ip6h));
if (!ip6h) {
/* Unlikely case, in non-linear section, just bpf_dynptr_read()
* Oops...actually bpf_dynptr_data_rdonly() should be used.
*/
bpf_dynptr_read(buf, sizeof(*ip6h), &dynptr, 0, 0);
ip6h = buf;
}
> + case BPF_DYNPTR_TYPE_SKB:
> + {
> + struct sk_buff *skb = ptr->data;
> +
> + /* if the data is paged, the caller needs to pull it first */
> + if (ptr->offset + offset + len > skb->len - skb->data_len)
nit. skb_headlen(skb)
The patches can't be applied cleanly also. Please remember to rebase.
eg. commit afef88e65554 ("selftests/bpf: Store BPF object files with
.bpf.o extension") has landed on Sep 2.
next parent reply other threads:[~2022-09-09 23:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220907183129.745846-1-joannelkoong@gmail.com>
[not found] ` <20220907183129.745846-2-joannelkoong@gmail.com>
2022-09-09 23:12 ` Martin KaFai Lau [this message]
2022-10-19 20:22 ` [PATCH bpf-next v6 1/3] bpf: Add skb dynptrs Joanne Koong
2022-10-20 6:34 ` Martin KaFai Lau
2022-10-20 6:40 ` Martin KaFai Lau
2022-10-20 19:30 ` Joanne Koong
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=cd8d201b-74f7-4045-ad2f-6d26ed608d1e@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=joannelkoong@gmail.com \
--cc=kernel-team@fb.com \
--cc=kuba@kernel.org \
--cc=martin.lau@kernel.org \
--cc=memxor@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=toke@redhat.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;
as well as URLs for NNTP newsgroup(s).