summaryrefslogtreecommitdiff
path: root/net/802
diff options
context:
space:
mode:
authorDavid S. Miller <davem@davemloft.net>2012-06-15 14:54:11 -0700
committerDavid S. Miller <davem@davemloft.net>2012-06-15 14:54:11 -0700
commit81aded24675ebda5de8a68843250ad15584ac38a (patch)
tree84f7bd5cf86cf010394de92efd5e4c5b636b3d20 /net/802
parent36393395536064e483b73d173f6afc103eadfbc4 (diff)
downloadlinux-3.10-81aded24675ebda5de8a68843250ad15584ac38a.tar.gz
linux-3.10-81aded24675ebda5de8a68843250ad15584ac38a.tar.bz2
linux-3.10-81aded24675ebda5de8a68843250ad15584ac38a.zip
ipv6: Handle PMTU in ICMP error handlers.
One tricky issue on the ipv6 side vs. ipv4 is that the ICMP callouts to handle the error pass the 32-bit info cookie in network byte order whereas ipv4 passes it around in host byte order. Like the ipv4 side, we have two helper functions. One for when we have a socket context and one for when we do not. ip6ip6 tunnels are not handled here, because they handle PMTU events by essentially relaying another ICMP packet-too-big message back to the original sender. This patch allows us to get rid of rt6_do_pmtu_disc(). It handles all kinds of situations that simply cannot happen when we do the PMTU update directly using a fully resolved route. In fact, the "plen == 128" check in ip6_rt_update_pmtu() can very likely be removed or changed into a BUG_ON() check. We should never have a prefixed ipv6 route when we get there. Another piece of strange history here is that TCP and DCCP, unlike in ipv4, never invoke the update_pmtu() method from their ICMP error handlers. This is incredibly astonishing since this is the context where we have the most accurate context in which to make a PMTU update, namely we have a fully connected socket and associated cached socket route. Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/802')
0 files changed, 0 insertions, 0 deletions