From: Johannes Berg <johannes@sipsolutions.net>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: linux-wireless@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Possible memory leak in net/wireless/scan.c
Date: Wed, 08 Jul 2009 05:06:53 +0200 [thread overview]
Message-ID: <1247022413.4755.56.camel@johannes.local> (raw)
In-Reply-To: <1246986269.9451.105.camel@pc1117.cambridge.arm.com>
[-- Attachment #1: Type: text/plain, Size: 391 bytes --]
On Tue, 2009-07-07 at 18:04 +0100, Catalin Marinas wrote:
> Hi,
>
> I'm investigating several kmemleak reports like the one below (it could
> as well be a false positive but it needs more digging):
By the way, what kind of machine do you need for kmemleak to be
feasible? I tried booting a kernel with it in kvm on my 2 ghz laptop,
and that was completely unfeasible.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2009-07-08 3:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-07 17:04 Possible memory leak in net/wireless/scan.c Catalin Marinas
2009-07-07 17:12 ` Johannes Berg
2009-07-07 21:29 ` Catalin Marinas
2009-07-07 21:47 ` Johannes Berg
2009-07-08 3:06 ` Johannes Berg [this message]
2009-07-08 8:46 ` Catalin Marinas
2009-07-08 10:24 ` Johannes Berg
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=1247022413.4755.56.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--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