From: "Arend van Spriel" <arend@broadcom.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
"Josh Boyer" <jwboyer@redhat.com>,
"Brett Rudley" <brudley@broadcom.com>,
"Roland Vossen" <rvossen@broadcom.com>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
"Seth Forshee" <seth.forshee@canonical.com>,
"Luis R. Rodriguez" <rodrigue@qca.qualcomm.com>
Subject: Re: assert_cfg80211_lock warning with Linux v3.5-8833-g2d53492
Date: Wed, 1 Aug 2012 21:28:48 +0200 [thread overview]
Message-ID: <50198370.20304@broadcom.com> (raw)
In-Reply-To: <50196660.8090001@broadcom.com>
On 08/01/2012 07:24 PM, Arend van Spriel wrote:
> It seems the API was as it currently is when adding regulatory framework
> changes in brcmsmac so we should have seen this assert flying by. The
> problem is that freq_reg_info() is exposed in cfg80211.h, but as it is
> now it can only be used under the cfg80211_mutex lock, ie. in regulatory
> notify callback (as Seth indicated).
>
> Gr. AvS
Ah, I see you need to run a LOCKDEP-enabled kernel to get this warning.
Gr. AvS
WARNING: multiple messages have this Message-ID (diff)
From: "Arend van Spriel" <arend-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
To: "Johannes Berg" <johannes-cdvu00un1VgdHxzADdlk8Q@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>,
"Luis R. Rodriguez"
<rodrigue-A+ZNKFmMK5xy9aJCnZT0Uw@public.gmane.org>
Subject: Re: assert_cfg80211_lock warning with Linux v3.5-8833-g2d53492
Date: Wed, 1 Aug 2012 21:28:48 +0200 [thread overview]
Message-ID: <50198370.20304@broadcom.com> (raw)
In-Reply-To: <50196660.8090001-dY08KVG/lbpWk0Htik3J/w@public.gmane.org>
On 08/01/2012 07:24 PM, Arend van Spriel wrote:
> It seems the API was as it currently is when adding regulatory framework
> changes in brcmsmac so we should have seen this assert flying by. The
> problem is that freq_reg_info() is exposed in cfg80211.h, but as it is
> now it can only be used under the cfg80211_mutex lock, ie. in regulatory
> notify callback (as Seth indicated).
>
> Gr. AvS
Ah, I see you need to run a LOCKDEP-enabled kernel to get this warning.
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 19:29 UTC|newest]
Thread overview: 19+ 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
2012-08-01 13:12 ` Josh Boyer
2012-08-01 14:18 ` John W. Linville
2012-08-01 14:18 ` John W. Linville
2012-08-01 15:38 ` Arend van Spriel
2012-08-01 15:38 ` Arend van Spriel
2012-08-01 15:51 ` Arend van Spriel
2012-08-01 15:52 ` John W. Linville
2012-08-01 16:40 ` Arend van Spriel
2012-08-01 16:40 ` Arend van Spriel
2012-08-01 15:53 ` Johannes Berg
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
2012-08-01 17:24 ` Arend van Spriel
2012-08-01 17:24 ` Arend van Spriel
2012-08-01 19:28 ` Arend van Spriel [this message]
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=50198370.20304@broadcom.com \
--to=arend@broadcom.com \
--cc=brudley@broadcom.com \
--cc=johannes@sipsolutions.net \
--cc=jwboyer@redhat.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=rodrigue@qca.qualcomm.com \
--cc=rvossen@broadcom.com \
--cc=seth.forshee@canonical.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.