From: David Miller <email@example.com>
Cc: firstname.lastname@example.org, email@example.com,
firstname.lastname@example.org, email@example.com, firstname.lastname@example.org,
email@example.com, firstname.lastname@example.org, email@example.com,
Subject: Re: [PATCH net v6] net: xdp: account for layer 3 packets in generic skb handler
Date: Wed, 19 Aug 2020 16:22:47 -0700 (PDT) [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
Date: Sat, 15 Aug 2020 09:41:02 +0200
> A user reported that packets from wireguard were possibly ignored by XDP
> . Another user reported that modifying packets from layer 3
> interfaces results in impossible to diagnose drops.
Jason this really is a minefield.
If you make everything look like ethernet, even when it isn't, that is
a huge pile of worms.
If the XDP program changes the fake ethernet header's protocol field,
what will update the next protocol field in the wireguard
encapsulation headers so that it matches?
How do you support pushing VLAN headers as some XDP programs do? What
will undo the fake ethernet header and push the VLAN header into the
right place, and set it's next protocol field correctly?
And so on, and so forth...
With so many unanswered questions and unclear semantics the only
reasonable approach right now is to reject L3 devices from having XDP
programs attached at this time.
Arguably the best answer is the hardest answer, which is that we
expose device protocols and headers exactly how they are and don't try
to pretend they are something else. But it really means that XDP
programs have to be written targetted to the attach point device type.
And it also means we need a way to update skb->protocol properly,
handle the pushing of new headers, etc.
In short, you can't just push a fake ethernet header and expect
everything to just work.
next prev parent reply other threads:[~2020-08-19 23:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-13 19:58 [PATCH net v4] net: xdp: account for layer 3 packets in generic skb handler Jason A. Donenfeld
2020-08-13 21:01 ` Jakub Kicinski
2020-08-14 6:56 ` Jason A. Donenfeld
2020-08-14 7:30 ` [PATCH net v5] " Jason A. Donenfeld
2020-08-14 20:55 ` David Miller
2020-08-14 20:57 ` Jason A. Donenfeld
2020-08-15 7:41 ` [PATCH net v6] " Jason A. Donenfeld
2020-08-19 7:07 ` Jesper Dangaard Brouer
2020-08-19 23:22 ` David Miller [this message]
2020-08-20 9:13 ` Jason A. Donenfeld
2020-08-20 18:55 ` David Miller
2020-08-20 20:29 ` Jason A. Donenfeld
2020-08-14 15:31 ` [PATCH net v4] " Jakub Kicinski
2020-08-14 21:04 ` Jason A. Donenfeld
2020-08-14 21:26 ` David Miller
2020-08-15 7:54 ` Jason A. Donenfeld
2020-08-14 21:14 ` David Miller
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).