linux-stable.git/include/net/route.h, branch linux-3.1.y

ipv4: Pass explicit destination address to rt_bind_peer().

2011-05-18T22:42:43+00:00

Signed-off-by: David S. Miller

ipv4: Pass explicit destination address to rt_get_peer().

2011-05-18T22:38:54+00:00

This will next trickle down to rt_bind_peer().

Signed-off-by: David S. Miller

ipv4: Remove route key identity dependencies in ip_rt_get_source().

2011-05-13T21:29:41+00:00

Pass in the sk_buff so that we can fetch the necessary keys from
the packet header when working with input routes.

Signed-off-by: David S. Miller

ipv4: Kill rt->rt_{src, dst} usage in IP GRE tunnels.

2011-05-04T19:55:07+00:00

First, make callers pass on-stack flowi4 to ip_route_output_gre()
so they can get at the fully resolved flow key.

Next, use that in ipgre_tunnel_xmit() to avoid the need to use
rt->rt_{dst,src}.

Signed-off-by: David S. Miller

ipv4: Make caller provide on-stack flow key to ip_route_output_ports().

2011-05-04T03:25:42+00:00

Signed-off-by: David S. Miller

ipv4: Renamt struct rtable's rt_tos to rt_key_tos.

2011-05-04T02:45:15+00:00

To more accurately reflect that it is purely a routing
cache lookup key and is used in no other context.

Signed-off-by: David S. Miller

ipv4: Remove now superfluous code in ip_route_connect().

2011-04-29T06:13:17+00:00

Now that output route lookups update the flow with
source address et al. selections, the fl4->{saddr,daddr}
assignments here are no longer necessary.

Signed-off-by: David S. Miller

ipv4: Use caller's on-stack flowi as-is in output route lookups.

2011-04-29T05:26:00+00:00

Signed-off-by: David S. Miller

ipv4: Kill RTO_CONN.

2011-04-27T20:59:05+00:00

It's not used by anything in the kernel, and defined in net/route.h so
never exported to userspace.

Therefore we can safely remove it.

Signed-off-by: David S. Miller

ipv4: Sanitize and simplify ip_route_{connect,newports}()

2011-04-27T20:59:04+00:00

These functions are used together as a unit for route resolution
during connect().  They address the chicken-and-egg problem that
exists when ports need to be allocated during connect() processing,
yet such port allocations require addressing information from the
routing code.

It's currently more heavy handed than it needs to be, and in
particular we allocate and initialize a flow object twice.

Let the callers provide the on-stack flow object.  That way we only
need to initialize it once in the ip_route_connect() call.

Later, if ip_route_newports() needs to do anything, it re-uses that
flow object as-is except for the ports which it updates before the
route re-lookup.

Also, describe why this set of facilities are needed and how it works
in a big comment.

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