From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Stanislaw Gruszka <sgruszka@redhat.com>
Subject: Re: Latest wireless-testing has broken scan locking.
Date: Thu, 07 Oct 2010 10:34:48 +0200 [thread overview]
Message-ID: <1286440488.3657.23.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <4CAD48DA.9010208@candelatech.com>
On Wed, 2010-10-06 at 21:13 -0700, Ben Greear wrote:
> Unless I really screwed up a merge in a strange way, the
> ieee80211_scan_work is broken.
>
> It calls mutex_unlock(&local->mtx) too many times when it hits
> this code:
>
> case SCAN_DECISION:
> /* if no more bands/channels left, complete scan */
> if (local->scan_channel_idx >= local->scan_req->n_channels) {
> aborted = false;
> goto out_complete;
> }
So much for trusting Stanislaw :-( I can reproduce this in hwsim.
Stanislaw, did you ever test software scan at all?
Below patch fixes this.
johannes
---
net/mac80211/scan.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
--- wireless-testing.orig/net/mac80211/scan.c 2010-10-07 10:27:37.000000000 +0200
+++ wireless-testing/net/mac80211/scan.c 2010-10-07 10:31:19.000000000 +0200
@@ -693,8 +693,6 @@ void ieee80211_scan_work(struct work_str
goto out_complete;
}
- mutex_unlock(&local->mtx);
-
/*
* as long as no delay is required advance immediately
* without scheduling a new work
@@ -725,6 +723,7 @@ void ieee80211_scan_work(struct work_str
} while (next_delay == 0);
ieee80211_queue_delayed_work(&local->hw, &local->scan_work, next_delay);
+ mutex_unlock(&local->mtx);
return;
out_complete:
next prev parent reply other threads:[~2010-10-07 8:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 4:13 Latest wireless-testing has broken scan locking Ben Greear
2010-10-07 8:34 ` Johannes Berg [this message]
2010-10-07 9:18 ` Stanislaw Gruszka
2010-10-07 9:24 ` Johannes Berg
2010-10-07 9:38 ` Stanislaw Gruszka
2010-10-07 9:38 ` Johannes Berg
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=1286440488.3657.23.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
--cc=sgruszka@redhat.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).