[Intel-wired-lan] [net-next PATCH v3 00/17] Future-proof tunnel offload handlers

David Miller davem at davemloft.net
Tue Jun 21 08:22:11 UTC 2016


From: Tom Herbert <tom at herbertland.com>
Date: Mon, 20 Jun 2016 10:05:01 -0700

> Generally, this means it needs to at least match by local addresses
> and port for an unconnected/unbound socket, the source address for
> an unconnected/bound socket, a the full 4-tuple for a connected
> socket.

These lookup keys are all insufficient.

At the very least the network namespace must be in the lookup key as
well if you want to match "sockets".  And this is just the tip of the
iceberg in my opinion.

The namespace bypassing to me is the biggest flaw in the UDP tunnel
offloads.  That is creating real dangers right now.

But anyways, the vastness of the key is why we want to keep "sockets"
out of network cards, because proper support of "sockets" requires
access to information the card simply does not and should not have.


More information about the Intel-wired-lan mailing list