From: Jesper Dangaard Brouer <brouer@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: Jason@zx2c4.com, netdev@vger.kernel.org, bpf@vger.kernel.org,
brouer@redhat.com
Subject: Re: [PATCH net] net: xdp: pull ethernet header off packet after computing skb->protocol
Date: Mon, 17 Aug 2020 08:01:02 +0200 [thread overview]
Message-ID: <20200817080102.61e109cf@carbon> (raw)
In-Reply-To: <20200816.152937.1107786737475087036.davem@davemloft.net>
On Sun, 16 Aug 2020 15:29:37 -0700 (PDT)
David Miller <davem@davemloft.net> wrote:
> From: "Jason A. Donenfeld" <Jason@zx2c4.com>
> Date: Sat, 15 Aug 2020 09:29:30 +0200
>
> > When an XDP program changes the ethernet header protocol field,
> > eth_type_trans is used to recalculate skb->protocol. In order for
> > eth_type_trans to work correctly, the ethernet header must actually be
> > part of the skb data segment, so the code first pushes that onto the
> > head of the skb. However, it subsequently forgets to pull it back off,
> > making the behavior of the passed-on packet inconsistent between the
> > protocol modifying case and the static protocol case. This patch fixes
> > the issue by simply pulling the ethernet header back off of the skb
> > head.
> >
> > Fixes: 297249569932 ("net: fix generic XDP to handle if eth header was mangled")
> > Cc: Jesper Dangaard Brouer <brouer@redhat.com>
> > Cc: David S. Miller <davem@davemloft.net>
> > Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
>
> Applied and queued up for -stable, thanks.
>
> Jesper, I wonder how your original patch was tested because it pushes a packet
> with skb->data pointing at the ethernet header into the stack. That should be
> popped at this point as per this fix here.
I think this patch is wrong, because eth_type_trans() also does a
skb_pull_inline(skb, ETH_HLEN).
To Jason, are you sure about this fix?
How did you test this?
I usually test with:
$ cd tools/testing/selftests/bpf/
$ sudo ./test_xdp_vlan_mode_generic.sh
But currently I get a build error on net-next in:
net-next/tools/testing/selftests/bpf/tools/build/bpftool/pid_iter.bpf.o
So, I could not run this test.
- -
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
LinkedIn: http://www.linkedin.com/in/brouer
On Sat, 15 Aug 2020 09:29:30 +0200
"Jason A. Donenfeld" <Jason@zx2c4.com> wrote:
> diff --git a/net/core/dev.c b/net/core/dev.c
> index 7df6c9617321..151f1651439f 100644
> --- a/net/core/dev.c
> +++ b/net/core/dev.c
> @@ -4676,6 +4676,7 @@ static u32 netif_receive_generic_xdp(struct sk_buff *skb,
> (orig_bcast != is_multicast_ether_addr_64bits(eth->h_dest))) {
> __skb_push(skb, ETH_HLEN);
> skb->protocol = eth_type_trans(skb, skb->dev);
> + __skb_pull(skb, ETH_HLEN);
> }
>
> switch (act) {
next prev parent reply other threads:[~2020-08-17 6:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-15 7:29 [PATCH net] net: xdp: pull ethernet header off packet after computing skb->protocol Jason A. Donenfeld
2020-08-16 22:29 ` David Miller
2020-08-17 6:01 ` Jesper Dangaard Brouer [this message]
2020-08-17 7:48 ` Jason A. Donenfeld
2020-08-17 18:48 ` David Miller
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=20200817080102.61e109cf@carbon \
--to=brouer@redhat.com \
--cc=Jason@zx2c4.com \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
/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).