mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pekka Enberg <penberg@kernel.org>
To: Anbu Manikandan <canbumanikandan@gmail.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>, linux-kernel@vger.kernel.org
Subject: Re: Kmemleak feature
Date: Wed, 9 May 2012 09:27:28 +0300 (EEST)	[thread overview]
Message-ID: <alpine.LFD.2.02.1205090925420.1879@tux.localdomain> (raw)
In-Reply-To: <CAAGB47N3oPkK1WhwzB7q4_6rvzKbnx3Ugwdr+aUuwTqiNX2oog@mail.gmail.com>

On Tue, 8 May 2012, Anbu Manikandan wrote:
> I am very much interested in learning about kmemleak feature in linux
> 3.0-RT kernel.
> I have already read the kmemleak document (Documentation/kmemleak.txt)
> provided in the kernel source.
> 
> Furthermore, I would like to understand the internal functionality of
> kmemleak source code.
> Could you please share some documents, links or presentations to
> understand the kmemleak internal functionality?

Catalin is the main author of kmemleak. I'm not aware of such 
presentations.

> One more thing, I have tried kmemleak test module in an ARM Target
> board(CortexA9 SMP Dual core Board) with 3.0-RT kernel and found that
> memory leak entries are not properly shown in
> sys/kernel/debug/kmemleak file.
> Instead of getting 25 memory leak entries in
> /sys/kernel/debug/kmemleak file, I have got only 5 memory leaks
> entries.
> May be the other memory leaks are called as false negatives as per the
> kmemleak document.
> Please suggest some way to overcome this problem.

I'm CC'ing LKML.

			Pekka

       reply	other threads:[~2012-05-09  6:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAAGB47OajENL-g-CvdAgp1k2XKU4dOWbHz=mDy79mPOvi-eEmQ@mail.gmail.com>
     [not found] ` <CAAGB47PiZ0cveWvObEjS8OPB++M3s1dENybnjoxyhQ8K_T4SpA@mail.gmail.com>
     [not found]   ` <CAAGB47PmB8o=mrnSoU1jYt_ecjH2WBLEzGRFqZWhWZXWQkTHaA@mail.gmail.com>
     [not found]     ` <CAAGB47PpTx9-eFz6ppbCYshA5yp293Tm1X-cAaBkZ+xX05_UUg@mail.gmail.com>
     [not found]       ` <CAAGB47N3oPkK1WhwzB7q4_6rvzKbnx3Ugwdr+aUuwTqiNX2oog@mail.gmail.com>
2012-05-09  6:27         ` Pekka Enberg [this message]
2012-05-09  8:22           ` Catalin Marinas
     [not found]             ` <CAAGB47NxugPZbV2ma-G7Aok5Xky=6AuyBGtis9U3hzNw8LDT0w@mail.gmail.com>
2012-05-10 17:21               ` 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=alpine.LFD.2.02.1205090925420.1879@tux.localdomain \
    --to=penberg@kernel.org \
    --cc=canbumanikandan@gmail.com \
    --cc=catalin.marinas@arm.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®