From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Arend van Spriel" Subject: Re: assert_cfg80211_lock warning with Linux v3.5-8833-g2d53492 Date: Wed, 1 Aug 2012 18:40:15 +0200 Message-ID: <50195BEF.8010206@broadcom.com> References: <20120801131232.GA1785@zod.bos.redhat.com> <20120801141810.GB27433@tuxdriver.com> <50194D7A.6060400@broadcom.com> <5019506C.6020707@broadcom.com> <20120801155252.GE27433@tuxdriver.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Cc: "Josh Boyer" , "Johannes Berg" , "Brett Rudley" , "Roland Vossen" , linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, "Seth Forshee" To: "John W. Linville" Return-path: In-Reply-To: <20120801155252.GE27433-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org> Sender: linux-wireless-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: netdev.vger.kernel.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