From: Larry Finger <Larry.Finger@lwfinger.net>
To: Dan Williams <dcbw@redhat.com>
Cc: Tomas Winkler <tomasw@gmail.com>, Helmut Schaa <hschaa@suse.de>,
John Linville <linville@tuxdriver.com>,
Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCHv2] mac80211: fix NULL pointer dereference in ieee80211_compatible_rates
Date: Sun, 18 May 2008 10:14:37 -0500 [thread overview]
Message-ID: <483047DD.2050205@lwfinger.net> (raw)
In-Reply-To: <1211117578.686.12.camel@localhost.localdomain>
Dan Williams wrote:
> On Sun, 2008-05-18 at 13:37 +0300, Tomas Winkler wrote:
>> Again, mac should rather solve the problem that we do not connect to
>> AP's that are not in the BSS list
>> Personally I would NACK this as it's just hiding the real problem
>
> Ugh; is that what's happening? If the AP isn't in the BSS list of the
> card, then the card shouldn't be connecting to it. It should have been
> probe-scanned already and thus exist in the BSS list, right?
>
> Dan
>
>> The other issue is that we call ieee80211_rx_bss_put(dev, bss); before
>> this call in ieee80211_send_assoc.
This AP certainly should have been in the BSS list. As I stated in the
original post, the system had been connected to that AP for about 18 hours
before the NULL bss NULL event occurred.
Clearly the sequence of events is improbable and it may be some time before
it happens again. What diagnostic information would be useful to capture
if/when it occurs? Is there any other location that I should monitor?
Larry
next prev parent reply other threads:[~2008-05-18 15:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-17 18:35 [PATCHv2] mac80211: fix NULL pointer dereference in ieee80211_compatible_rates Helmut Schaa
2008-05-18 10:37 ` Tomas Winkler
2008-05-18 13:32 ` Dan Williams
2008-05-18 15:14 ` Larry Finger [this message]
2008-05-19 11:07 ` Dan Williams
2008-05-19 11:37 ` Helmut Schaa
2008-05-19 12:41 ` Johannes Berg
2008-05-19 16:44 ` Tomas Winkler
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=483047DD.2050205@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=dcbw@redhat.com \
--cc=hschaa@suse.de \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=tomasw@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.