| commit | 4ada424db196c78746fec255d493cacb1c9feddf | |
| author | Luis R. Rodriguez <lrodriguez@atheros.com> | |
| Fri, 14 Nov 2008 22:44:22 +0000 (14 14:44 -0800) | ||
| committer | John W. Linville <linville@tuxdriver.com> | |
| Tue, 25 Nov 2008 21:41:40 +0000 (25 16:41 -0500) | ||
| tree | 8fc36e480aa46b8cfebd6aff95b8d1a40b910f33 | treesnapshot (tar.gz zip) |
| parent | 4d3601b234a51fdd268c8ef8068d239e26dd7ef1 | commitdiff |
mac80211: don't assume driver has been attached on registration
mac80211's ieee80211_register_hw() is often called within the
probe path so it cannot assume the device's driver structure
has been attached yet so to create a workqueue instead of
using driver->name use the wiphy's phy%d name. The name doesn't
really matter anyway.
This should fix sporadic oopses found when we race to beat the
driver pointer setting. Not even sure how this was working properly.
http://www.kerneloops.org/search.php?search=ieee80211_register_hw
Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
Acked-by: Johannes Berg <johannes@sipsolutions.net>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
mac80211's ieee80211_register_hw() is often called within the
probe path so it cannot assume the device's driver structure
has been attached yet so to create a workqueue instead of
using driver->name use the wiphy's phy%d name. The name doesn't
really matter anyway.
This should fix sporadic oopses found when we race to beat the
driver pointer setting. Not even sure how this was working properly.
http://www.kerneloops.org/search.php?search=ieee80211_register_hw
Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
Acked-by: Johannes Berg <johannes@sipsolutions.net>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
| net/mac80211/main.c | diffblobblamehistory |