From: Ben Greear <greearb@candelatech.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>
Subject: Re: kmemleak reports in kernel 3.9.5+
Date: Tue, 11 Jun 2013 17:28:13 -0700 [thread overview]
Message-ID: <51B7C09D.9020402@candelatech.com> (raw)
In-Reply-To: <51B78009.2060808@candelatech.com>
On 06/11/2013 12:52 PM, Ben Greear wrote:
> On 06/10/2013 03:32 PM, Catalin Marinas wrote:
>> On 10 June 2013 19:22, Ben Greear <greearb@candelatech.com> wrote:
>>> We had a system go OOM while doing lots of wireless
>>> stations. (System had 8GB of RAM, so I suspect a leak).
>>>
>>> I enabled kmemleak in a 3.9.5 (plus some local patches) and
>>> I see the entries below. Any idea if these are real or not?
Most of this went away when I disabled SLUB debugging and other
kernel hacking options. The wifi cfg80211_inform_bss_frame
remains, however. I'll go dig some more on that tomorrow...didn't
see anything obvious at first glance.
But, perhaps there could be some improvements to
kmemleak to make it deal better with the various kernel
debugging features?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2013-06-12 0:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-10 18:22 kmemleak reports in kernel 3.9.5+ Ben Greear
2013-06-10 22:32 ` Catalin Marinas
2013-06-11 18:36 ` Ben Greear
2013-06-11 19:52 ` Ben Greear
2013-06-12 0:28 ` Ben Greear [this message]
2013-06-13 15:50 ` Catalin Marinas
2013-06-17 22:45 ` Ben Greear
2013-06-13 15:48 ` Catalin Marinas
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=51B7C09D.9020402@candelatech.com \
--to=greearb@candelatech.com \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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