linux-stable.git/include/net/ip6_route.h, branch linux-3.8.y

ipv6: export IP6_RT_PRIO_* to userland

2012-11-16T06:47:40+00:00

The kernel uses some default metric when routes are managed. For example, a
static route added with a metric set to 0 is inserted in the kernel with
metric 1024 (IP6_RT_PRIO_USER).
It is useful for routing daemons to know these values, to be able to set routes
without interfering with what the kernel does.

Signed-off-by: Nicolas Dichtel 
Signed-off-by: David S. Miller

ipv6: fix inet6_csk_xmit()

2012-07-18T15:59:58+00:00

We should provide to inet6_csk_route_socket a struct flowi6 pointer,
so that net6_csk_xmit() works correctly instead of sending garbage.

Also add some consts

Signed-off-by: Eric Dumazet 
Reported-by: Yuchung Cheng 
Cc: Neal Cardwell 
Signed-off-by: David S. Miller

ipv6: Use icmpv6_notify() to propagate redirect, instead of rt6_redirect().

2012-07-12T07:33:37+00:00

And delete rt6_redirect(), since it is no longer used.

Signed-off-by: David S. Miller

ipv6: Add ip6_redirect() and ip6_sk_redirect() helper functions.

2012-07-12T07:08:07+00:00

Signed-off-by: David S. Miller

ipv6: Move bulk of redirect handling into rt6_redirect().

2012-07-12T06:43:53+00:00

This sets things up so that we can have the protocol error handlers
call down into the ipv6 route code for redirects just as ipv4 already
does.

Signed-off-by: David S. Miller

ipv6: Handle PMTU in ICMP error handlers.

2012-06-15T21:54:11+00:00

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

inet: Fix BUG triggered by __rt{,6}_get_peer().

2012-06-11T22:52:29+00:00

If no peer actually gets attached (either because create is zero or
the peer allocation fails) we'll trigger a BUG because we
unconditionally do an rt{,6}_peer_ptr() afterwards.

Fix this by guarding it with the proper check.

Signed-off-by: David S. Miller

inet: Hide route peer accesses behind helpers.

2012-06-11T09:08:47+00:00

We encode the pointer(s) into an unsigned long with one state bit.

The state bit is used so we can store the inetpeer tree root to use
when resolving the peer later.

Later the peer roots will be per-FIB table, and this change works to
facilitate that.

Signed-off-by: David S. Miller

inet: Create and use rt{,6}_get_peer_create().

2012-06-09T06:24:18+00:00

There's a lot of places that open-code rt{,6}_get_peer() only because
they want to set 'create' to one.  So add an rt{,6}_get_peer_create()
for their sake.

There were also a few spots open-coding plain rt{,6}_get_peer() and
those are transformed here as well.

Signed-off-by: David S. Miller

ipv6: bool/const conversions phase2

2012-05-19T05:08:16+00:00

Mostly bool conversions, some inline removals and const additions.

Signed-off-by: Eric Dumazet 
Signed-off-by: David S. Miller