net: rename skb_gso_validate_mtu -> skb_gso_validate_network_len
If you take a GSO skb, and split it into packets, will the network length (L3 headers + L4 headers + payload) of those packets be small enough to fit within a given MTU? skb_gso_validate_mtu gives you the answer to that question. However, we recently added to add a way to validate the MAC length of a split GSO skb (L2+L3+L4+payload), and the names get confusing, so rename skb_gso_validate_mtu to skb_gso_validate_network_len Signed-off-by:Daniel Axtens <dja@axtens.net> Reviewed-by:
Marcelo Ricardo Leitner <marcelo.leitner@gmail.com> Signed-off-by:
David S. Miller <davem@davemloft.net>
Showing
- include/linux/skbuff.h 1 addition, 1 deletioninclude/linux/skbuff.h
- net/core/skbuff.c 6 additions, 5 deletionsnet/core/skbuff.c
- net/ipv4/ip_forward.c 1 addition, 1 deletionnet/ipv4/ip_forward.c
- net/ipv4/ip_output.c 1 addition, 1 deletionnet/ipv4/ip_output.c
- net/ipv4/netfilter/nf_flow_table_ipv4.c 1 addition, 1 deletionnet/ipv4/netfilter/nf_flow_table_ipv4.c
- net/ipv6/ip6_output.c 1 addition, 1 deletionnet/ipv6/ip6_output.c
- net/ipv6/netfilter/nf_flow_table_ipv6.c 1 addition, 1 deletionnet/ipv6/netfilter/nf_flow_table_ipv6.c
- net/mpls/af_mpls.c 1 addition, 1 deletionnet/mpls/af_mpls.c
- net/xfrm/xfrm_device.c 1 addition, 1 deletionnet/xfrm/xfrm_device.c
Loading
Please register or sign in to comment