1. 18 6月, 2008 1 次提交
    • E
      udp: sk_drops handling · cb61cb9b
      Eric Dumazet 提交于
      In commits 33c732c3 ([IPV4]: Add raw
      drops counter) and a92aa318 ([IPV6]:
      Add raw drops counter), Wang Chen added raw drops counter for
      /proc/net/raw & /proc/net/raw6
      
      This patch adds this capability to UDP sockets too (/proc/net/udp &
      /proc/net/udp6).
      
      This means that 'RcvbufErrors' errors found in /proc/net/snmp can be also
      be examined for each udp socket.
      
      # grep Udp: /proc/net/snmp
      Udp: InDatagrams NoPorts InErrors OutDatagrams RcvbufErrors SndbufErrors
      Udp: 23971006 75 899420 16390693 146348 0
      
      # cat /proc/net/udp
       sl  local_address rem_address   st tx_queue rx_queue tr tm->when retrnsmt  ---
      uid  timeout inode ref pointer drops
       75: 00000000:02CB 00000000:0000 07 00000000:00000000 00:00000000 00000000  ---
        0        0 2358 2 ffff81082a538c80 0
      111: 00000000:006F 00000000:0000 07 00000000:00000000 00:00000000 00000000  ---
        0        0 2286 2 ffff81042dd35c80 146348
      
      In this example, only port 111 (0x006F) was flooded by messages that
      user program could not read fast enough. 146348 messages were lost.
      Signed-off-by: NEric Dumazet <dada1@cosmosbay.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      cb61cb9b
  2. 17 6月, 2008 3 次提交
  3. 15 6月, 2008 1 次提交
  4. 12 6月, 2008 1 次提交
  5. 05 6月, 2008 3 次提交
  6. 12 4月, 2008 1 次提交
    • B
      [IPv6]: Change IPv6 unspecified destination address to ::1 for raw and un-connected sockets · 876c7f41
      Brian Haley 提交于
      This patch fixes a difference between IPv4 and IPv6 when sending packets
      to the unspecified address (either 0.0.0.0 or ::) when using raw or
      un-connected UDP sockets.  There are two cases where IPv6 either fails
      to send anything, or sends with the destination address set to ::.  For
      example:
      
      --> ping -c1 0.0.0.0
      PING 0.0.0.0 (127.0.0.1) 56(84) bytes of data.
      64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.032 ms
      
      --> ping6 -c1 ::
      PING ::(::) 56 data bytes
      ping: sendmsg: Invalid argument
      
      Doing a sendto("0.0.0.0") reveals:
      
      10:55:01.495090 IP localhost.32780 > localhost.7639: UDP, length 100
      
      Doing a sendto("::") reveals:
      
      10:56:13.262478 IP6 fe80::217:8ff:fe7d:4718.32779 > ::.7639: UDP, length 100
      
      If you issue a connect() first in the UDP case, it will be sent to ::1,
      similar to what happens with TCP.
      
      This restores the BSD-ism.
      Signed-off-by: NBrian Haley <brian.haley@hp.com>
      Signed-off-by: NYOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
      876c7f41
  7. 29 3月, 2008 4 次提交
  8. 26 3月, 2008 3 次提交
  9. 25 3月, 2008 1 次提交
  10. 23 3月, 2008 1 次提交
  11. 21 3月, 2008 1 次提交
  12. 08 3月, 2008 1 次提交
  13. 07 3月, 2008 1 次提交
    • D
      [UDP]: Revert udplite and code split. · db8dac20
      David S. Miller 提交于
      This reverts commit db1ed684 ("[IPV6]
      UDP: Rename IPv6 UDP files."), commit
      8be8af8f ("[IPV4] UDP: Move
      IPv4-specific bits to other file.") and commit
      e898d4db ("[UDP]: Allow users to
      configure UDP-Lite.").
      
      First, udplite is of such small cost, and it is a core protocol just
      like TCP and normal UDP are.
      
      We spent enormous amounts of effort to make udplite share as much code
      with core UDP as possible.  All of that work is less valuable if we're
      just going to slap a config option on udplite support.
      
      It is also causing build failures, as reported on linux-next, showing
      that the changeset was not tested very well.  In fact, this is the
      second build failure resulting from the udplite change.
      
      Finally, the config options provided was a bool, instead of a modular
      option.  Meaning the udplite code does not even get build tested
      by allmodconfig builds, and furthermore the user is not presented
      with a reasonable modular build option which is particularly needed
      by distribution vendors.
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      db8dac20
  14. 04 3月, 2008 2 次提交
  15. 01 2月, 2008 1 次提交
  16. 29 1月, 2008 11 次提交
  17. 07 11月, 2007 2 次提交
  18. 16 10月, 2007 1 次提交
  19. 11 10月, 2007 1 次提交