Sander spotted that regulatory requests get stalled when cfg80211 is built-in. This issue is hit since regulatory requests only trigger a udev rule to run CRDA when being processed and if cfg80211 is built-in the udev rule that kicks CRDA could end up doing nothing as the filesystem path that has CRDA may not be mounted yet. This series of patches addresses this situation by allowing us to reprocess the last pending regulatory request. We add support for that by first taking into consideration the RCU case where the request being processed is the last request, then by trying to reprocess the last request if we find it hasn't been processed yet when checking the queues, and lastly by adding some opportunistic checks of the pending regulatory work when bringing an interface up or down. If folks want to consider this for stable the first two seem least intrusive and address the issue but those two patches still require a trigger to process the queue. Typically the queues will be processed on a system after bootup after the interface comes up and finds some beacon hints on 5 gHz, or when a user asks to change regulatory domains. The last patch tries to avoid requiring this and I consider it more an enhancement. Luis R. Rodriguez (3): cfg80211: allow reprocessing of pending requests cfg80211: fix processing world regdomain when non modular cfg80211: processing regulatory requests on netdev notifier net/wireless/core.c | 2 ++ net/wireless/reg.c | 21 ++++++++++++++------- net/wireless/reg.h | 1 + 3 files changed, 17 insertions(+), 7 deletions(-) -- 1.8.4.3 -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
