From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, Johannes Berg <johannes.berg@intel.com>
Subject: Re: [PATCH 3.10] cfg80211: fix interface down/disconnect state handling
Date: Wed, 22 May 2013 11:15:55 -0700 [thread overview]
Message-ID: <519D0B5B.5070707@candelatech.com> (raw)
In-Reply-To: <519D00EF.60002@candelatech.com>
On 05/22/2013 10:31 AM, Ben Greear wrote:
> On 05/14/2013 12:36 AM, Johannes Berg wrote:
>> From: Johannes Berg <johannes.berg@intel.com>
>>
>> When the interface goes down, there's no need to call
>> cfg80211_mlme_down() after __cfg80211_disconnect() as
>> the latter will call the former (if appropriate.)
>>
>> Also, in __cfg80211_disconnect(), if the cfg80211 SME
>> isn't used, __cfg80211_disconnected() may still need
>> to be called (depending on the current state) so that
>> the SME state gets cleared.
>
> 3.9.3 with this patch (and others) was running well until I
> tweaked user-space to drive a bit harder/differently and removed the
> noisy printk from my sme state debugging patches.
>
> Now, it appears the problem is back..though of course I
> don't have useful debugging as to why :P
Err, maybe it's something elsewhere in my logic.
Kernel debugging seems to show proper activity so far...
Ben
>
> Ben
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2013-05-22 18:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 7:36 [PATCH 3.10] cfg80211: fix interface down/disconnect state handling Johannes Berg
2013-05-22 17:31 ` Ben Greear
2013-05-22 18:15 ` Ben Greear [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=519D0B5B.5070707@candelatech.com \
--to=greearb@candelatech.com \
--cc=johannes.berg@intel.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 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.