All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Felix Fietkau <nbd@openwrt.org>
Cc: Arend van Spriel <arend@broadcom.com>,
	"linville@tuxdriver.com" <linville@tuxdriver.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2] mac80211: minstrel_ht: fix NULL pointer dereference during auth/assoc
Date: Thu, 09 Feb 2012 09:04:54 +0100	[thread overview]
Message-ID: <4F337E26.6030901@sipsolutions.net> (raw)
In-Reply-To: <4F32B3A5.5020903@openwrt.org>

On 2/8/2012 6:40 PM, Felix Fietkau wrote:
>> I will test it. So basically we don't want to do rate control for
>> management frames like AUTH and ASSOC?
> Right. That's already handled like this by the current code, only the tx
> status path was left out (probably accidentally).

Yes, my mistake, I forgot about TX status path. Thanks everyone for 
taking care of this!

johannes

  reply	other threads:[~2012-02-09  8:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-08 12:44 [PATCH v2] mac80211: minstrel_ht: fix NULL pointer dereference during auth/assoc Arend van Spriel
2012-02-08 15:56 ` Larry Finger
2012-02-08 16:08 ` Felix Fietkau
2012-02-08 16:27   ` Arend van Spriel
2012-02-08 16:45     ` Larry Finger
2012-02-08 17:06     ` Felix Fietkau
2012-02-08 17:29       ` Felix Fietkau
2012-02-08 17:35         ` Arend van Spriel
2012-02-08 17:40           ` Felix Fietkau
2012-02-09  8:04             ` Johannes Berg [this message]
2012-02-08 18:04         ` Arend van Spriel
2012-02-08 18:27           ` Larry Finger
     [not found]       ` <CALSq=Bb5s+3cc8yX=fL2LOjJWSyxQSF728KE9ODLSBERNjj5mQ@mail.gmail.com>
2012-02-08 17:33         ` Arend van Spriel
2012-02-08 19:53 ` Arend van Spriel

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=4F337E26.6030901@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=arend@broadcom.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=nbd@openwrt.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 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.