From: Pavel Roskin <proski@gnu.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/3] mac80211: cooperate more with network namespaces
Date: Sun, 26 Jul 2009 20:04:42 -0400 [thread overview]
Message-ID: <1248653082.3106.7.camel@mj> (raw)
In-Reply-To: <20090713223413.255405284@sipsolutions.net>
On Tue, 2009-07-14 at 00:33 +0200, Johannes Berg wrote:
> @@ -1900,10 +1880,16 @@ void ieee80211_tx_pending(unsigned long
>
> while (!skb_queue_empty(&local->pending[i])) {
> struct sk_buff *skb = __skb_dequeue(&local->pending[i]);
> + struct ieee80211_tx_info *info = IEEE80211_SKB_CB(skb);
> + struct ieee80211_sub_if_data *sdata;
> +
> + sdata = vif_to_sdata(info->control.vif);
> + dev_hold(sdata->dev);
I'm getting a panic at this point if I run hostapd on ath9k and a
Windows client tries to authenticate with a wrong WPA key.
Debugging shows that sdata->dev is NULL.
The current wireless-testing is affected. The revision preceding to
this patch is not affected.
CONFIG_NET_NS is not enabled. The architecture is x86_64.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2009-07-27 0:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-13 22:33 [PATCH 0/3] wireless network namespace work Johannes Berg
2009-07-13 22:33 ` [PATCH 1/3] mac80211: cooperate more with network namespaces Johannes Berg
2009-07-27 0:04 ` Pavel Roskin [this message]
2009-07-27 8:27 ` Johannes Berg
2009-07-27 15:34 ` Pavel Roskin
2009-07-27 15:59 ` Johannes Berg
2009-07-27 16:02 ` Johannes Berg
2009-07-27 16:12 ` Pavel Roskin
2009-07-27 16:40 ` Pavel Roskin
2009-07-27 18:22 ` Johannes Berg
2009-07-27 19:02 ` Pavel Roskin
2009-07-27 19:07 ` Johannes Berg
2009-07-27 17:30 ` Johannes Berg
2009-07-13 22:33 ` [PATCH 2/3] cfg80211: make aware of net namespaces Johannes Berg
2009-07-13 22:33 ` [PATCH 3/3] mac80211: allow using network namespaces Johannes Berg
2009-07-13 22:39 ` [HACK] mac80211: don't set netdev parent pointer 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=1248653082.3106.7.camel@mj \
--to=proski@gnu.org \
--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).