From: Maciej Fijalkowski <maciejromanfijalkowski@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@redhat.com>
Cc: Jesper Dangaard Brouer <brouer@redhat.com>,
netdev@vger.kernel.org, Daniel Borkmann <daniel@iogearbox.net>,
Alexei Starovoitov <ast@kernel.org>,
David Miller <davem@davemloft.net>,
Jonathan Lemon <jonathan.lemon@gmail.com>
Subject: Re: [PATCH bpf-next v3 2/3] bpf_xdp_redirect_map: Perform map lookup in eBPF helper
Date: Wed, 12 Jun 2019 22:01:05 +0200 [thread overview]
Message-ID: <20190612220105.00000d39@gmail.com> (raw)
In-Reply-To: <87y328f0m9.fsf@toke.dk>
On Tue, 11 Jun 2019 20:17:02 +0200
Toke Høiland-Jørgensen <toke@redhat.com> wrote:
> Jesper Dangaard Brouer <brouer@redhat.com> writes:
>
> > On Tue, 11 Jun 2019 17:44:00 +0200
> > Toke Høiland-Jørgensen <toke@redhat.com> wrote:
> >
> >> From: Toke Høiland-Jørgensen <toke@redhat.com>
> >>
> >> The bpf_redirect_map() helper used by XDP programs doesn't return any
> >> indication of whether it can successfully redirect to the map index it was
> >> given. Instead, BPF programs have to track this themselves, leading to
> >> programs using duplicate maps to track which entries are populated in the
> >> devmap.
> >>
> >> This patch fixes this by moving the map lookup into the bpf_redirect_map()
> >> helper, which makes it possible to return failure to the eBPF program. The
> >> lower bits of the flags argument is used as the return code, which means
> >> that existing users who pass a '0' flag argument will get XDP_ABORTED.
> >>
> >> With this, a BPF program can check the return code from the helper call and
> >> react by, for instance, substituting a different redirect. This works for
> >> any type of map used for redirect.
> >>
> >> Signed-off-by: Toke Høiland-Jørgensen <toke@redhat.com>
> >> ---
> >> include/linux/filter.h | 1 +
> >> include/uapi/linux/bpf.h | 8 ++++++++
> >> net/core/filter.c | 26 ++++++++++++--------------
> >> 3 files changed, 21 insertions(+), 14 deletions(-)
> >>
> >> diff --git a/include/linux/filter.h b/include/linux/filter.h
> >> index 43b45d6db36d..f31ae8b9035a 100644
> >> --- a/include/linux/filter.h
> >> +++ b/include/linux/filter.h
> >> @@ -580,6 +580,7 @@ struct bpf_skb_data_end {
> >> struct bpf_redirect_info {
> >> u32 ifindex;
> >> u32 flags;
> >> + void *item;
> >> struct bpf_map *map;
> >> struct bpf_map *map_to_flush;
> >> u32 kern_flags;
> >> diff --git a/include/uapi/linux/bpf.h b/include/uapi/linux/bpf.h
> >> index 7c6aef253173..9931cf02de19 100644
> >> --- a/include/uapi/linux/bpf.h
> >> +++ b/include/uapi/linux/bpf.h
> >> @@ -3098,6 +3098,14 @@ enum xdp_action {
> >> XDP_REDIRECT,
> >> };
> >>
> >> +/* Flags for bpf_xdp_redirect_map helper */
> >> +
> >> +/* The lower flag bits will be the return code of bpf_xdp_redirect_map() helper
> >> + * if the map lookup fails.
> >> + */
> >> +#define XDP_REDIRECT_INVALID_MASK (XDP_ABORTED | XDP_DROP | XDP_PASS | XDP_TX)
> >> +#define XDP_REDIRECT_ALL_FLAGS XDP_REDIRECT_INVALID_MASK
> >> +
> >
> > Slightly confused about the naming of the define, see later.
> >
> >> /* user accessible metadata for XDP packet hook
> >> * new fields must be added to the end of this structure
> >> */
> >> diff --git a/net/core/filter.c b/net/core/filter.c
> >> index 7a996887c500..dd43be497480 100644
> >> --- a/net/core/filter.c
> >> +++ b/net/core/filter.c
> >> @@ -3608,17 +3608,13 @@ static int xdp_do_redirect_map(struct net_device *dev, struct xdp_buff *xdp,
> >> struct bpf_redirect_info *ri)
> >> {
> >> u32 index = ri->ifindex;
> >> - void *fwd = NULL;
> >> + void *fwd = ri->item;
> >> int err;
> >>
> >> ri->ifindex = 0;
> >> + ri->item = NULL;
> >> WRITE_ONCE(ri->map, NULL);
> >>
> >> - fwd = __xdp_map_lookup_elem(map, index);
> >> - if (unlikely(!fwd)) {
> >> - err = -EINVAL;
> >> - goto err;
> >> - }
> >> if (ri->map_to_flush && unlikely(ri->map_to_flush != map))
> >> xdp_do_flush_map();
> >>
> >> @@ -3655,18 +3651,13 @@ static int xdp_do_generic_redirect_map(struct net_device *dev,
> >> {
> >> struct bpf_redirect_info *ri = this_cpu_ptr(&bpf_redirect_info);
> >> u32 index = ri->ifindex;
> >> - void *fwd = NULL;
> >> + void *fwd = ri->item;
> >> int err = 0;
> >>
> >> ri->ifindex = 0;
> >> + ri->item = NULL;
> >> WRITE_ONCE(ri->map, NULL);
> >>
> >> - fwd = __xdp_map_lookup_elem(map, index);
> >> - if (unlikely(!fwd)) {
> >> - err = -EINVAL;
> >> - goto err;
> >> - }
> >> -
> >> if (map->map_type == BPF_MAP_TYPE_DEVMAP) {
> >> struct bpf_dtab_netdev *dst = fwd;
> >>
> >> @@ -3735,6 +3726,7 @@ BPF_CALL_2(bpf_xdp_redirect, u32, ifindex, u64, flags)
> >>
> >> ri->ifindex = ifindex;
> >> ri->flags = flags;
> >> + ri->item = NULL;
> >> WRITE_ONCE(ri->map, NULL);
> >>
> >> return XDP_REDIRECT;
> >> @@ -3753,9 +3745,15 @@ BPF_CALL_3(bpf_xdp_redirect_map, struct bpf_map *, map, u32, ifindex,
> >> {
> >> struct bpf_redirect_info *ri = this_cpu_ptr(&bpf_redirect_info);
> >>
> >> - if (unlikely(flags))
> >> + if (unlikely(flags & ~XDP_REDIRECT_ALL_FLAGS))
> >> return XDP_ABORTED;
> >>
Here you don't allow the flags to get different value than
XDP_REDIRECT_ALL_FLAGS.
> >> + ri->item = __xdp_map_lookup_elem(map, ifindex);
> >> + if (unlikely(!ri->item)) {
> >> + WRITE_ONCE(ri->map, NULL);
> >> + return (flags & XDP_REDIRECT_INVALID_MASK);
So here you could just return flags? Don't we know that the flags value is
legit here? Am I missing something? TBH the v2 was more clear to me.
> >
> > Maybe I'm reading it wrong, but shouldn't the mask be called the "valid" mask?
>
> It's the mask that is applied when the index looked up is invalid (i.e.,
> the entry doesn't exist)? But yeah, can see how the name can be
> confusing; maybe it should just be "RETURN_MASK" or something like that?
Maybe something along ALLOWED_RETVAL_MASK?
>
> -Toke
next prev parent reply other threads:[~2019-06-12 20:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 15:44 [PATCH bpf-next v3 0/3] xdp: Allow lookup into devmaps before redirect Toke Høiland-Jørgensen
2019-06-11 15:44 ` [PATCH bpf-next v3 3/3] devmap: Allow map lookups from eBPF Toke Høiland-Jørgensen
2019-06-11 15:44 ` [PATCH bpf-next v3 1/3] devmap/cpumap: Use flush list instead of bitmap Toke Høiland-Jørgensen
2019-06-13 5:51 ` Andrii Nakryiko
2019-06-13 11:02 ` Toke Høiland-Jørgensen
2019-06-11 15:44 ` [PATCH bpf-next v3 2/3] bpf_xdp_redirect_map: Perform map lookup in eBPF helper Toke Høiland-Jørgensen
2019-06-11 18:00 ` Jesper Dangaard Brouer
2019-06-11 18:17 ` Toke Høiland-Jørgensen
2019-06-12 20:01 ` Maciej Fijalkowski [this message]
2019-06-12 21:33 ` Toke Høiland-Jørgensen
2019-06-11 21:48 ` Jakub Kicinski
2019-06-12 9:49 ` Toke Høiland-Jørgensen
2019-06-12 19:45 ` Jakub Kicinski
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=20190612220105.00000d39@gmail.com \
--to=maciejromanfijalkowski@gmail.com \
--cc=ast@kernel.org \
--cc=brouer@redhat.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=jonathan.lemon@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).