From: Larry Finger <Larry.Finger@lwfinger.net>
To: Kalle Valo <kvalo@codeaurora.org>, Severn <severn@xephris.net>,
Taehee Yoo <ap420073@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: rtlwifi NULL pointer dereference
Date: Sat, 06 Jun 2015 13:25:51 -0500 [thread overview]
Message-ID: <55733B2F.9090807@lwfinger.net> (raw)
In-Reply-To: <87fv65nfcn.fsf@kamboji.qca.qualcomm.com>
On 06/06/2015 08:20 AM, Kalle Valo wrote:
> Severn <severn@xephris.net> writes:
>
>> I've been hitting this NULL pointer deref with an rtl8188ee PCIE card.
>> It happens 100% of the time when I bring up a WPA2-PSK AP with hostapd
>> 2.4.
>>
>> If I revert 33511b157bbcebaef853cc1811992b664a2e5862, everything seems
>> to work properly.
>>
>> Below is my hostapd.conf and the crash log. This is mainline 4.0.4
>> with no patches.
>
> Below is the changelog for the commit. Larry & Taehee, what should we
> do?
>
> commit 33511b157bbcebaef853cc1811992b664a2e5862
> Author: Taehee Yoo <ap420073@gmail.com>
> Date: Wed Jan 21 16:58:19 2015 +0900
>
> rtlwifi: add support to send beacon frame.
>
> In AP mode, beacon frame is necessary to keep connection.
> this patch adds a sending beacon frame routine in initialization routine.
>
> Signed-off-by: Taehee Yoo <ap420073@gmail.com>
> Acked-by: Larry Finger <Larry.Finger@lwfinger.net>
> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Kalle,
I'm trying to find the missing setup step when the new interface is added to the
driver. Whatever it is is causing mac80211 to issue the warning at
net/mac80211/driver-ops.h:12. That problem appears to cascade to the NULL
pointer dereference. Any help would be appreciated.
Reversion of the above commit may be necessary, but I would like to see if we
can get a better "fix" as that commit is necessary for proper beaconing.
Larry
prev parent reply other threads:[~2015-06-06 18:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-05 1:27 rtlwifi NULL pointer dereference Severn
2015-06-06 13:20 ` Kalle Valo
2015-06-06 18:25 ` 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=55733B2F.9090807@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=ap420073@gmail.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=severn@xephris.net \
/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.