From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
To: Arend van Spriel <arend-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
Cc: "John W. Linville"
<linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>,
Josh Boyer <jwboyer-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Brett Rudley <brudley-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>,
Roland Vossen <rvossen-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>,
linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Seth Forshee
<seth.forshee-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
Subject: Re: assert_cfg80211_lock warning with Linux v3.5-8833-g2d53492
Date: Wed, 01 Aug 2012 17:53:58 +0200 [thread overview]
Message-ID: <1343836438.4638.5.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <5019506C.6020707-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
On Wed, 2012-08-01 at 17:51 +0200, Arend van Spriel wrote:
> On 08/01/2012 05:38 PM, Arend van Spriel wrote:
> >> brcmsmac needs to hold cfg80211_mutex before calling freq_reg_info...
> >> >
> >> > It looks like those calls were added in mid-June.
> >> >
> > I think mid-june sounds about right. We never observed the warning when
> > changes to use regulatory infrastructure were tested/reviewed. Should
> > this precondition be mentioned in cfg80211.h?
> >
> > Gr. AvS
>
> Diving in further it seems brcmsmac can not grab the cfg80211_mutex. So
> another solution is needed.
Yeah I was going to say -- how can it possibly access that? It seems
that in some patch the API got broken, it should be taking the lock or
whatever ... I'll leave it to Luis to sort out though :-P
johannes
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-08-01 15:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-01 13:12 assert_cfg80211_lock warning with Linux v3.5-8833-g2d53492 Josh Boyer
[not found] ` <20120801131232.GA1785-8k7Gwy46GHkf7BdofF/totBPR1lH4CV8@public.gmane.org>
2012-08-01 14:18 ` John W. Linville
[not found] ` <20120801141810.GB27433-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2012-08-01 15:38 ` Arend van Spriel
2012-08-01 15:51 ` Arend van Spriel
2012-08-01 15:52 ` John W. Linville
[not found] ` <20120801155252.GE27433-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2012-08-01 16:40 ` Arend van Spriel
[not found] ` <5019506C.6020707-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2012-08-01 15:53 ` Johannes Berg [this message]
2012-08-01 16:19 ` Seth Forshee
2012-08-01 17:14 ` Johannes Berg
2012-08-01 17:56 ` Seth Forshee
[not found] ` <1343836438.4638.5.camel-8upI4CBIZJIJvtFkdXX2HixXY32XiHfO@public.gmane.org>
2012-08-01 17:24 ` Arend van Spriel
[not found] ` <50196660.8090001-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2012-08-01 19:28 ` Arend van Spriel
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=1343836438.4638.5.camel@jlt3.sipsolutions.net \
--to=johannes-cdvu00un1vgdhxzaddlk8q@public.gmane.org \
--cc=arend-dY08KVG/lbpWk0Htik3J/w@public.gmane.org \
--cc=brudley-dY08KVG/lbpWk0Htik3J/w@public.gmane.org \
--cc=jwboyer-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rvossen-dY08KVG/lbpWk0Htik3J/w@public.gmane.org \
--cc=seth.forshee-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org \
/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).