linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: catalin.marinas@arm.com
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] kmemleak: Allow kmemleak to be built on powerpc
Date: Thu, 16 Jul 2009 17:43:50 +1000	[thread overview]
Message-ID: <1247730230.18228.5.camel@concordia> (raw)
In-Reply-To: <f18967360113efe4354a9ad0d71ead9a0f7579ea.1247707485.git.michael@ellerman.id.au>

[-- Attachment #1: Type: text/plain, Size: 1517 bytes --]

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.

And I'm seeing lots (~250) of these:

unreferenced object 0xc0000000fcd2e2f0 (size 16):
  comm "swapper", pid 1, jiffies 4294892393
  backtrace:
    [<c00000000014d9c0>] .create_object+0x164/0x2a8
    [<c00000000014dc94>] .kmemleak_alloc+0x74/0x120
    [<c0000000001474d0>] .__kmalloc+0x20c/0x2ac
    [<c00000000036998c>] .kvasprintf+0x64/0xb0
    [<c000000000360558>] .kobject_set_name_vargs+0x44/0xb4
    [<c0000000003f06d0>] .dev_set_name+0x50/0x6c
    [<c00000000042a794>] .scsi_sysfs_device_initialize+0xd0/0x16c
    [<c000000000426600>] .scsi_alloc_sdev+0x1c4/0x284
    [<c000000000426b50>] .scsi_probe_and_add_lun+0x144/0xbd4
    [<c0000000004279bc>] .__scsi_scan_target+0xfc/0x658
    [<c000000000427f90>] .scsi_scan_channel+0x78/0xe8
    [<c0000000004280cc>] .scsi_scan_host_selected+0xcc/0x154
    [<c00000000042823c>] .do_scsi_scan_host+0xe8/0x10c
    [<c0000000004286ec>] .scsi_scan_host+0x250/0x294
    [<c000000000456ef8>] .ibmvscsi_probe+0x4f8/0x630
    [<c000000000027418>] .vio_bus_probe+0x360/0x3cc


cheers

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-07-16  7:43 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 [this message]
2009-07-16 11:31   ` Josh Boyer
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=1247730230.18228.5.camel@concordia \
    --to=michael@ellerman.id.au \
    --cc=catalin.marinas@arm.com \
    --cc=linuxppc-dev@ozlabs.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).