From: "John W. Linville" <linville@tuxdriver.com>
To: Ben Greear <greearb@candelatech.com>
Cc: Senthil Balasubramanian <senthilkumar@atheros.com>,
linux-wireless@vger.kernel.org, Stable <stable@kernel.org>,
Kyungwan Nam <Kyungwan.Nam@atheros.com>
Subject: Re: [PATCH v2 2/2] ath9k: Fix STA disconnect issue due to received MIC failed bcast frames
Date: Thu, 2 Dec 2010 14:17:05 -0500 [thread overview]
Message-ID: <20101202191705.GB2358@tuxdriver.com> (raw)
In-Reply-To: <4CF6A8FD.6020508@candelatech.com>
On Wed, Dec 01, 2010 at 11:58:53AM -0800, Ben Greear wrote:
> On 12/01/2010 03:00 AM, Senthil Balasubramanian wrote:
> >AR_RxKeyIdxValid will not be set for bcast/mcast frames and so relying
> >this status for MIC failed frames is buggy.
> >
> >Due to this, MIC failure events for broadcast frames are not sent to
> >supplicant resulted in AP disconnecting the STA.
> >
> >Able to pass Wifi Test case 5.2.18 with this fix.
>
> Please do not apply this yet. As far as I can tell, either
> of these patches breaks multiple VIF scenarios. I'm not
> sure exactly why, but I had to revert this to get any
> of my interfaces to associate.
I'm reverting v1 and ignoring v2 on the basis of this report.
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2010-12-02 19:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 11:00 [PATCH v2 2/2] ath9k: Fix STA disconnect issue due to received MIC failed bcast frames Senthil Balasubramanian
2010-12-01 19:58 ` Ben Greear
2010-12-02 5:09 ` Mohammed Shafi
2010-12-02 5:44 ` Ben Greear
2010-12-02 7:16 ` Mohammed Shafi
2010-12-03 8:04 ` Ben Greear
2010-12-03 8:20 ` [ath9k-devel] " Mohammed Shafi
2010-12-03 14:17 ` Senthil Balasubramanian
2010-12-03 17:58 ` Ben Greear
2010-12-06 11:31 ` Senthil Balasubramanian
2010-12-02 19:17 ` John W. Linville [this message]
2010-12-03 8:44 ` Senthil Balasubramanian
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=20101202191705.GB2358@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=Kyungwan.Nam@atheros.com \
--cc=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
--cc=senthilkumar@atheros.com \
--cc=stable@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 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.