From: Johannes Berg <johannes@sipsolutions.net>
To: Chun-Yeow Yeoh <yeohchunyeow@gmail.com>
Cc: linux-wireless@vger.kernel.org, linville@tuxdriver.com,
devel@lists.open80211s.org
Subject: Re: [PATCH] mac80211: fix the kernel panic on ath_tx_aggr_wakeup on mesh
Date: Fri, 21 Jun 2013 22:48:53 +0200 [thread overview]
Message-ID: <1371847733.8936.6.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1371803215-2685-1-git-send-email-yeohchunyeow@gmail.com> (sfid-20130621_103004_439845_20E28F3A)
On Fri, 2013-06-21 at 16:26 +0800, Chun-Yeow Yeoh wrote:
> The is to fix the kernel panic happens if user space inserts the mesh
> STA and not proceed with the SAE and AMPE, and later the same mesh STA
> is detected again. The sta_state of the mesh STA remains at
> IEEE80211_STA_NONE and if the ieee80211_sta_ps_deliver_wakeup
> is called and subsequently the ath_tx_aggr_wakeup, the kernel panic due
> to ath_tx_node_init is not called before to initialize the require data
> structures.
I'd like to have a less ath9k-centric description, and particularly
subject, please.
> Thomas Perdersen
I think you misspelled that :)
> also mentioned that this patch has fixed the
> bad sta magic warning in mac80211_hwsim_set_tim() when applied to
> mac80211-next/master
"The bad sta magic warning"? That sounds like everyone should know about
that, but I don't think I do, or maybe it just slipped my mind?
johannes
next prev parent reply other threads:[~2013-06-21 20:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 8:26 [PATCH] mac80211: fix the kernel panic on ath_tx_aggr_wakeup on mesh Chun-Yeow Yeoh
2013-06-21 20:48 ` Johannes Berg [this message]
2013-06-24 0:44 ` Yeoh Chun-Yeow
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=1371847733.8936.6.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=devel@lists.open80211s.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=yeohchunyeow@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox