From: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Stanislaw Gruszka <sgruszka@redhat.com>,
Intel Linux Wireless <ilw@linux.intel.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] iwlwifi: do not nulify ctx->vif on reset
Date: Mon, 26 Mar 2012 11:51:32 -0700 [thread overview]
Message-ID: <1332787892.27767.17.camel@wwguy-huron> (raw)
In-Reply-To: <20120326184209.GJ13806@tuxdriver.com>
Hi John,
On Mon, 2012-03-26 at 14:42 -0400, John W. Linville wrote:
> On Mon, Mar 26, 2012 at 07:30:32AM -0700, Guy, Wey-Yi wrote:
> > On Mon, 2012-03-26 at 11:08 +0200, Johannes Berg wrote:
> > > On Wed, 2012-03-14 at 09:14 +0100, Stanislaw Gruszka wrote:
> > > > On Wed, Mar 14, 2012 at 08:07:48AM +0100, Stanislaw Gruszka wrote:
> > > > > I'll update and recheck again.
> > > >
> > > > On updated tree (head 035364916f75151b4b91ea53968c6beba7545317) devices
> > > > stop working here on any forced reset during TX as well. There are
> > > > messages like below in dmesg:
> > > >
> > > > wlan3: dropped data frame to not associated station 00:00:00:00:00:00
> > > >
> > > > And one time crash happened too, in:
> > > >
> > > > (gdb) l *(iwl_remove_dynamic_key+0x1f0)
> > > > 0x15e20 is in iwl_remove_dynamic_key (drivers/net/wireless/iwlwifi/iwl-agn-sta.c:1105).
> > > > 1100 /*
> > > > 1101 * The device expects GTKs for station interfaces to be
> > > > 1102 * installed as GTKs for the AP station. If we have no
> > > > 1103 * station ID, then use the ap_sta_id in that case.
> > > > 1104 */
> > > > 1105 if (vif->type == NL80211_IFTYPE_STATION && vif_priv->ctx)
> > > > 1106 return vif_priv->ctx->ap_sta_id;
> > > > 1107
> > > > 1108 return IWL_INVALID_STATION;
> > > > 1109 }
> > > >
> > > > To reproduce problems, I'm doing "ping -f 192.168.1.1" on one console
> > > > and run script [1] on other console.
> > >
> > > Ok so I finally got some time to look into this in some detail. It seems
> > > that the driver assumes a few calls from mac80211 like key settings can
> > > only happen while the vif pointers are valid, which is correct under
> > > normal circumstances but due to races with HW reset it's not really true
> > > there.
> > >
> > > We could fix all of those, but it seems your patch is the better
> > > approach. Wey, can you pick it up?
> >
> > yes
>
> Should I just take it and try to get it merged for -rc1?
I am taking it into our internal tree for our regression, if it is ok
for you, could you wait a bit, I will push it with all our other
patches.
btw, I have pretty large queue of patches again (~50+), this time I will
break it up and push separated :-)
Thanks
Wey
prev parent reply other threads:[~2012-03-26 18:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 15:10 [PATCH] iwlwifi: do not nulify ctx->vif on reset Stanislaw Gruszka
2012-03-13 15:15 ` Johannes Berg
2012-03-14 6:25 ` Stanislaw Gruszka
2012-03-14 6:58 ` Johannes Berg
2012-03-14 7:07 ` Stanislaw Gruszka
2012-03-14 8:14 ` Stanislaw Gruszka
2012-03-16 14:37 ` Stanislaw Gruszka
2012-03-16 15:16 ` Johannes Berg
2012-03-26 9:08 ` Johannes Berg
2012-03-26 14:30 ` Guy, Wey-Yi
2012-03-26 18:42 ` John W. Linville
2012-03-26 18:51 ` Guy, Wey-Yi [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=1332787892.27767.17.camel@wwguy-huron \
--to=wey-yi.w.guy@intel.com \
--cc=ilw@linux.intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--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 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.