1. 13 Jun, 2008 3 commits
  2. 12 Jun, 2008 2 commits
    • Eilon Greenstein's avatar
      bnx2x: Updating the Maintainer · 24e3fcef
      Eilon Greenstein authored
      
      
      I would like to thank Eliezer Tamir for writing and maintaining the
      driver for the past two years. I will take over maintaining the bnx2x
      driver from now on.
      Signed-off-by: default avatarEilon Greenstein <eilong@broadcom.com>
      Signed-off-by: default avatarEliezer Tamir <eliezert@broadcom.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      24e3fcef
    • David S. Miller's avatar
      net: Eliminate flush_scheduled_work() calls while RTNL is held. · 4bb073c0
      David S. Miller authored
      
      
      If the RTNL is held when we invoke flush_scheduled_work() we could
      deadlock.  One such case is linkwatch, it is a work struct which tries
      to grab the RTNL semaphore.
      
      The most common case are net driver ->stop() methods.  The
      simplest conversion is to instead use cancel_{delayed_}work_sync()
      explicitly on the various work struct the driver uses.
      
      This is an OK transformation because these work structs are doing
      things like resetting the chip, restarting link negotiation, and so
      forth.  And if we're bringing down the device, we're about to turn the
      chip off and reset it anways.  So if we cancel a pending work event,
      that's fine here.
      
      Some drivers were working around this deadlock by using a msleep()
      polling loop of some sort, and those cases are converted to instead
      use cancel_{delayed_}work_sync() as well.
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      4bb073c0
  3. 11 Jun, 2008 3 commits
  4. 10 Jun, 2008 22 commits
  5. 09 Jun, 2008 9 commits
  6. 04 Jun, 2008 1 commit
    • James Chapman's avatar
      l2tp: Fix possible oops if transmitting or receiving when tunnel goes down · 24b95685
      James Chapman authored
      
      
      Some problems have been experienced in the field which cause an oops
      in the pppol2tp driver if L2TP tunnels fail while passing data.
      
      The pppol2tp driver uses private data that is referenced via the
      sk->sk_user_data of its UDP and PPPoL2TP sockets. This patch makes
      sure that the driver uses sock_hold() when it holds a reference to the
      sk pointer. This affects its sendmsg(), recvmsg(), getname(),
      [gs]etsockopt() and ioctl() handlers.
      
      Tested by ISP where problem was seen. System has been up 10 days with
      no oops since running this patch. Without the patch, an oops would
      occur every 1-2 days.
      
      Signed-off-by: James Chapman <jchapman@katalix.com> 
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      24b95685