mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: Jake Edge <jake@lwn.net>,
	linux-wireless@vger.kernel.org,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: Bisected 3.9 regression for iwl4965 connection problem to 1672c0e3
Date: Fri, 24 May 2013 22:28:43 +0200	[thread overview]
Message-ID: <1369427323.8290.37.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <20130522115908.GA22547@redhat.com>

On Wed, 2013-05-22 at 13:59 +0200, Stanislaw Gruszka wrote:

> > AFICT, we wake queues only if beacon arrives or mac80211 call drv_config
> > with BSS_CHANGED_IDLE. I'm not sure if the latter prevent stuck. 
> 
> It should prevent stuck. When we fail to auth, drv_config() with BSS_CHANGED_IDLE
> is called via:
> 
> ieee80211_destroy_auth_data ->
> ieee80211_vif_release_channel ->
> __ieee80211_vif_release_channel ->
> ieee80211_unassign_vif_chanctx ->
> ieee80211_bss_info_change_notify
> 
> But there is need to have ->vif.chanctx_conf valid in 
> __ieee80211_vif_release_channel(), where is below condition:
> 
>         conf = rcu_dereference_protected(sdata->vif.chanctx_conf,
>                                          lockdep_is_held(&local->chanctx_mtx));
>         if (!conf)
>                 return;
> 
> I'm not sure if that always happen. Perhaps would be better to change
> BSS_CHANGED_IDLE to BSS_CHANGED_BSSID, which is called directly from
> ieee80211_destroy_auth_data() ?

I don't think the "!conf" can hit in this case, since to even try to
associate you have to have a channel context assigned.

johannes


  reply	other threads:[~2013-05-24 20:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-05 20:38 Jake Edge
2013-05-06 12:38 ` Stanislaw Gruszka
2013-05-06 14:37   ` Jake Edge
2013-05-06 15:30     ` Stanislaw Gruszka
2013-05-06 15:31       ` Johannes Berg
2013-05-06 15:44         ` Johannes Berg
2013-05-07  8:42           ` Stanislaw Gruszka
2013-05-07  8:46             ` Emmanuel Grumbach
2013-05-07 13:53             ` Johannes Berg
2013-05-07 15:35               ` Stanislaw Gruszka
2013-05-07 16:07                 ` [PATCH 3.10] iwl4965: workaround connection regression on passive channel Stanislaw Gruszka
2013-05-22 11:59                 ` Bisected 3.9 regression for iwl4965 connection problem to 1672c0e3 Stanislaw Gruszka
2013-05-24 20:28                   ` Johannes Berg [this message]
2013-05-06 15:11 ` Johannes Berg
2013-05-06 15:21   ` Jake Edge
2013-05-06 15:24     ` Johannes Berg
2013-05-06 15:29       ` Jake Edge

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=1369427323.8290.37.camel@jlt4.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=jake@lwn.net \
    --cc=linux-kernel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®