From: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Jeff Chua <jeff.chua.linux@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
"Zhao, Shanyu" <shanyu.zhao@intel.com>,
"Chatre, Reinette" <reinette.chatre@intel.com>,
"stable@kernel.org" <stable@kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [REVERT] be6b38bcb175613f239e0b302607db346472c6b6. v2.6.34-rc3-406 oops with 4965AGN wireless
Date: Thu, 08 Apr 2010 13:09:33 -0700 [thread overview]
Message-ID: <1270757373.11853.11.camel@wwguy-ubuntu> (raw)
In-Reply-To: <20100408181340.GN30031@ZenIV.linux.org.uk>
On Thu, 2010-04-08 at 11:13 -0700, Al Viro wrote:
> On Fri, Apr 09, 2010 at 01:16:43AM +0800, Jeff Chua wrote:
> >
> > index 1bd2cd8..83c52a6 100644
> > --- a/drivers/net/wireless/iwlwifi/iwl-4965.c
> > +++ b/drivers/net/wireless/iwlwifi/iwl-4965.c
> > @@ -2041,16 +2041,14 @@ static void iwl4965_rx_reply_tx(struct iwl_priv *priv,
> > tx_resp->failure_frame);
> >
> > freed = iwl_tx_queue_reclaim(priv, txq_id, index);
> > - if (qc && likely(sta_id != IWL_INVALID_STATION))
> > - priv->stations[sta_id].tid[tid].tfds_in_queue -= freed;
> > + iwl_free_tfds_in_queue(priv, sta_id, tid, freed);
>
> So what happens if we hit sta_id == IWL_INVALID_STATION and !txq->sched_retry?
>
> AFAICS, IWL_INVALID_STATION is 255 and priv->stations[] has only 32 elements.
> And code around that place is
> if (txq->sched_retry && unlikely(sta_id == IWL_INVALID_STATION)) {
> IWL_ERR(priv, "Station not known\n");
> return;
> }
> if (txq->sched_retry) {
> ....
> } else {
> ....
> the code modified in that chunk
> ....
> }
> so this removal of check for sta_id doesn't look apriori safe...
>
> I'm not familiar with that code and I don't have the hardware, so this is
> just from RTFS, but... might make sense to replace that call of
> iwl_free_tfds_in_queue with
>
> if (sta_id == IWL_INVALID_STATION)
> printk(KERN_ERR "buggered");
> else
> iwl_free_tfds_in_queue(priv, sta_id, tid, freed);
>
> and see if that helps and if printk gets triggered.
We can check for IWL_INVALID_STATION and print log, but need to check
for qc to make sure it is valid; maybe something like
if (qc && likely(sta_id != IWL_INVALID_STATION))
iwl_free_tfds_in_queue(priv, sta_id,
tid, freed);
else {
if (sta_id == IWL_INVALID_STATION)
IWL_ERR(priv, "invalid station"");
}
Wey
next prev parent reply other threads:[~2010-04-08 19:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-08 17:16 [REVERT] be6b38bcb175613f239e0b302607db346472c6b6. v2.6.34-rc3-406 oops with 4965AGN wireless Jeff Chua
2010-04-08 17:19 ` Linus Torvalds
2010-04-08 19:47 ` Peter Zijlstra
2010-04-08 18:13 ` Al Viro
2010-04-08 20:09 ` Guy, Wey-Yi [this message]
2010-04-08 20:24 ` Guy, Wey-Yi
2010-04-08 18:50 ` Guy, Wey-Yi
-- strict thread matches above, loose matches on Subject: below --
2010-04-08 19:27 Jeff Chua
2010-04-08 19:42 ` Jeff Chua
2010-04-08 20:50 ` Guy, Wey-Yi
2010-04-08 20:02 ` John W. Linville
2010-04-08 21:28 ` Guy, Wey-Yi
[not found] ` <k2yb6a2187b1004081736td3a4c0f3uc05451902bec39a5@mail.gmail.com>
2010-04-09 3:15 ` Guy, Wey-Yi
2010-04-08 20:19 ` John W. Linville
2010-04-08 20:39 ` John W. Linville
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=1270757373.11853.11.camel@wwguy-ubuntu \
--to=wey-yi.w.guy@intel.com \
--cc=jeff.chua.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reinette.chatre@intel.com \
--cc=shanyu.zhao@intel.com \
--cc=stable@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@ZenIV.linux.org.uk \
/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