From: Jesper Dangaard Brouer <brouer@redhat•com>
To: Song Liu <liu.song.a23@gmail•com>
Cc: Networking <netdev@vger•kernel.org>,
Daniel Borkmann <borkmann@iogearbox•net>,
yoel@kviknet•dk,
Alexei Starovoitov <alexei.starovoitov@gmail•com>,
brouer@redhat•com
Subject: Re: [bpf-next PATCH 1/3] net: fix generic XDP to handle if eth header was mangled
Date: Wed, 3 Oct 2018 16:04:13 +0200 [thread overview]
Message-ID: <20181003160413.755f9cd5@redhat.com> (raw)
In-Reply-To: <CAPhsuW76ancX7f1PTV4=Ur=BL7eWKVqW-mTpHE16QJTbKMjYLA@mail.gmail.com>
On Tue, 25 Sep 2018 22:36:39 -0700
Song Liu <liu.song.a23@gmail•com> wrote:
> On Tue, Sep 25, 2018 at 7:26 AM Jesper Dangaard Brouer
> <brouer@redhat•com> wrote:
> >
> > XDP can modify (and resize) the Ethernet header in the packet.
> >
> > There is a bug in generic-XDP, because skb->protocol and skb->pkt_type
> > are setup before reaching (netif_receive_)generic_xdp.
> >
> > This bug was hit when XDP were popping VLAN headers (changing
> > eth->h_proto), as skb->protocol still contains VLAN-indication
> > (ETH_P_8021Q) causing invocation of skb_vlan_untag(skb), which corrupt
> > the packet (basically popping the VLAN again).
> >
> > This patch catch if XDP changed eth header in such a way, that SKB
> > fields needs to be updated.
> >
> > Fixes: d445516966dc ("net: xdp: support xdp generic on virtual devices")
> > Signed-off-by: Jesper Dangaard Brouer <brouer@redhat•com>
> > ---
> > net/core/dev.c | 14 ++++++++++++++
> > 1 file changed, 14 insertions(+)
> >
> > diff --git a/net/core/dev.c b/net/core/dev.c
> > index ca78dc5a79a3..db6d89f536cb 100644
> > --- a/net/core/dev.c
> > +++ b/net/core/dev.c
> > @@ -4258,6 +4258,9 @@ static u32 netif_receive_generic_xdp(struct sk_buff *skb,
> > struct netdev_rx_queue *rxqueue;
> > void *orig_data, *orig_data_end;
> > u32 metalen, act = XDP_DROP;
> > + __be16 orig_eth_type;
> > + struct ethhdr *eth;
> > + bool orig_bcast;
> > int hlen, off;
> > u32 mac_len;
> >
> > @@ -4298,6 +4301,9 @@ static u32 netif_receive_generic_xdp(struct sk_buff *skb,
> > xdp->data_hard_start = skb->data - skb_headroom(skb);
> > orig_data_end = xdp->data_end;
> > orig_data = xdp->data;
> > + eth = (struct ethhdr *)xdp->data;
> > + orig_bcast = is_multicast_ether_addr_64bits(eth->h_dest);
> > + orig_eth_type = eth->h_proto;
> >
> > rxqueue = netif_get_rxqueue(skb);
> > xdp->rxq = &rxqueue->xdp_rxq;
> > @@ -4321,6 +4327,14 @@ static u32 netif_receive_generic_xdp(struct sk_buff *skb,
> >
> > }
> >
> > + /* check if XDP changed eth hdr such SKB needs update */
> > + eth = (struct ethhdr *)xdp->data;
> > + if ((orig_eth_type != eth->h_proto) ||
> > + (orig_bcast != is_multicast_ether_addr_64bits(eth->h_dest))) {
>
> Is the actions below always correct for the condition above? Do we need
> to confirm the SKB is updated properly?
I cannot find the issue that you are hinting to?
If the BPF prog used bpf_xdp_adjust_head(), which the included selftest
program does, then skb->data have been appropriately adjusted just
above (with __skb_pull(skb, off) or __skb_push(skb, -off)), which makes
the call to skb_reset_mac_header(skb) inside eth_type_trans() correct.
I've double checked the code, and I cannot find anything wrong...
please let me know if I missed something!?
> > + __skb_push(skb, mac_len);
> > + skb->protocol = eth_type_trans(skb, skb->dev);
We could change mac_len to be ETH_HLEN, because inside eth_type_trans()
the constant ETH_HLEN is used, that way we are 100% sure the
skb_push/skb_pull are "paired". Will that be better for you?
> > + }
> > +
> > switch (act) {
> > case XDP_REDIRECT:
> > case XDP_TX:
> >
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
LinkedIn: http://www.linkedin.com/in/brouer
next prev parent reply other threads:[~2018-10-03 20:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 14:25 [bpf-next PATCH 0/3] bpf/xdp: fix generic-XDP and demonstrate VLAN manipulation Jesper Dangaard Brouer
2018-09-25 14:25 ` [bpf-next PATCH 1/3] net: fix generic XDP to handle if eth header was mangled Jesper Dangaard Brouer
2018-09-26 5:36 ` Song Liu
2018-10-01 19:13 ` Daniel Borkmann
2018-10-03 14:04 ` Jesper Dangaard Brouer [this message]
2018-10-04 23:20 ` Song Liu
2018-09-25 14:25 ` [bpf-next PATCH 2/3] bpf: make TC vlan bpf_helpers avail to selftests Jesper Dangaard Brouer
2018-09-25 14:25 ` [bpf-next PATCH 3/3] selftests/bpf: add XDP selftests for modifying and popping VLAN headers Jesper Dangaard Brouer
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=20181003160413.755f9cd5@redhat.com \
--to=brouer@redhat$(echo .)com \
--cc=alexei.starovoitov@gmail$(echo .)com \
--cc=borkmann@iogearbox$(echo .)net \
--cc=liu.song.a23@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=yoel@kviknet$(echo .)dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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