linux/net/ipv4, branch v2.6.13

[FIB_TRIE]: Don't ignore negative results from fib_semantic_match

2005-08-24T05:06:09Z

When a semantic match occurs either success, not found or an error (for matching unreachable routes/blackholes) is returned. fib_trie ignores the errors and looks for a different matching route. Treat results other than "no match" as success and end lookup. Signed-off-by: Patrick McHardy Signed-off-by: David S. Miller

[TCP]: Document non-trivial locking path in tcp_v{4,6}_get_port().

2005-08-23T17:49:54Z

This trips up a lot of folks reading this code. Put an unlikely() around the port-exhaustion test for good measure. Signed-off-by: David S. Miller

[TCP]: Unconditionally clear TCP_NAGLE_PUSH in skb_entail().

2005-08-23T17:13:06Z

Intention of this bit is to force pushing of the existing send queue when TCP_CORK or TCP_NODELAY state changes via setsockopt(). But it's easy to create a situation where the bit never clears. For example, if the send queue starts empty: 1) set TCP_NODELAY 2) clear TCP_NODELAY 3) set TCP_CORK 4) do small write() The current code will leave TCP_NAGLE_PUSH set after that sequence. Unconditionally clearing the bit when new data is added via skb_entail() solves the problem. Signed-off-by: David S. Miller

[NETFILTER]: Fix HW checksum handling in ip_queue/ip6_queue

2005-08-23T17:10:35Z

The checksum needs to be filled in on output, after mangling a packet ip_summed needs to be reset. Signed-off-by: Patrick McHardy Signed-off-by: David S. Miller

[IPV4]: Fix negative timer loop with lots of ipv4 peers.

2005-08-23T17:10:15Z

From: Dave Johnson Found this bug while doing some scaling testing that created 500K inet peers. peer_check_expire() in net/ipv4/inetpeer.c isn't using inet_peer_gc_mintime correctly and will end up creating an expire timer with less than the minimum duration, and even zero/negative if enough active peers are present. If >65K peers, the timer will be less than inet_peer_gc_mintime, and with >70K peers, the timer duration will reach zero and go negative. The timer handler will continue to schedule another zero/negative timer in a loop until peers can be aged. This can continue for at least a few minutes or even longer if the peers remain active due to arriving packets while the loop is occurring. Bug is present in both 2.4 and 2.6. Same patch will apply to both just fine. Signed-off-by: Andrew Morton Signed-off-by: David S. Miller

[TCP]: Do TSO deferral even if tail SKB can go out now.

2005-08-23T17:09:27Z

If the tail SKB fits into the window, it is still benefitical to defer until the goal percentage of the window is available. This give the application time to feed more data into the send queue and thus results in larger TSO frames going out. Patch from Dmitry Yusupov . Signed-off-by: David S. Miller

[NETFILTER]: Fix HW checksum handling in TCPMSS target

2005-08-21T00:40:41Z

Most importantly, remove bogus BUG() in receive path. Signed-off-by: Patrick McHardy Signed-off-by: David S. Miller

[NETFILTER]: Fix HW checksum handling in ECN target

2005-08-21T00:39:15Z

Signed-off-by: Patrick McHardy Signed-off-by: David S. Miller

[NETFILTER]: Fix ECN target TCP marking

2005-08-21T00:38:40Z

An incorrect check made it bail out before doing anything. Signed-off-by: Patrick McHardy Signed-off-by: David S. Miller

[IPCOMP]: Fix false smp_processor_id warning

2005-08-18T21:36:59Z

This patch fixes a false-positive from debug_smp_processor_id(). The processor ID is only used to look up crypto_tfm objects. Any processor ID is acceptable here as long as it is one that is iterated on by for_each_cpu(). Signed-off-by: Herbert Xu Signed-off-by: David S. Miller