From: Yonghong Song <yhs@fb.com>
To: Udip Pant <udippant@fb.com>, Alexei Starovoitov <ast@kernel.org>,
Martin KaFai Lau <kafai@fb.com>, Song Liu <songliubraving@fb.com>,
Andrii Nakryiko <andriin@fb.com>,
"David S . Miller" <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, <bpf@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH bpf] bpf: verifier: check for packet data access based on target prog
Date: Tue, 18 Aug 2020 23:03:45 -0700 [thread overview]
Message-ID: <fce8d46c-ff72-f885-b8a4-06813f832375@fb.com> (raw)
In-Reply-To: <20200819011244.2027725-1-udippant@fb.com>
On 8/18/20 6:12 PM, Udip Pant wrote:
> While using dynamic program extension (of type BPF_PROG_TYPE_EXT), we
> need to check the program type of the target program to grant the read /
> write access to the packet data.
>
> The BPF_PROG_TYPE_EXT type can be used to extend types such as XDP, SKB
> and others. Since the BPF_PROG_TYPE_EXT program type on itself is just a
> placeholder for those, we need this extended check for those target
> programs to actually work while using this option.
>
> Tested this with a freplace xdp program. Without this patch, the
> verifier fails with error 'cannot write into packet'.
Could you add a selftest for this? FYI, current selftests/bpf have
4 freplace programs:
fexit_bpf2bpf.c:SEC("freplace/get_skb_len")
fexit_bpf2bpf.c:SEC("freplace/get_skb_ifindex")
fexit_bpf2bpf.c:SEC("freplace/get_constant")
freplace_connect4.c:SEC("freplace/do_bind")
>
> Signed-off-by: Udip Pant <udippant@fb.com>
> ---
> kernel/bpf/verifier.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/kernel/bpf/verifier.c b/kernel/bpf/verifier.c
> index ef938f17b944..4d7604430994 100644
> --- a/kernel/bpf/verifier.c
> +++ b/kernel/bpf/verifier.c
> @@ -2629,7 +2629,11 @@ static bool may_access_direct_pkt_data(struct bpf_verifier_env *env,
> const struct bpf_call_arg_meta *meta,
> enum bpf_access_type t)
> {
> - switch (env->prog->type) {
> + struct bpf_prog *prog = env->prog;
> + enum bpf_prog_type prog_type = prog->aux->linked_prog ?
> + prog->aux->linked_prog->type : prog->type;
> +
> + switch (prog_type) {
> /* Program types only with direct read access go here! */
> case BPF_PROG_TYPE_LWT_IN:
> case BPF_PROG_TYPE_LWT_OUT:
>
prev parent reply other threads:[~2020-08-19 6:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 1:12 Udip Pant
2020-08-19 6:03 ` 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=fce8d46c-ff72-f885-b8a4-06813f832375@fb.com \
--to=yhs@fb.com \
--cc=andriin@fb.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=kafai@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=udippant@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
all inboxes | Powered by JetHome®