From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211: run scan after finish connection monitoring
Date: Tue, 29 May 2012 13:24:09 +0200 [thread overview]
Message-ID: <20120529112407.GB2441@redhat.com> (raw)
In-Reply-To: <1337174840-2658-1-git-send-email-sgruszka@redhat.com>
On Wed, May 16, 2012 at 03:27:20PM +0200, Stanislaw Gruszka wrote:
> commit 133d40f9a22bdfd2617a446f1e3209537c5415ec
> Author: Stanislaw Gruszka <sgruszka@redhat.com>
> Date: Wed Mar 28 16:01:19 2012 +0200
>
> mac80211: do not scan and monitor connection in parallel
>
> add bug, which make possible to start a scan and never finish it, so
> make every new scanning request finish with -EBUSY error. This can
> happen on code paths where we finish connection monitoring and clear
> IEEE80211_STA_*_POLL flags, but do not check if scan was deferred.
> This patch fixes those code paths.
This patch fix commit, which went to Linus (3.5-rc) kernel, so should be
applied there as well.
Stanislaw
prev parent reply other threads:[~2012-05-29 11:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 13:27 [PATCH] mac80211: run scan after finish connection monitoring Stanislaw Gruszka
2012-05-29 11:24 ` Stanislaw Gruszka [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=20120529112407.GB2441@redhat.com \
--to=sgruszka@redhat.com \
--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).