1. 13 11月, 2008 4 次提交
  2. 04 11月, 2008 1 次提交
  3. 28 10月, 2008 1 次提交
  4. 10 10月, 2008 5 次提交
  5. 19 9月, 2008 4 次提交
  6. 16 8月, 2008 1 次提交
  7. 15 8月, 2008 4 次提交
  8. 19 7月, 2008 3 次提交
  9. 15 7月, 2008 6 次提交
  10. 20 6月, 2008 7 次提交
  11. 12 6月, 2008 1 次提交
    • D
      net: Eliminate flush_scheduled_work() calls while RTNL is held. · 4bb073c0
      David S. Miller 提交于
      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: NDavid S. Miller <davem@davemloft.net>
      4bb073c0
  12. 17 5月, 2008 3 次提交