Linux wireless drivers development
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: linux-wireless@vger.kernel.org, Johannes Berg <johannes.berg@intel.com>
Subject: Kernel oops in code added by "cfg80211: allow userspace to control supported rates in scan"
Date: Tue, 19 Jul 2011 17:42:56 -0400	[thread overview]
Message-ID: <4E25FA60.7040807@gnu.org> (raw)

Hello!

The current wireless-testing.git has a problem.  I'm trying to run 
wpa_supplicant on an interface created by carl9170 (with nl80211 
driver), and it oopses in nl80211_trigger_scan().  It turns out it 
oopses here:

for (i = 0; i < IEEE80211_NUM_BANDS; i++)
       request->rates[i] = (1 << wiphy->bands[i]->n_bitrates) - 1;

Here's the self-explanatory debug output I added:

[  460.190157] IEEE80211_NUM_BANDS = 2
[  460.193636] request = ffff8801246dc500
[  460.197373] request->rates = ffff8801246dc520
[  460.201748] wiphy = ffff8800b78b84e0
[  460.205317] wiphy->bands = ffff8800b78b8590
[  460.209489] i = 0, wiphy->bands[i] = ffffffffa00a80a0
[  460.214559] i = 1, wiphy->bands[i] =           (null)

wiphy->bands[1] is NULL, so wiphy->bands[1]->n_bitrates is invalid.

Likewise, if I run "iwconfig wlanX scan", I get an oops in 
cfg80211_wext_siwscan() on line 866:

for (i = 0; i < IEEE80211_NUM_BANDS; i++)
      creq->rates[i] = (1 << wiphy->bands[i]->n_bitrates) - 1;

Both pieces of code were added by:

commit 58389c69150e6032504dfcd3edca6b1975c8b5bc
Author: Johannes Berg <johannes.berg@intel.com>
Date:   Mon Jul 18 18:08:35 2011 +0200

     cfg80211: allow userspace to control supported rates in scan

-- 
Regards,
Pavel Roskin

             reply	other threads:[~2011-07-19 21:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-19 21:42 Pavel Roskin [this message]
2011-07-19 21:55 ` Kernel oops in code added by "cfg80211: allow userspace to control supported rates in scan" Johannes Berg
2011-07-19 22:01   ` Pavel Roskin
2011-07-19 22:26     ` Johannes Berg

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=4E25FA60.7040807@gnu.org \
    --to=proski@gnu.org \
    --cc=johannes.berg@intel.com \
    --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