From: Simon Wunderlich <sw@simonwunderlich.de>
To: Luciano Coelho <luciano.coelho@intel.com>
Cc: linux-wireless@vger.kernel.org, yeohchunyeow@gmail.com,
yeohchunyeow@cozybit.com, andrei.otcheretianski@intel.com
Subject: Re: [PATCH v8 5/5] mac80211: only set CSA beacon when at least one beacon must be transmitted
Date: Thu, 5 Dec 2013 19:49:58 +0100 [thread overview]
Message-ID: <201312051949.58777.sw@simonwunderlich.de> (raw)
In-Reply-To: <1386257143-29840-6-git-send-email-luciano.coelho@intel.com>
Hey Luca,
let me add first that there is another locking regression introduced by my
latest fixes for the IBSS mode. I'll send a fix in a minute, please include it
when you test/rebase.
Appearently there are a few locking problems in your patch too (do you have a
chance to test it, somehow?), see comments inline:
> --- a/net/mac80211/cfg.c
> +++ b/net/mac80211/cfg.c
> @@ -2982,21 +2982,19 @@ cfg80211_beacon_dup(struct cfg80211_beacon_data
> *beacon) return new_beacon;
> }
>
> -void ieee80211_csa_finalize_work(struct work_struct *work)
> +void ieee80211_csa_finish(struct ieee80211_vif *vif)
> {
> - struct ieee80211_sub_if_data *sdata =
> - container_of(work, struct ieee80211_sub_if_data,
> - csa_finalize_work);
> - struct ieee80211_local *local = sdata->local;
> - int err, changed = 0;
> + struct ieee80211_sub_if_data *sdata = vif_to_sdata(vif);
>
> - sdata_lock(sdata);
> - /* AP might have been stopped while waiting for the lock. */
> - if (!sdata->vif.csa_active)
> - goto unlock;
> + ieee80211_queue_work(&sdata->local->hw,
> + &sdata->csa_finalize_work);
> +}
> +EXPORT_SYMBOL(ieee80211_csa_finish);
>
> - if (!ieee80211_sdata_running(sdata))
> - goto unlock;
> +static void ieee80211_csa_finalize(struct ieee80211_sub_if_data *sdata)
> +{
> + struct ieee80211_local *local = sdata->local;
> + int err, changed = 0;
>
> sdata->radar_required = sdata->csa_radar_required;
> err = ieee80211_vif_change_channel(sdata, &changed);
This hunk is a little hard to understand, but at least in the resulting file I
have here, csa_finalize() does sdata_unlock but never locks it. Lockdep
complains about locking imbalance, and actually that's true ...
> @@ -3048,6 +3046,29 @@ unlock:
> sdata_unlock(sdata);
> }
>
> +void ieee80211_csa_finalize_work(struct work_struct *work)
> +{
> + struct ieee80211_sub_if_data *sdata =
> + container_of(work, struct ieee80211_sub_if_data,
> + csa_finalize_work);
> +
> + sdata_lock(sdata);
> + /* AP might have been stopped while waiting for the lock. */
> + if (!sdata->vif.csa_active)
> + goto unlock;
> +
> + if (!ieee80211_sdata_running(sdata))
> + goto unlock;
> +
> + if (!ieee80211_sdata_running(sdata))
> + return;
Why are you checking the same thing twice? The second time without unlocking,
that's unsafe too ...
> +
> + ieee80211_csa_finalize(sdata);
> +
> +unlock:
> + sdata_unlock(sdata);
> +}
> +
> int ieee80211_channel_switch(struct wiphy *wiphy, struct net_device *dev,
> struct cfg80211_csa_settings *params)
> {
Cheers,
Simon
next prev parent reply other threads:[~2013-12-05 18:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 15:25 [PATCH v8 0/5] CSA beacon count changes Luciano Coelho
2013-12-05 15:25 ` [PATCH v8 1/5] mac80211: refactor ieee80211_ibss_process_chanswitch() Luciano Coelho
2013-12-05 15:25 ` [PATCH v8 2/5] mac80211: align ieee80211_ibss_csa_beacon() with ieee80211_csa_beacon() Luciano Coelho
2013-12-07 16:44 ` Jones Desougi
2013-12-05 15:25 ` [PATCH v8 3/5] mac80211: refactor ieee80211_mesh_process_chanswitch() Luciano Coelho
2013-12-05 16:05 ` Johannes Berg
2013-12-05 19:31 ` Coelho, Luciano
2013-12-05 15:25 ` [PATCH v8 4/5] mac80211: align ieee80211_mesh_csa_beacon() with ieee80211_csa_beacon() Luciano Coelho
2013-12-05 16:04 ` Johannes Berg
2013-12-05 18:53 ` Coelho, Luciano
2013-12-05 18:53 ` Johannes Berg
2013-12-05 19:01 ` Coelho, Luciano
2013-12-05 15:25 ` [PATCH v8 5/5] mac80211: only set CSA beacon when at least one beacon must be transmitted Luciano Coelho
2013-12-05 18:49 ` Simon Wunderlich [this message]
2013-12-06 10:34 ` Yeoh Chun-Yeow
2013-12-06 12:03 ` Coelho, Luciano
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=201312051949.58777.sw@simonwunderlich.de \
--to=sw@simonwunderlich.de \
--cc=andrei.otcheretianski@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=luciano.coelho@intel.com \
--cc=yeohchunyeow@cozybit.com \
--cc=yeohchunyeow@gmail.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 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).