From: Felix Fietkau <nbd@openwrt.org>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH] ath9k: fix beacon slot/buffer leak
Date: Tue, 19 Jan 2010 22:19:27 +0100 [thread overview]
Message-ID: <4B5621DF.60703@openwrt.org> (raw)
In-Reply-To: <43e72e891001191306m36984dc4o7f302612a071982c@mail.gmail.com>
On 2010-01-19 10:06 PM, Luis R. Rodriguez wrote:
> On Tue, Jan 19, 2010 at 11:51 AM, Felix Fietkau <nbd@openwrt.org> wrote:
>> When cleaning up beacon buffers and slots, ath9k currently checks if
>> sc->ah->opmode is set to a beacon related mode before cleaning up
>> buffers.
>> An unfortunate ordering of interface up/down commands can lead to
>> sc->ah->opmode being set to monitor mode, while there are AP interfaces
>> present on the same wiphy.
>> Always cleaning up beacon buffers if present fixes this issue.
>>
>
> CC stable?
Yeah, forgot about that. Should I send it again with Cc?
- Felix
next prev parent reply other threads:[~2010-01-19 21:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-19 19:51 [PATCH] ath9k: fix beacon slot/buffer leak Felix Fietkau
2010-01-19 21:06 ` Luis R. Rodriguez
2010-01-19 21:19 ` Felix Fietkau [this message]
2010-01-19 21:35 ` Luis R. Rodriguez
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=4B5621DF.60703@openwrt.org \
--to=nbd@openwrt.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@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.