From: Pavel Roskin <proski@gnu.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, John Linville <linville@tuxdriver.com>
Subject: Re: [PATCH] cfg80211: fix disassociation warning due to misuse of wdev->current_bss
Date: Thu, 06 Aug 2009 08:55:08 -0400 [thread overview]
Message-ID: <1249563308.15613.9.camel@ct> (raw)
In-Reply-To: <1249549574.4852.17.camel@johannes.local>
On Thu, 2009-08-06 at 11:06 +0200, Johannes Berg wrote:
> On Thu, 2009-08-06 at 04:52 -0400, Pavel Roskin wrote:
> > WARN_ON was triggered at mlme.c:213 when dissociating from an AP.
> >
> > wdev->current_bss->pub.bssid should be used in place of
> > wdev->current_bss for BSSID comparison.
>
> Oh wow, good catch, thanks.
Now that the check is fixed, it turn out there is a related problem in
the same function. If the device is in the managed mode and disconnects
from an AP due to a low signal, attempts to reassociate by setting the
same ESSID fail:
Error for wireless request "Set ESSID" (8B1A) :
SET failed on device wlan0 ; Operation already in progress.
It happens because wdev->auth_bsses[i] is not set to NULL.
cfg80211_sme_disassoc() can do it, but not if wdev->conn->state is
CFG80211_CONN_IDLE.
Either cfg80211_sme_disassoc() or __cfg80211_send_disassoc() should
unset wdev->auth_bsses[i] for the management mode.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2009-08-06 12:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-06 8:52 [PATCH] cfg80211: fix disassociation warning due to misuse of wdev->current_bss Pavel Roskin
2009-08-06 9:06 ` Johannes Berg
2009-08-06 12:55 ` Pavel Roskin [this message]
2009-08-06 13:09 ` Johannes Berg
2009-08-06 20:39 ` Pavel Roskin
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=1249563308.15613.9.camel@ct \
--to=proski@gnu.org \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.