1. 22 Jul, 2008 1 commit
  2. 19 Jun, 2008 1 commit
    • Vlad Yasevich's avatar
      sctp: Follow security requirement of responding with 1 packet · 2e3216cd
      Vlad Yasevich authored
      RFC 4960, Section 11.4. Protection of Non-SCTP-Capable Hosts
      When an SCTP stack receives a packet containing multiple control or
      DATA chunks and the processing of the packet requires the sending of
      multiple chunks in response, the sender of the response chunk(s) MUST
      NOT send more than one packet.  If bundling is supported, multiple
      response chunks that fit into a single packet MAY be bundled together
      into one single response packet.  If bundling is not supported, then
      the sender MUST NOT send more than one response chunk and MUST
      discard all other responses.  Note that this rule does NOT apply to a
      SACK chunk, since a SACK chunk is, in itself, a response to DATA and
      a SACK does not require a response of more DATA.
      We implement this by not servicing our outqueue until we reach the end
      of the packet.  This enables maximum bundling.  We also identify
      'response' chunks and make sure that we only send 1 packet when sending
      such chunks.
      Signed-off-by: default avatarVlad Yasevich <vladislav.yasevich@hp.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
  3. 04 Jun, 2008 2 commits
  4. 17 Apr, 2008 1 commit
  5. 13 Apr, 2008 2 commits
  6. 06 Mar, 2008 1 commit
  7. 29 Feb, 2008 1 commit
  8. 07 Feb, 2008 1 commit
  9. 05 Feb, 2008 1 commit
  10. 28 Jan, 2008 1 commit
  11. 09 Nov, 2007 1 commit
    • Vlad Yasevich's avatar
      SCTP: Always flush the queue when uncorcking. · 7d54dc68
      Vlad Yasevich authored
      When the code calls uncork, trigger a queue flush, even
      if the queue was not corked.  Most callers that explicitely
      cork the queue will have additinal checks to see if they 
      corked it.  Callers who do not cork the queue expect packets
      to flow when they call uncork.
      The scneario that showcased this bug happend when we were not
      able to bundle DATA with outgoing COOKIE-ECHO.  As a result
      the data just sat in the outqueue and did not get transmitted.
      The application expected a response, but nothing happened.
      Signed-off-by: default avatarVlad Yasevich <vladislav.yasevich@hp.com>
  12. 07 Nov, 2007 2 commits
  13. 30 Aug, 2007 1 commit
  14. 26 Apr, 2007 1 commit
  15. 26 Feb, 2007 1 commit
    • Vlad Yasevich's avatar
      [SCTP]: Fix connection hang/slowdown with PR-SCTP · 8c4a2d41
      Vlad Yasevich authored
      The problem that this patch corrects happens when all of the following
      conditions are satisfisfied:
       1.  PR-SCTP is used and the timeout on the chunks is set below RTO.Max.
       2.  One of the paths on a multihomed associations is brought down.
      In this scenario, data will expire within the rto of the initial
      transmission and will never be retransmitted.  However this data still
      fills the send buffer and is counted against the association as outstanding
      data.  This causes any new data not to be sent and retransmission to not
      The fix is to discount the abandoned data from the outstanding count and
      peers rwnd estimation.  This allows new data to be sent and a retransmission
      timer restarted.  Even though this new data will most likely expire within
      the rto, the timer still counts as a strike against the transport and forces
      the FORWARD-TSN chunk to be retransmitted as well.
      Signed-off-by: default avatarVlad Yasevich <vladislav.yasevich@hp.com>
      Signed-off-by: default avatarSridhar Samudrala <sri@us.ibm.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
  16. 11 Feb, 2007 1 commit
  17. 03 Dec, 2006 2 commits
  18. 30 Sep, 2006 1 commit
  19. 22 Sep, 2006 1 commit
  20. 21 Jul, 2006 1 commit
  21. 18 Jun, 2006 1 commit
  22. 03 Feb, 2006 1 commit
  23. 09 Jul, 2005 1 commit
  24. 20 Jun, 2005 1 commit
  25. 16 Apr, 2005 1 commit
    • Linus Torvalds's avatar
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds authored
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      Let it rip!