All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Mohammed Shafi <shafi.wireless@gmail.com>
Cc: Senthil Balasubramanian <senthilkumar@atheros.com>,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2 2/2] ath9k: Fix STA disconnect issue due to received MIC failed bcast frames
Date: Fri, 03 Dec 2010 00:04:44 -0800	[thread overview]
Message-ID: <4CF8A49C.2000401@candelatech.com> (raw)
In-Reply-To: <AANLkTinrQYN3_GpbfR=4xcJQ-moa32+QJtVorqq6xgR4@mail.gmail.com>

On 12/01/2010 11:16 PM, Mohammed Shafi wrote:
> On Thu, Dec 2, 2010 at 11:14 AM, Ben Greear<greearb@candelatech.com>  wrote:
>> On 12/01/2010 09:09 PM, Mohammed Shafi wrote:
>>>
>>> On Thu, Dec 2, 2010 at 1:28 AM, Ben Greear<greearb@candelatech.com>
>>>   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.
>>>
>>> Ben can you please give some more information(or just point out some
>>> link) regarding your test case,I can try it out.
>>> thanks,
>>> shafi
>>
>> Try this script, or something like it:
>>
>> http://www.spinics.net/lists/linux-wireless/msg60126.html
>>
>> Edit 'max' to create a small number of STA interfaces or you will probably
>> have
>> worse issues than them just not associating!
>>
>> You have to enable the nohwcrypt module option.
>>
>> Let me know if that doesn't work and I can probably put together something
>> more specific.
>
> thanks Ben.

Were you able to reproduce the problem?

Thanks,
Ben

>
>>
>> Thanks,
>> Ben
>>
>> --
>> Ben Greear<greearb@candelatech.com>
>> Candela Technologies Inc  http://www.candelatech.com
>>


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

  reply	other threads:[~2010-12-03  8:04 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 [this message]
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
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=4CF8A49C.2000401@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=senthilkumar@atheros.com \
    --cc=shafi.wireless@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.