Skip to content

cloud-kernel
cloud-kernel

openanolis / cloud-kernel
12 个月 前同步成功

通知 152
Star 36
Fork 7
cloud-kernel
cloud-kernel

体验新版 GitCode，发现更多精彩内容 >>

切换分支/标签
  1. 14 6月, 2007 2 次提交
  3. 26 4月, 2007 10 次提交
  5. 11 2月, 2007 1 次提交
  7. 03 12月, 2006 6 次提交
  9. 31 10月, 2006 2 次提交
  11. 30 9月, 2006 2 次提交
  13. 23 9月, 2006 2 次提交
  15. 18 6月, 2006 2 次提交
  17. 20 5月, 2006 2 次提交
    • V
      [SCTP]: A better solution to fix the race between sctp_peeloff() and · 61c9fed4
      由 Vladislav Yasevich 提交于 
      sctp_rcv().

The goal is to hold the ref on the association/endpoint throughout the
state-machine process.  We accomplish like this:

  /* ref on the assoc/ep is taken during lookup */

  if owned_by_user(sk)
 	sctp_add_backlog(skb, sk);
  else
 	inqueue_push(skb, sk);

  /* drop the ref on the assoc/ep */

However, in sctp_add_backlog() we take the ref on assoc/ep and hold it
while the skb is on the backlog queue.  This allows us to get rid of the
sock_hold/sock_put in the lookup routines.

Now sctp_backlog_rcv() needs to account for potential association move.
In the unlikely event that association moved, we need to retest if the
new socket is locked by user.  If we don't this, we may have two packets
racing up the stack toward the same socket and we can't deal with it.
If the new socket is still locked, we'll just add the skb to its backlog
continuing to hold the ref on the association.  This get's rid of the
need to move packets from one backlog to another and it also safe in
case new packets arrive on the same backlog queue.

The last step, is to lock the new socket when we are moving the
association to it.  This is needed in case any new packets arrive on
the association when it moved.  We want these to go to the backlog since
we would like to avoid the race between this new packet and a packet
that may be sitting on the backlog queue of the old socket toward the
same association.
Signed-off-by: NVladislav Yasevich <vladislav.yasevich@hp.com>
Signed-off-by: NSridhar Samudrala <sri@us.ibm.com>
      61c9fed4
    • S
      [SCTP]: Set sk_err so that poll wakes up after a non-blocking connect failure. · 8de8c873
      由 Sridhar Samudrala 提交于 
      Also fix some other cases where sk_err is not set for 1-1 style sockets.
Signed-off-by: NSridhar Samudrala <sri@us.ibm.com>
      8de8c873
  19. 25 3月, 2006 1 次提交
    • H
      [SCTP]: Fix up sctp_rcv return value · 2babf9da
      由 Herbert Xu 提交于 
      I was working on the ipip/xfrm problem and as usual I get side-tracked by
other problems.

As part of an attempt to change the IPv4 protocol handler calling
convention I found that SCTP violated the existing convention.

It's returning non-zero values after freeing the skb.  This is doubly bad
as 1) the skb gets resubmitted; 2) the return value is interpreted as a
protocol number.

This patch changes those return values to zero.

IPv6 doesn't suffer from this problem because it uses a positive return
value as an indication for resubmission.  So the only effect of this patch
there is to increment the IPSTATS_MIB_INDELIVERS counter which IMHO is
the right thing to do.
Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      2babf9da
  21. 18 1月, 2006 3 次提交
  23. 08 1月, 2006 1 次提交
  25. 04 1月, 2006 1 次提交
  27. 12 11月, 2005 1 次提交
  29. 30 8月, 2005 1 次提交
  31. 19 7月, 2005 1 次提交
  33. 09 7月, 2005 1 次提交
  35. 21 6月, 2005 1 次提交