diff options
| author | Jesse Brandeburg <jesse.brandeburg@intel.com> | 2010-09-22 18:22:42 +0000 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2010-09-23 14:33:38 -0700 |
| commit | 338c15e470d818f215d651505dc169d4e92f36a4 (patch) | |
| tree | 90153c4c54f0b43ed48700a396db695d232f1878 /net/rfkill | |
| parent | 5cf42fcda0fdddfe7f5ea8629cb7b820bf7e91ab (diff) | |
| download | linux-338c15e470d818f215d651505dc169d4e92f36a4.tar.bz2 | |
e1000: fix occasional panic on unload
Net drivers in general have an issue where timers fired
by mod_timer or work threads with schedule_work are running
outside of the rtnl_lock.
With no other lock protection these routines are vulnerable
to races with driver unload or reset paths.
The longer term solution to this might be a redesign with
safer locks being taken in the driver to guarantee no
reentrance, but for now a safe and effective fix is
to take the rtnl_lock in these routines.
Signed-off-by: Jesse Brandeburg <jesse.brandeburg@intel.com>
Tested-by: Jeff Pieper <jeffrey.e.pieper@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/rfkill')
0 files changed, 0 insertions, 0 deletions