From: Larry Finger <Larry.Finger@lwfinger.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-wireless@vger.kernel.org, bugme-daemon@bugzilla.kernel.org,
jckn@gmx.net, Johannes Berg <johannes@sipsolutions.net>,
Helmut Schaa <hschaa@suse.de>
Subject: Re: [Bugme-new] [Bug 10755] New: iwl3945 regression - NULL deref in ieee80211_associate
Date: Mon, 19 May 2008 18:48:42 -0500 [thread overview]
Message-ID: <483211DA.5080205@lwfinger.net> (raw)
In-Reply-To: <20080519162655.f79208cd.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Mon, 19 May 2008 15:56:01 -0700 (PDT)
> bugme-daemon@bugzilla.kernel.org wrote:
>
>> http://bugzilla.kernel.org/show_bug.cgi?id=10755
>>
>> Summary: iwl3945 regression - NULL deref in ieee80211_associate
>> Product: Drivers
>> Version: 2.5
>> KernelVersion: 2.6.26-rc3
>> Platform: All
>> OS/Version: Linux
>> Tree: Mainline
>> Status: NEW
>> Severity: normal
>> Priority: P1
>> Component: network-wireless
>> AssignedTo: drivers_network-wireless@kernel-bugs.osdl.org
>> ReportedBy: jckn@gmx.net
>>
>>
>> Latest working kernel version: 2.6.26-rc2
>> Earliest failing kernel version: 2.6.26-rc3
>> Distribution: Debian
>> Hardware Environment: Lenovo Thinkpad R61 (8943-DLG)
>> Software Environment:
>> Problem Description: iwl3945 trying to associate to an AP leads to a kernel
>> oops. The current (2008/05/19) linuxwireless.org compat-wireless driver is
>> affected, too.
>>
>
> A post-2.6.25 regression.
>
> EIP is at ieee80211_associate+0x253/0x640 [mac80211]
>
> and it might not be iwl3945-specific.
This bug looks like the one I found and reported in
http://marc.info/?l=linux-wireless&m=121097330013277&w=2. I found it for b43
- it is clearly not iwl3945 specific.
The patch is in version 4 and probably not the final one, but it fixes the
oops. You will find the patch at
http://marc.info/?l=linux-wireless&m=121120929012836&w=2.
We know that bss is NULL when mac80211 tries to associate; however, I had
only one of these that happened after my interface had been connected to my
AP for ~18 hours, then got disassociated, followed by the oops. It sounds as
if jckn@gmx.net might be getting this systematically and there is hope to
find the root cause so as to prevent the problem rather than covering over
the symptoms as is done with the patch. In any case, there is a fix in the works.
I have added Johannes and Helmut to the CC list.
Larry
prev parent reply other threads:[~2008-05-19 23:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-10755-10286@http.bugzilla.kernel.org/>
2008-05-19 23:26 ` [Bugme-new] [Bug 10755] New: iwl3945 regression - NULL deref in ieee80211_associate Andrew Morton
2008-05-19 23:48 ` Larry Finger [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=483211DA.5080205@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=hschaa@suse.de \
--cc=jckn@gmx.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).