1. 19 6月, 2005 10 次提交
  2. 09 6月, 2005 2 次提交
  3. 07 6月, 2005 1 次提交
  4. 30 5月, 2005 4 次提交
  5. 13 5月, 2005 1 次提交
    • [PATCH] Wireless Extensions 18 (aka WPA) · fff9cfd9
      提交于
        
              This is version 18 of the Wireless Extensions. The main change
        is that it adds all the necessary APIs for WPA and WPA2 support. This
        work was entirely done by Jouni Malinen, so let's thank him for both
        his hard work and deep expertise on the subject ;-)
              This APIs obviously doesn't do much by itself and works in
        concert with driver support (Jouni already sent you the HostAP
        changes) and userspace (Jouni is updating wpa_supplicant). This is
        also orthogonal with the ongoing work on in-kernel IEEE support (but
        potentially useful).
              The patch is attached, tested with 2.6.11. Normally, I would
        ask you to push that directly in the kernel (99% of the patch has been
        on my web page for ages and it does not affect non-WPA stuff), but
        Jouni convinced me that it should bake a few weeks in wireless-2.6
        first, so that other driver maintainers can get up to speed with it.
      Signed-off-by: NJeff Garzik <jgarzik@pobox.com>
      fff9cfd9
  6. 06 5月, 2005 2 次提交
  7. 04 5月, 2005 8 次提交
    • P
    • P
      e4f8ab00
    • T
      [NET]: Disable queueing when carrier is lost. · cacaddf5
      Tommy S. Christensen 提交于
      Some network drivers call netif_stop_queue() when detecting loss of
      carrier. This leads to packets being queued up at the qdisc level for
      an unbound period of time. In order to prevent this effect, the core
      networking stack will now cease to queue packets for any device, that
      is operationally down (i.e. the queue is flushed and disabled).
      Signed-off-by: NTommy S. Christensen <tommy.christensen@tpack.net>
      Acked-by: NHerbert Xu <herbert@gondor.apana.org.au>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      cacaddf5
    • D
      [XFRM/RTNETLINK]: Decrement qlen properly in {xfrm_,rt}netlink_rcv(). · 0f4821e7
      David S. Miller 提交于
      If we free up a partially processed packet because it's
      skb->len dropped to zero, we need to decrement qlen because
      we are dropping out of the top-level loop so it will do
      the decrement for us.
      
      Spotted by Herbert Xu.
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      0f4821e7
    • D
      [NETLINK]: Fix infinite loops in synchronous netlink changes. · 09e14305
      David S. Miller 提交于
      The qlen should continue to decrement, even if we
      pop partially processed SKBs back onto the receive queue.
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      09e14305
    • H
      [NETLINK]: Synchronous message processing. · 2a0a6ebe
      Herbert Xu 提交于
      Let's recap the problem.  The current asynchronous netlink kernel
      message processing is vulnerable to these attacks:
      
      1) Hit and run: Attacker sends one or more messages and then exits
      before they're processed.  This may confuse/disable the next netlink
      user that gets the netlink address of the attacker since it may
      receive the responses to the attacker's messages.
      
      Proposed solutions:
      
      a) Synchronous processing.
      b) Stream mode socket.
      c) Restrict/prohibit binding.
      
      2) Starvation: Because various netlink rcv functions were written
      to not return until all messages have been processed on a socket,
      it is possible for these functions to execute for an arbitrarily
      long period of time.  If this is successfully exploited it could
      also be used to hold rtnl forever.
      
      Proposed solutions:
      
      a) Synchronous processing.
      b) Stream mode socket.
      
      Firstly let's cross off solution c).  It only solves the first
      problem and it has user-visible impacts.  In particular, it'll
      break user space applications that expect to bind or communicate
      with specific netlink addresses (pid's).
      
      So we're left with a choice of synchronous processing versus
      SOCK_STREAM for netlink.
      
      For the moment I'm sticking with the synchronous approach as
      suggested by Alexey since it's simpler and I'd rather spend
      my time working on other things.
      
      However, it does have a number of deficiencies compared to the
      stream mode solution:
      
      1) User-space to user-space netlink communication is still vulnerable.
      
      2) Inefficient use of resources.  This is especially true for rtnetlink
      since the lock is shared with other users such as networking drivers.
      The latter could hold the rtnl while communicating with hardware which
      causes the rtnetlink user to wait when it could be doing other things.
      
      3) It is still possible to DoS all netlink users by flooding the kernel
      netlink receive queue.  The attacker simply fills the receive socket
      with a single netlink message that fills up the entire queue.  The
      attacker then continues to call sendmsg with the same message in a loop.
      
      Point 3) can be countered by retransmissions in user-space code, however
      it is pretty messy.
      
      In light of these problems (in particular, point 3), we should implement
      stream mode netlink at some point.  In the mean time, here is a patch
      that implements synchronous processing.  
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      2a0a6ebe
    • T
      [RTNETLINK] Cleanup rtnetlink_link tables · db46edc6
      Thomas Graf 提交于
      Converts remaining rtnetlink_link tables to use c99 designated
      initializers to make greping a little bit easier.
      Signed-off-by: NThomas Graf <tgraf@suug.ch>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      db46edc6
    • T
      [RTNETLINK] Fix & cleanup rtm_min/rtm_max · f90a0a74
      Thomas Graf 提交于
      Converts rtm_min and rtm_max arrays to use c99 designated
      initializers for easier insertion of new message families.
      RTM_GETMULTICAST and RTM_GETANYCAST did not have the minimal
      message size specified which means that the netlink message
      was parsed for routing attributes starting from the header.
      Adds the proper minimal message sizes for these messages
      (netlink header + common rtnetlink header) to fix this issue.
      Signed-off-by: NThomas Graf <tgraf@suug.ch>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      f90a0a74
  8. 01 5月, 2005 4 次提交
  9. 29 4月, 2005 1 次提交
  10. 26 4月, 2005 2 次提交
    • A
      [NET]: kill gratitious includes of major.h · 5523662c
      Al Viro 提交于
      	A lot of places in there are including major.h for no reason
      whatsoever.  Removed.  And yes, it still builds.
      
      	The history of that stuff is often amusing.  E.g. for net/core/sock.c
      the story looks so, as far as I've been able to reconstruct it: we used to
      need major.h in net/socket.c circa 1.1.early.  In 1.1.13 that need had
      disappeared, along with register_chrdev(SOCKET_MAJOR, "socket", &net_fops)
      in sock_init().  Include had not.  When 1.2 -> 1.3 reorg of net/* had moved
      a lot of stuff from net/socket.c to net/core/sock.c, this crap had followed...
      Signed-off-by: NAl Viro <viro@parcelfarce.linux.theplanet.co.uk>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      5523662c
    • A
      [PATCH] kill gratitious includes of major.h under net/* · b453257f
      Al Viro 提交于
      A lot of places in there are including major.h for no reason whatsoever.
      Removed.  And yes, it still builds. 
      
      The history of that stuff is often amusing.  E.g.  for net/core/sock.c
      the story looks so, as far as I've been able to reconstruct it: we used
      to need major.h in net/socket.c circa 1.1.early.  In 1.1.13 that need
      had disappeared, along with register_chrdev(SOCKET_MAJOR, "socket",
      &net_fops) in sock_init().  Include had not.  When 1.2 -> 1.3 reorg of
      net/* had moved a lot of stuff from net/socket.c to net/core/sock.c,
      this crap had followed... 
      Signed-off-by: NAl Viro <viro@parcelfarce.linux.theplanet.co.uk>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      b453257f
  11. 25 4月, 2005 1 次提交
  12. 22 4月, 2005 1 次提交
  13. 20 4月, 2005 3 次提交