From: "Arend van Spriel" <arend-dY08KVG/lbpWk0Htik3J/w@public•gmane.org>
To: "John W. Linville" <linville-2XuSBdqkA4R54TAoqtyWWQ@public•gmane.org>
Cc: "Josh Boyer" <jwboyer-H+wXaHxf7aLQT0dZR+AlfA@public•gmane.org>,
"Johannes Berg"
<johannes-cdvu00un1VgdHxzADdlk8Q@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, 1 Aug 2012 18:40:15 +0200 [thread overview]
Message-ID: <50195BEF.8010206@broadcom.com> (raw)
In-Reply-To: <20120801155252.GE27433-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
On 08/01/2012 05:52 PM, John W. Linville wrote:
> On Wed, Aug 01, 2012 at 05:51:08PM +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.
>
> Do we need to revert those patches?
>
either that or fix it.
Gr. AvS
--
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 16:40 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 [this message]
[not found] ` <5019506C.6020707-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
2012-08-01 15:53 ` Johannes Berg
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=50195BEF.8010206@broadcom.com \
--to=arend-dy08kvg/lbpwk0htik3j/w@public$(echo .)gmane.org \
--cc=brudley-dY08KVG/lbpWk0Htik3J/w@public$(echo .)gmane.org \
--cc=johannes-cdvu00un1VgdHxzADdlk8Q@public$(echo .)gmane.org \
--cc=jwboyer-H+wXaHxf7aLQT0dZR+AlfA@public$(echo .)gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public$(echo .)gmane.org \
--cc=linville-2XuSBdqkA4R54TAoqtyWWQ@public$(echo .)gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public$(echo .)gmane.org \
--cc=rvossen-dY08KVG/lbpWk0Htik3J/w@public$(echo .)gmane.org \
--cc=seth.forshee-Z7WLFzj8eWMS+FvcfC7Uqw@public$(echo .)gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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