linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Marek Puzyniak <marek.puzyniak@tieto.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v4] cfg80211: fix dfs channel state after stopping AP
Date: Mon, 16 Dec 2013 15:29:55 +0100	[thread overview]
Message-ID: <1387204195.2057.14.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1387191346-23830-1-git-send-email-marek.puzyniak@tieto.com> (sfid-20131216_115607_589735_28E33061)

On Mon, 2013-12-16 at 11:55 +0100, Marek Puzyniak wrote:
> In AP mode DFS channel state is changed to DFS_AVAILABLE
> after successful CAC and remains as such until a radar
> signal is detected during the In-Service Monitoring.
> When AP is stopped it is no longer monitoring current channel
> for radar signals. DFS channel state should be changed
> to DFS_USABLE when last AP interface is stopped. Starting AP
> again on that channel will start CAC instead of starting radiation.

If you keep changing your patch without any changelog (after the "---"
line!) then I have no idea what I should look at?

> +	if (rdev->num_running_ifaces == 1) {
> +		/* Last running AP iface*/

missing a space

> +		wdev_lock(wdev_iter);

This will almost certainly cause a lockdep warning since you hold the
wdev lock already.

> +		if (!netif_running(wdev_iter->netdev)) {
> +			wdev_unlock(wdev_iter);
> +			continue;
> +		}
> +
> +		if (wdev_iter->iftype == NL80211_IFTYPE_AP) {
> +			wdev_unlock(wdev_iter);
> +			return false;
> +		}
> +		wdev_unlock(wdev_iter);

I don't think checking the iftype needs the lock (this lock - maybe
rtnl) anyway?

johannes


  reply	other threads:[~2013-12-16 14:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-16 10:55 [PATCH v4] cfg80211: fix dfs channel state after stopping AP Marek Puzyniak
2013-12-16 14:29 ` Johannes Berg [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-12-16 14:53 Marek Puzyniak

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=1387204195.2057.14.camel@jlt4.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=marek.puzyniak@tieto.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).