From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: catalin.marinas@arm.com, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] kmemleak: Allow kmemleak to be built on powerpc
Date: Thu, 16 Jul 2009 07:31:00 -0400 [thread overview]
Message-ID: <20090716113100.GB7102@zod.rchland.ibm.com> (raw)
In-Reply-To: <1247730230.18228.5.camel@concordia>
On Thu, Jul 16, 2009 at 05:43:50PM +1000, Michael Ellerman wrote:
>On Thu, 2009-07-16 at 11:25 +1000, Michael Ellerman wrote:
>> Very lightly tested, doesn't crash the kernel.
>>
>> Signed-off-by: Michael Ellerman <michael@ellerman.id.au>
>> ---
>>
>> It doesn't look like we actually need to add any support in the
>> arch code - or is there something I'm missing?
>
>Hmm, I think we want to add annotations in lib/lmb.c don't we? That's
>our low-level pre-bootmem allocator.
>
>And we have the same problem with _edata as x86.
I'll point out that the Fedora developers enabled this in the rawhide kernels
for 3 days, and then turned it back off because most of the things found were
false positives.
Might still be worth poking at, but until it gets a bit less buggy itself it
could be a timesink.
josh
next prev parent reply other threads:[~2009-07-16 11:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 1:25 [PATCH] kmemleak: Allow kmemleak to be built on powerpc Michael Ellerman
2009-07-16 7:43 ` Michael Ellerman
2009-07-16 11:31 ` Josh Boyer [this message]
2009-07-16 13:16 ` Catalin Marinas
2009-07-16 17:52 ` Catalin Marinas
2009-07-17 0:29 ` Michael Ellerman
2009-07-17 8:26 ` Catalin Marinas
2009-07-17 8:32 ` Michael Ellerman
2009-07-17 8:41 ` 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=20090716113100.GB7102@zod.rchland.ibm.com \
--to=jwboyer@linux.vnet.ibm.com \
--cc=catalin.marinas@arm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=michael@ellerman.id.au \
/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).