From: Jesper Dangaard Brouer <jbrouer@redhat.com>
To: Larysa Zaremba <larysa.zaremba@intel.com>, bpf <bpf@vger.kernel.org>
Cc: brouer@redhat.com, netdev <netdev@vger.kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Toke Hoiland-Jorgensen <toke@redhat.com>,
Magnus Karlsson <magnus.karlsson@intel.com>,
Maciej Fijalkowski <maciej.fijalkowski@intel.com>,
Alexander Lobakin <alexandr.lobakin@intel.com>,
"xdp-hints@xdp-project.net" <xdp-hints@xdp-project.net>
Subject: [xdp-hints] Re: Accessing XDP packet memory from the end
Date: Thu, 21 Apr 2022 18:27:47 +0200 [thread overview]
Message-ID: <f1417959-4b0d-7c33-4b2b-08989bb86b23@redhat.com> (raw)
In-Reply-To: <20220421155620.81048-1-larysa.zaremba@intel.com>
On 21/04/2022 17.56, Larysa Zaremba wrote:
> Dear all,
> Our team has encountered a need of accessing data_meta in a following way:
>
> int xdp_meta_prog(struct xdp_md *ctx)
> {
> void *data_meta_ptr = (void *)(long)ctx->data_meta;
> void *data_end = (void *)(long)ctx->data_end;
> void *data = (void *)(long)ctx->data;
> u64 data_size = sizeof(u32);
> u32 magic_meta;
> u8 offset;
>
> offset = (u8)((s64)data - (s64)data_meta_ptr);
I'm not sure the verifier can handle this 'offset' calc. As it cannot
statically know the sized based on this statement. Maybe this is not the
issue.
> if (offset < data_size) {
> bpf_printk("invalid offset: %ld\n", offset);
> return XDP_DROP;
> }
>
> data_meta_ptr += offset;
> data_meta_ptr -= data_size;
>
> if (data_meta_ptr + data_size > data) {
> return XDP_DROP;
> }
>
> magic_meta = *((u32 *)data);
> bpf_printk("Magic: %d\n", magic_meta);
> return XDP_PASS;
> }
>
> Unfortunately, verifier claims this code attempts to access packet with
> an offset of -2 (a constant part) and negative offset is generally forbidden.
Are you forgetting to mention:
- Have you modified the NIC driver to adjust data_meta pointer and
provide info in this area?
p.s. this is exactly what I'm also working towards[1], so I'll be happy
to collaborate. I'm missing the driver code, as link[1] is focused on
decoding BTF data_meta area in userspace for AF_XDP.
[1]
https://github.com/xdp-project/bpf-examples/tree/master/AF_XDP-interaction
> For now we have 2 solutions, one is using bpf_xdp_adjust_meta(),
> which is pretty good, but not ideal for the hot path.
> The second one is the patch at the end.
>
Are you saying, verifier cannot handle that driver changed data_meta
pointer and provided info there (without calling bpf_xdp_adjust_meta)?
> Do you see any other way of accessing memory from the end of data_meta/data?
> What do you think about both suggested solutions?
>
> Best regards,
> Larysa Zaremba
>
> ---
>
> --- a/kernel/bpf/verifier.c
> +++ b/kernel/bpf/verifier.c
> @@ -3576,8 +3576,11 @@ static int check_packet_access(struct bpf_verifier_env *env, u32 regno, int off,
> }
>
> err = reg->range < 0 ? -EINVAL :
> - __check_mem_access(env, regno, off, size, reg->range,
> - zero_size_allowed);
> + __check_mem_access(env, regno, off + reg->smin_value, size,
> + reg->range + reg->smin_value, zero_size_allowed);
> + err = err ? :
> + __check_mem_access(env, regno, off + reg->umax_value, size,
> + reg->range + reg->umax_value, zero_size_allowed);
> if (err) {
> verbose(env, "R%d offset is outside of the packet\n", regno);
> return err;
>
next parent reply other threads:[~2022-04-21 16:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220421155620.81048-1-larysa.zaremba@intel.com>
2022-04-21 16:27 ` Jesper Dangaard Brouer [this message]
2022-04-22 10:06 ` Alexander Lobakin
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
List information: https://lists.xdp-project.net/postorius/lists/xdp-hints.xdp-project.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f1417959-4b0d-7c33-4b2b-08989bb86b23@redhat.com \
--to=jbrouer@redhat.com \
--cc=alexandr.lobakin@intel.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=brouer@redhat.com \
--cc=daniel@iogearbox.net \
--cc=larysa.zaremba@intel.com \
--cc=maciej.fijalkowski@intel.com \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=toke@redhat.com \
--cc=xdp-hints@xdp-project.net \
/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