Re: memory clobber in rx path, maybe related to ath9k.

[Ben Greear <greearb@candelatech.com>]

On 10/14/2010 04:39 PM, Luis R. Rodriguez wrote:
> On Thu, Oct 14, 2010 at 4:30 PM, Ben Greear<greearb@candelatech.com>  wrote:
>> On 10/14/2010 04:19 PM, Luis R. Rodriguez wrote:
>>>
>>> Ok please try this patch, it cures it for me.
>>
>> Well, it got a lot further than normal, but it still
>> hit the poison check after a few minutes.
>>
>> Current test case is my app loading 130 or so stations, each running
>> wpa_supplicant.  All were created, and quite a few had associated
>> when the poison check hit.
>>
>> So, it definitely looks like a step in the right direction, but
>> not fully fixed yet.
>>
>> I'll do some more testing with this patch applied and using just my
>> perl script to make sure the problem is reproducible outside of my
>> application.
>
> Ok, whatever userspace does it should not corrupt to kernel, unless
> its poking /dev/mem

Sure, but it's nice to have a simpler test case.

I ran my script with 32 stations for maybe 20 minutes...seemed to be doing
OK as far as stability goes..then it crashed in the divide-by-zero ani thing.

I have to run home now, but I'll try my script with more interfaces
and/or some traffic mix, etc, to see if I can get another reasonable way
to reproduce this w/out my big binary application.

I can also work on the divide-by-zero bug if no one beats me to it.

Thanks,
Ben

>
>    Luis


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