public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Justin Schoeman <justin@expertron.co.za>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Tracing memory leaks (slabs) in 2.6.9+ kernels?
Date: Wed, 02 Mar 2005 10:17:15 +0200	[thread overview]
Message-ID: <4225768B.3010005@expertron.co.za> (raw)

Hi,

I am having a problem with memory leaking on a patched kernel.  In order 
to pinpoint the leak, I would like to try to trace the allocation points 
for the memory.

I have found some vague references to patches that allow the user to 
dump the caller address for slab allocations, but I cannot find the 
patch itself.

Can anybody please point me in the right direction - either for that 
patch, or any other way to track down leaking slabs?

Thank you,
Justin Schoeman

             reply	other threads:[~2005-03-02  8:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-02  8:17 Justin Schoeman [this message]
2005-03-02  9:24 ` Tracing memory leaks (slabs) in 2.6.9+ kernels? Andrew Morton
2005-03-02 13:32   ` OGAWA Hirofumi
2005-03-02 16:32     ` Andrew Morton
2005-03-02 19:46       ` Manfred Spraul
2005-03-03 12:19   ` Justin Schoeman
2005-03-03 12:26     ` Andrew Morton
2005-03-04  7:48       ` Justin Schoeman
2005-03-04  7:56         ` Andrew Morton
2005-03-02  9:31 ` Alexander Nyberg

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=4225768B.3010005@expertron.co.za \
    --to=justin@expertron.co.za \
    --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