linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jean-Pierre Tosoni" <jp.tosoni@acksys.fr>
To: <linux-wireless@vger.kernel.org>
Subject: get_expected_throughput introduces a kernel oops on sta_set_sinfo calls
Date: Tue, 22 Jul 2014 11:11:07 +0200	[thread overview]
Message-ID: <004101cfa58c$e0ccb3f0$a2661bd0$@acksys.fr> (raw)

Hi list,

I am using compat-wireless-20132-04-16 with kernel 3.3.8.
I experienced a kernel oops after applying the "get_expected_throughput"
patches series from Antonio Quartulli.
It happens when a station_dump is issued from userspace while an association
has begun but does not complete immediately due to bad channel.
After some debugging I made this patch which solves the issue:
===========================================================================
--- a/net/mac80211/rc80211_minstrel.c
+++ b/net/mac80211/rc80211_minstrel.c
@@@ -708,6 +708,15 @@ static u32 minstrel_get_expected_throughput(
 	struct minstrel_sta_info *mi = priv_sta;
 	int idx = mi->max_tp_rate[0];
 
+	if (!mi->r) {
+		/*
+		 * Happens if get_expected_throughput() is called by
+		 * ieee80211_dump_station during association from HT
+		 * client to AP, before getting the HT IE from the AP
+		 */
+		printk(KERN_ERR "minstrel: uninitialized station rates");
+		return 0; /* value suggested by J. Berg 25-apr-2014 */
+	}
 	/* convert pkt per sec in kbps (1200 is the average pkt size used
for
 	 * computing cur_tp
 	 */
===========================================================================

With this patch I get this trace (the timeout is expected, since the SNR is
very low):

[  359.798796] wlan0: authenticate with 92:a4:de:21:4f:85

[  359.813180] wlan0: direct probe to 92:a4:de:21:4f:85 (try 1/3)

[  359.922306] wlan0: direct probe to 92:a4:de:21:4f:85 (try 2/3)

[  360.005424] minstrel: uninitialized station rates

[  360.030318] wlan0: direct probe to 92:a4:de:21:4f:85 (try 3/3)

[  360.138294] wlan0: authentication with 92:a4:de:21:4f:85 timed out

Maybe station_dump should not dump the stations just created by an
yet-unanswered authentication request?
Or is my patch the right thing to do?

Regards
Jean-Pierre Tosoni


             reply	other threads:[~2014-07-22  9:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-22  9:11 Jean-Pierre Tosoni [this message]
2014-07-22 13:47 ` get_expected_throughput introduces a kernel oops on sta_set_sinfo calls Felix Fietkau
2014-07-22 14:55   ` Jean-Pierre Tosoni
2014-07-22 18:57     ` Felix Fietkau

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='004101cfa58c$e0ccb3f0$a2661bd0$@acksys.fr' \
    --to=jp.tosoni@acksys.fr \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).