1. 05 8月, 2005 1 次提交
    • D
      [PATCH] tcp: fix TSO sizing bugs · 846998ae
      David S. Miller 提交于
      MSS changes can be lost since we preemptively initialize the tso_segs count
      for an SKB before we %100 commit to sending it out.
      
      So, by the time we send it out, the tso_size information can be stale due
      to PMTU events.  This mucks up all of the logic in our send engine, and can
      even result in the BUG() triggering in tcp_tso_should_defer().
      
      Another problem we have is that we're storing the tp->mss_cache, not the
      SACK block normalized MSS, as the tso_size.  That's wrong too.
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      Cc: Herbert Xu <herbert@gondor.apana.org.au>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      846998ae
  2. 31 7月, 2005 4 次提交
  3. 29 7月, 2005 1 次提交
  4. 28 7月, 2005 6 次提交
  5. 27 7月, 2005 1 次提交
  6. 25 7月, 2005 2 次提交
  7. 23 7月, 2005 7 次提交
  8. 22 7月, 2005 1 次提交
    • R
      [NETFILTER]: ip_conntrack_expect_related must not free expectation · 4acdbdbe
      Rusty Russell 提交于
      If a connection tracking helper tells us to expect a connection, and
      we're already expecting that connection, we simply free the one they
      gave us and return success.
      
      The problem is that NAT helpers (eg. FTP) have to allocate the
      expectation first (to see what port is available) then rewrite the
      packet.  If that rewrite fails, they try to remove the expectation,
      but it was freed in ip_conntrack_expect_related.
      
      This is one example of a larger problem: having registered the
      expectation, the pointer is no longer ours to use.  Reference counting
      is needed for ctnetlink anyway, so introduce it now.
      
      To have a single "put" path, we need to grab the reference to the
      connection on creation, rather than open-coding it in the caller.
      Signed-off-by: NRusty Russell <rusty@rustcorp.com.au>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      4acdbdbe
  9. 20 7月, 2005 8 次提交
  10. 19 7月, 2005 8 次提交
  11. 13 7月, 2005 1 次提交
    • T
      [VLAN]: Fix early vlan adding leads to not functional device · f4637b55
      Tommy Christensen 提交于
      OK, I can see what's happening here. eth0 doesn't detect link-up until
      after a few seconds, so when the vlan interface is opened immediately
      after eth0 has been opened, it inherits the link-down state. Subsequently
      the vlan interface is never properly activated and are thus unable to
      transmit any packets.
      
      dev->state bits are not supposed to be manipulated directly. Something
      similar is probably needed for the netif_device_present() bit, although
      I don't know how this is meant to work for a virtual device.
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      f4637b55