From: Ben Greear <greearb@candelatech.com>
To: Eliad Peller <eliad@wizery.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: lockdep splat related to wifi regulatory in 3.3.6+
Date: Mon, 21 May 2012 09:26:59 -0700 [thread overview]
Message-ID: <4FBA6CD3.8020201@candelatech.com> (raw)
In-Reply-To: <CAB3XZEem=2P36WgWXynoscemAhMrcgh0mKFocBbGhy8C-cJigQ@mail.gmail.com>
On 05/19/2012 03:42 PM, Eliad Peller wrote:
> hi Ben,
>
> On Sat, May 19, 2012 at 1:45 AM, Ben Greear<greearb@candelatech.com> wrote:
>> This appears to be this bug:
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=734519
>>
>> Test case was to create 40 (virtual) stations against an AP that can only
>> handle
>> 30, so the remaining 10 constantly try to re-associate, get DHCP if
>> they manage, etc....
Thanks, I will try your patch.
But, it has a fairly scary comment about race conditions.
Any idea why sort of symptoms I might see from this potential
race?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2012-05-21 16:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-18 22:45 lockdep splat related to wifi regulatory in 3.3.6+ Ben Greear
2012-05-19 22:42 ` Eliad Peller
2012-05-21 16:26 ` Ben Greear [this message]
2012-05-21 16:48 ` Eliad Peller
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=4FBA6CD3.8020201@candelatech.com \
--to=greearb@candelatech.com \
--cc=eliad@wizery.com \
--cc=linux-wireless@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).