This project is mirrored from The repository failed to update .
Repository mirroring has been paused due to too many failed attempts, and can be resumed by a project maintainer.
Last successful update .
  1. 02 Dec, 2009 1 commit
  2. 18 Nov, 2009 1 commit
  3. 06 Nov, 2009 1 commit
  4. 12 Oct, 2009 1 commit
    • Neil Horman (CI test user)'s avatar
      net: Generalize socket rx gap / receive queue overflow cmsg · 3b885787
      Neil Horman (CI test user) authored
      Create a new socket level option to report number of queue overflows
      Recently I augmented the AF_PACKET protocol to report the number of frames lost
      on the socket receive queue between any two enqueued frames.  This value was
      exported via a SOL_PACKET level cmsg.  AFter I completed that work it was
      requested that this feature be generalized so that any datagram oriented socket
      could make use of this option.  As such I've created this patch, It creates a
      new SOL_SOCKET level option called SO_RXQ_OVFL, which when enabled exports a
      SOL_SOCKET level cmsg that reports the nubmer of times the sk_receive_queue
      overflowed between any two given frames.  It also augments the AF_PACKET
      protocol to take advantage of this new feature (as it previously did not touch
      sk->sk_drops, which this patch uses to record the overflow count).  Tested
      successfully by me.
      1) Unlike my previous patch, this patch simply records the sk_drops value, which
      is not a number of drops between packets, but rather a total number of drops.
      Deltas must be computed in user space.
      2) While this patch currently works with datagram oriented protocols, it will
      also be accepted by non-datagram oriented protocols. I'm not sure if thats
      agreeable to everyone, but my argument in favor of doing so is that, for those
      protocols which aren't applicable to this option, sk_drops will always be zero,
      and reporting no drops on a receive queue that isn't used for those
      non-participating protocols seems reasonable to me.  This also saves us having
      to code in a per-protocol opt in mechanism.
      3) This applies cleanly to net-next assuming that commit
      97775007 (my af packet cmsg patch) is reverted
      Signed-off-by: Neil Horman (CI test user)'s avatarNeil Horman <>
      Signed-off-by: default avatarEric Dumazet <>
      Signed-off-by: default avatarDavid S. Miller <>
  5. 07 Oct, 2009 1 commit
  6. 02 Sep, 2009 2 commits
  7. 18 Jun, 2009 1 commit
  8. 27 Feb, 2009 1 commit
  9. 26 Jan, 2009 1 commit
  10. 26 Nov, 2008 14 commits
  11. 07 Nov, 2008 1 commit
  12. 31 Oct, 2008 1 commit
    • Alexey Dobriyan's avatar
      key: fix setkey(8) policy set breakage · 920da692
      Alexey Dobriyan authored
      Steps to reproduce:
      	#/usr/sbin/setkey -f
      	add ah 24500 -A hmac-md5 "1234567890123456";
      	add esp 24501 -E 3des-cbc "123456789012123456789012";
      	spdadd any -P out ipsec
      setkey: invalid keymsg length
      Policy dump will bail out with the same message after that.
      -recv(4, "\2\16\0\0\32\0\3\0\0\0\0\0\37\r\0\0\3\0\5\0\377 \0\0\2\0\0\0\300\250\0*\0"..., 32768, 0) = 208
      +recv(4, "\2\16\0\0\36\0\3\0\0\0\0\0H\t\0\0\3\0\5\0\377 \0\0\2\0\0\0\300\250\0*\0"..., 32768, 0) = 208
      Signed-off-by: default avatarAlexey Dobriyan <>
      Signed-off-by: default avatarDavid S. Miller <>
  13. 10 Oct, 2008 1 commit
  14. 05 Oct, 2008 1 commit
  15. 01 Oct, 2008 2 commits
  16. 26 Jul, 2008 1 commit
  17. 11 Jun, 2008 4 commits
  18. 10 Jun, 2008 1 commit
  19. 21 May, 2008 1 commit
  20. 28 Apr, 2008 1 commit
  21. 25 Apr, 2008 1 commit
  22. 22 Apr, 2008 1 commit
    • Herbert Xu's avatar
      [IPSEC]: Fix catch-22 with algorithm IDs above 31 · c5d18e98
      Herbert Xu authored
      As it stands it's impossible to use any authentication algorithms
      with an ID above 31 portably.  It just happens to work on x86 but
      fails miserably on ppc64.
      The reason is that we're using a bit mask to check the algorithm
      ID but the mask is only 32 bits wide.
      After looking at how this is used in the field, I have concluded
      that in the long term we should phase out state matching by IDs
      because this is made superfluous by the reqid feature.  For current
      applications, the best solution IMHO is to allow all algorithms when
      the bit masks are all ~0.
      The following patch does exactly that.
      This bug was identified by IBM when testing on the ppc64 platform
      using the NULL authentication algorithm which has an ID of 251.
      Signed-off-by: default avatarHerbert Xu <>
      Signed-off-by: default avatarDavid S. Miller <>