From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
To: johannes@sipsolutions.net
Cc: linux@eikelenboom.it, linux-wireless@vger.kernel.org,
"Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Subject: [PATCH 0/3] cfg80211: process pending regulatory requests
Date: Thu, 19 Dec 2013 12:53:16 -0800 [thread overview]
Message-ID: <1387486399-4053-1-git-send-email-mcgrof@do-not-panic.com> (raw)
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
next reply other threads:[~2013-12-19 20:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 20:53 Luis R. Rodriguez [this message]
2013-12-19 20:53 ` [PATCH 1/3] cfg80211: allow reprocessing of pending requests Luis R. Rodriguez
2014-01-07 15:34 ` Johannes Berg
2014-01-23 13:16 ` Sander Eikelenboom
2014-01-24 23:14 ` Luis R. Rodriguez
2014-01-27 10:48 ` Sander Eikelenboom
2014-02-19 0:51 ` Luis R. Rodriguez
2013-12-19 20:53 ` [PATCH 2/3] cfg80211: fix processing world regdomain when non modular Luis R. Rodriguez
2014-01-07 15:35 ` Johannes Berg
2014-02-19 1:10 ` Luis R. Rodriguez
2013-12-19 20:53 ` [PATCH 3/3] cfg80211: processing regulatory requests on netdev notifier Luis R. Rodriguez
2014-01-07 15:35 ` Johannes Berg
2014-02-19 1:24 ` Luis R. Rodriguez
2014-02-19 18:08 ` Luis R. Rodriguez
2013-12-20 12:19 ` [PATCH 0/3] cfg80211: process pending regulatory requests Sander Eikelenboom
2014-01-06 13:10 ` Sander Eikelenboom
2014-01-06 13:32 ` Johannes Berg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1387486399-4053-1-git-send-email-mcgrof@do-not-panic.com \
--to=mcgrof@do-not-panic.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@eikelenboom.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).