From: Larry Finger <Larry.Finger@lwfinger.net>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: wireless <linux-wireless@vger.kernel.org>
Subject: Re: NULL pointer in mac80211:ieee80211_associate
Date: Fri, 16 May 2008 18:05:40 -0500 [thread overview]
Message-ID: <482E1344.7080808@lwfinger.net> (raw)
In-Reply-To: <1210974434.6381.60.camel@johannes.berg>
Johannes Berg wrote:
> Larry,
>
>> I think this report is new. If it is a duplicate, I apologize for any noise.
>
> I've definitely not seen it before, thanks.
>
>> The system was last booted at 18:02 on May 15. Until 10:10:58, everything
>> seemed normal. Then a reason 3 deauthentication arrived, and the following
>> ensued:
>
> Actually, the deauthentication is what you're sending, see
> ieee80211_sta_deauthenticate (in mlme.c). Any idea why it would be sent?
> Did you kill wpa_supplicant or something similar?
No, I was just working at the reverse engineering for the LP-PHY code without
using the network. When I went to check for new E-mail, I found that the b43
device was off line. Whne it wouldn't reconnect, I found the error message in
the logs.
> In any case, we wouldn't expect to get a deauth with reason 15
> (WLAN_REASON_4WAY_HANDSHAKE_TIMEOUT) then. Hmm. Maybe that's why
> wpa_supplicant was trying to disassociate as well?
>
> Still, we should of course not crash :)
>
>> May 16 10:10:58 larrylap kernel: eth1: deauthenticate(reason=3)
>> May 16 10:10:58 larrylap kernel: eth1: RX deauthentication from 00:1a:70:46:ba:b1 (reason=15)
>> May 16 10:10:58 larrylap kernel: eth1: deauthenticated
>> May 16 10:10:58 larrylap avahi-daemon[3042]: Withdrawing address record for
>> 192.168.1.122 on eth1.
>> May 16 10:10:58 larrylap avahi-daemon[3042]: Leaving mDNS multicast
>> group on interface eth1.IPv4 with address 192.168.1.122.
>> May 16 10:10:58 larrylap avahi-daemon[3042]: Interface eth1.IPv4 no longer
>> relevant for mDNS.
>> May 16 10:10:59 larrylap kernel: eth1: authenticate with AP 00:1a:70:46:ba:b1
>> May 16 10:10:59 larrylap kernel: eth1: RX authentication from
>> 00:1a:70:46:ba:b1 (alg=0 transaction=2 status=0)
>> May 16 10:10:59 larrylap kernel: eth1: authenticated
>> May 16 10:10:59 larrylap kernel: eth1: associate with AP 00:1a:70:46:ba:b1
>> May 16 10:10:59 larrylap kernel: BUG: unable to handle kernel NULL pointer dereference at 00000000000000c0
>> May 16 10:10:59 larrylap kernel: IP: [<ffffffffa0159eb1>] :mac80211:ieee80211_associate+0x2ba/0x53e
>> May 16 10:10:59 larrylap kernel: PGD b8258067 PUD b8259067 PMD 0
>> May 16 10:10:59 larrylap kernel: Oops: 0000 [1] SMP
>
> I can definitely not place this, though.
>
> Can you try to find out what code this corresponds to?
From objdump with line numbers, it occurs at "for (i = 0; i <
bss->supp_rates_len; i++) {" in ieee80211_compatible_rates, which I think is
entered from ieee80211_send_assoc. It seems that bss is NULL. For testing, I
have placed a WARN_ON(!bss) statement just before the for loop.
Larry
next prev parent reply other threads:[~2008-05-16 23:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-16 21:28 NULL pointer in mac80211:ieee80211_associate Larry Finger
2008-05-16 21:47 ` Johannes Berg
2008-05-16 23:05 ` Larry Finger [this message]
2008-05-16 23:09 ` Johannes Berg
2008-05-17 16:50 ` Helmut Schaa
2008-05-17 16:56 ` 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=482E1344.7080808@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=johannes@sipsolutions.net \
--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).