From: Dave Young <hidave.darkstar@gmail.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: mmotm 2010-06-03-16-36 lots of suspected kmemleak
Date: Fri, 4 Jun 2010 21:55:05 +0800 [thread overview]
Message-ID: <AANLkTillFhDzhz06IXArHKbZCy9zBI5Isl4c2DiROXlz@mail.gmail.com> (raw)
In-Reply-To: <tnxvd9zcbr9.fsf@e102109-lin.cambridge.arm.com>
On Fri, Jun 4, 2010 at 6:50 PM, Catalin Marinas <catalin.marinas@arm.com> wrote:
> Dave Young <hidave.darkstar@gmail.com> wrote:
>> With mmotm 2010-06-03-16-36, I gots tuns of kmemleaks
>
> Do you have CONFIG_NO_BOOTMEM enabled? I posted a patch for this but
> hasn't been reviewed yet (I'll probably need to repost, so if it fixes
> the problem for you a Tested-by would be nice):
>
> http://lkml.org/lkml/2010/5/4/175
I'd like to test, but I can not access the test pc during weekend. So
I will test it next monday.
For CONFIG_NO_BOOTMEM, I don't remember. I guess set as 'y'
>
> Thanks.
>
> --
> Catalin
>
--
Regards
dave
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-06-04 13:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-04 8:27 mmotm 2010-06-03-16-36 lots of suspected kmemleak Dave Young
2010-06-04 10:50 ` Catalin Marinas
2010-06-04 13:55 ` Dave Young [this message]
2010-06-07 5:20 ` Dave Young
2010-06-07 9:19 ` Catalin Marinas
2010-06-07 10:00 ` Dave Young
2010-06-07 16:43 ` Catalin Marinas
2010-06-08 1:37 ` Dave Young
2010-06-09 2:37 ` Dave Young
2010-06-09 2:44 ` Dave Young
2010-06-09 9:19 ` Dave Young
2010-06-10 1:16 ` [PATCH -mm] only drop root anon_vma if not self Rik van Riel
2010-06-10 1:30 ` Dave Young
2010-06-10 11:21 ` Catalin Marinas
2010-06-11 8:08 ` Dave Young
2010-06-11 9:17 ` Catalin Marinas
2010-06-11 9:30 ` Dave Young
2010-06-11 9:48 ` Dave Young
2010-06-11 10:06 ` Catalin Marinas
2010-06-12 1:50 ` Dave Young
2010-06-07 8:30 ` mmotm 2010-06-03-16-36 lots of suspected kmemleak Dave Young
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=AANLkTillFhDzhz06IXArHKbZCy9zBI5Isl4c2DiROXlz@mail.gmail.com \
--to=hidave.darkstar@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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).