From: Jakub Kicinski <kubakici@wp.pl>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211: fix sdata locking around __ieee80211_request_smps
Date: Mon, 3 Jun 2013 15:05:03 +0200 [thread overview]
Message-ID: <20130603150503.787d2840@north> (raw)
In-Reply-To: <1370260400-12149-1-git-send-email-johannes@sipsolutions.net>
On Mon, 3 Jun 2013 13:53:20 +0200, Johannes Berg wrote:
> From: Johannes Berg <johannes.berg@intel.com>
>
> My cfg80211/mac80211 locking unification broke the sdata
> locking in ieee80211_set_power_mgmt, it needs to acquire
> the lock for __ieee80211_request_smps(). Add the locking.
>
> Reported-by: Jakub Kicinski <kubakici@wp.pl>
> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
> ---
> net/mac80211/cfg.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/net/mac80211/cfg.c b/net/mac80211/cfg.c
> index 9034da1..3062210 100644
> --- a/net/mac80211/cfg.c
> +++ b/net/mac80211/cfg.c
> @@ -2378,7 +2378,9 @@ static int ieee80211_set_power_mgmt(struct wiphy *wiphy, struct net_device *dev,
> local->dynamic_ps_forced_timeout = timeout;
>
> /* no change, but if automatic follow powersave */
> + sdata_lock(sdata);
> __ieee80211_request_smps(sdata, sdata->u.mgd.req_smps);
> + sdata_unlock(sdata);
>
> if (local->hw.flags & IEEE80211_HW_SUPPORTS_DYNAMIC_PS)
> ieee80211_hw_config(local, IEEE80211_CONF_CHANGE_PS);
I can confirm that this patch fixes the reported warning.
I had to double check that sdata_lock takes the wdev mutex
though, because lockdep assert on cfg.c:2321 looks like this:
lockdep_assert_held(&sdata->wdev.mtx)
instead of:
sdata_assert_lock(&sdata)
just saying... :-)
-- kuba
prev parent reply other threads:[~2013-06-03 13:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-03 11:53 [PATCH] mac80211: fix sdata locking around __ieee80211_request_smps Johannes Berg
2013-06-03 13:05 ` Jakub Kicinski [this message]
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=20130603150503.787d2840@north \
--to=kubakici@wp.pl \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.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).