From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Crash on removal of 400 interfaces (3.7.6+)
Date: Tue, 19 Feb 2013 14:52:57 -0800 [thread overview]
Message-ID: <51240249.6060801@candelatech.com> (raw)
In-Reply-To: <1361225773.8555.50.camel@jlt4.sipsolutions.net>
On 02/18/2013 02:16 PM, Johannes Berg wrote:
> On Mon, 2013-02-18 at 14:14 -0800, Ben Greear wrote:
>> We often see crashes in work-queue processing when deleting
>> lots of wifi station interfaces. I'm guessing that there is probably
>> a work item that was not properly un-registered before deleting
>> memory. I have backported some wifi fixes from upstream, so
>> maybe they are to blame, but in case anyone has any suggestions
>> for places to look, please let me know.
>
> Enable CONFIG_DEBUG_OBJECTS and CONFIG_DEBUG_OBJECTS_WORK :)
That did not catch anything.
I have another data point that may shed some light: The test
case actually deletes the AP (on another machine) at the same
time it starts tearing down 200 stations on the first machine.
So, we are manually tearing down stations at the same time they
start timing out due to the AP disappearing, and any un-registering
that the stations might try are probably going to hit some failure cases
because the AP is of course not answering.
I could not reproduce this on a system that continually created
and tore down 400 stations against APs that remained stable and
active....
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2013-02-19 22:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 22:14 Crash on removal of 400 interfaces (3.7.6+) Ben Greear
2013-02-18 22:16 ` Johannes Berg
2013-02-19 22:52 ` Ben Greear [this message]
2013-02-19 23:24 ` Ben Greear
2013-02-19 23:46 ` Ben Greear
2013-02-20 0:39 ` Ben Greear
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=51240249.6060801@candelatech.com \
--to=greearb@candelatech.com \
--cc=johannes@sipsolutions.net \
--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).