All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 05/10] cfg80211: add regulatory_hint_core() to separate the core reg hint
Date: Mon, 16 Feb 2009 01:17:46 -0800	[thread overview]
Message-ID: <43e72e890902160117yd3a3b09o45ada7bc0aa0fbd7@mail.gmail.com> (raw)
In-Reply-To: <1234774211.4219.102.camel@johannes.local>

On Mon, Feb 16, 2009 at 12:50 AM, Johannes Berg
<johannes@sipsolutions.net> wrote:
> On Mon, 2009-02-16 at 00:14 -0800, Luis R. Rodriguez wrote:
>> On Sun, Feb 15, 2009 at 2:59 AM, Johannes Berg
>> <johannes@sipsolutions.net> wrote:
>> > On Fri, 2009-02-13 at 21:33 -0800, Luis R. Rodriguez wrote:
>> >> This will allow us to clean up and make distinctions of who
>> >> needs locking or not.
>> >>
>> >> Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
>> >> ---
>> >>  net/wireless/reg.c |   36 +++++++++++++++++++++++++++---------
>> >>  1 files changed, 27 insertions(+), 9 deletions(-)
>> >>
>> >> diff --git a/net/wireless/reg.c b/net/wireless/reg.c
>> >> index ba82312..679fded 100644
>> >> --- a/net/wireless/reg.c
>> >> +++ b/net/wireless/reg.c
>> >> @@ -1050,11 +1050,7 @@ static int ignore_request(struct wiphy *wiphy, enum reg_set_by set_by,
>> >>       case REGDOM_SET_BY_INIT:
>> >>               return -EINVAL;
>> >>       case REGDOM_SET_BY_CORE:
>> >> -             /*
>> >> -              * Always respect new wireless core hints, should only happen
>> >> -              * when updating the world regulatory domain at init.
>> >> -              */
>> >> -             return 0;
>> >> +             return -EINVAL;
>> >>       case REGDOM_SET_BY_COUNTRY_IE:
>> >>               if (unlikely(!is_an_alpha2(alpha2)))
>> >>                       return -EINVAL;
>> >> @@ -1183,6 +1179,26 @@ new_request:
>> >>       return call_crda(alpha2);
>> >>  }
>> >>
>> >> +static int regulatory_hint_core(const char *alpha2)
>> >> +{
>> >> +     struct regulatory_request *request;
>> >> +
>> >> +     BUG_ON(last_request);
>> >> +
>> >> +     request = kzalloc(sizeof(struct regulatory_request),
>> >> +                       GFP_KERNEL);
>> >> +     if (!request)
>> >> +             return -ENOMEM;
>> >> +
>> >> +     request->alpha2[0] = alpha2[0];
>> >> +     request->alpha2[1] = alpha2[1];
>> >> +     request->initiator = REGDOM_SET_BY_CORE;
>> >> +
>> >> +     last_request = request;
>> >
>> > So before you documented that cfg80211_mutex is used to protect this
>> > variable, but it's not used here.
>>
>> This is only used during initialization, have any better ideas?
>
> If regulatory is initialised before netlink that is probably fine, is
> it?

Yeah I was hoping that would be the case but then I realized that we
also end up creating a udev event to call crda and we need nl80211
initialized in order to process these hints so technically we have a
race between regulatory_init() finishing and nl80211_init() get done
before we can let nl80211 process the first CORE call to crda so it
may be dropped -- unless we are sure udev will do some sort of
retries.

An alternative is to add the regulatory_request() for core to the
queue and then call a reg_post_init() on core.c  that would just
schedule the reg workqueue after nl80211_init().

Thoughts?

  Luis

  reply	other threads:[~2009-02-16  9:17 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-14  5:33 [PATCH 00/10] cfg80211: move reg hints to workqueue Luis R. Rodriguez
2009-02-14  5:33 ` [PATCH 01/10] cfg80211: rename cfg80211_registered_device's idx to wiphy_idx Luis R. Rodriguez
2009-02-14  5:33 ` [PATCH 02/10] cfg80211: add wiphy_idx_valid to check for wiphy_idx sanity Luis R. Rodriguez
2009-02-14  5:33 ` [PATCH 03/10] cfg80211: rename cfg80211_drv_mutex to cfg80211_mutex Luis R. Rodriguez
2009-02-14  5:33 ` [PATCH 04/10] nl80211: disallow user requests prior to regulatory_init() Luis R. Rodriguez
2009-02-15 10:58   ` Johannes Berg
2009-02-16  8:13     ` Luis R. Rodriguez
2009-02-16  8:49       ` Johannes Berg
2009-02-16  9:01         ` Luis R. Rodriguez
2009-02-14  5:33 ` [PATCH 05/10] cfg80211: add regulatory_hint_core() to separate the core reg hint Luis R. Rodriguez
2009-02-15 10:59   ` Johannes Berg
2009-02-16  8:14     ` Luis R. Rodriguez
2009-02-16  8:50       ` Johannes Berg
2009-02-16  9:17         ` Luis R. Rodriguez [this message]
2009-02-16  9:22           ` Johannes Berg
2009-02-16  9:29             ` Luis R. Rodriguez
2009-02-14  5:33 ` [PATCH 06/10] cfg80211: propagate -ENOMEM during regulatory_init() Luis R. Rodriguez
2009-02-15 11:01   ` Johannes Berg
2009-02-16  8:18     ` Luis R. Rodriguez
2009-02-16  8:52       ` Johannes Berg
2009-02-16  9:09         ` Luis R. Rodriguez
2009-02-16  9:15           ` Johannes Berg
2009-02-16  9:24             ` Luis R. Rodriguez
2009-02-14  5:33 ` [PATCH 07/10] cfg80211: add assert_cfg80211_lock() to ensure proper protection Luis R. Rodriguez
2009-02-15 11:01   ` Johannes Berg
2009-02-16  8:19     ` Luis R. Rodriguez
2009-02-14  5:33 ` [PATCH 08/10] cfg80211: make regulatory_request use wiphy_idx instead of wiphy Luis R. Rodriguez
2009-02-15 11:04   ` Johannes Berg
2009-02-16  9:55     ` Luis R. Rodriguez
2009-02-16 10:02       ` Johannes Berg
2009-02-16 10:11         ` Luis R. Rodriguez
2009-02-16 10:20           ` Johannes Berg
2009-02-16 11:11             ` Luis R. Rodriguez
2009-02-14  5:33 ` [PATCH 09/10] cfg80211: move regulatory hints to workqueue Luis R. Rodriguez
2009-02-15 11:10   ` Johannes Berg
2009-02-16  9:48     ` Luis R. Rodriguez
2009-02-16  9:55       ` Johannes Berg
2009-02-16 10:09         ` Luis R. Rodriguez
2009-02-16 10:18           ` Johannes Berg
2009-02-14  5:33 ` [PATCH 10/10] cfg80211: comments style cleanup Luis R. Rodriguez
2009-02-14  5:50 ` [PATCH 00/10] cfg80211: move reg hints to workqueue Luis R. Rodriguez

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=43e72e890902160117yd3a3b09o45ada7bc0aa0fbd7@mail.gmail.com \
    --to=lrodriguez@atheros.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.