gtp: fixes and support multiple VRF's per GTP socket
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v2 Latest18 patches 2 repliesIn review
- v117 patches 0 repliesSuperseded
Changes in v2 from the cover letter
* the socket that is hold by the pdp context has to be release in a rcu callback. Otherwise a stray GTP rx could end uo with an invalid socket.
* accessing the skb->sk field in gtp_rx is invalid, that field has no been populated at that point
* add dst_cache to speed up the routing
Patches in v2 No applies recorded yet
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.
Cover letter [PATCH v2 00/18] gtp: fixes and support multiple VRF's per GTP socket
The current linking of GTP network devices and GTP enabled sockets means that we can not have multiple VRF's per GTP socket. This series seperates the sockets from network device, makes sockets attached to GTP network device optional and adds a API function to enable GTP encapsulation on socket without having to create a new GTP device.
It is still possible to use the old API. The network device attached socket is then used when no socket is specified on PDP context creation.
During that work some smaller problems where found and fixes for them are included.
v2 changes:
* the socket that is hold by the pdp context has to be release in a rcu callback. Otherwise a stray GTP rx could end uo with an invalid socket.
* accessing the skb->sk field in gtp_rx is invalid, that field has no been populated at that point
* add dst_cache to speed up the routing
Regards
Andreas