From: Andrew Morton <akpm@osdl.org>
To: Holger Kiehl <Holger.Kiehl@dwd.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Finding memory leak
Date: Wed, 15 Oct 2003 03:25:39 -0700 [thread overview]
Message-ID: <20031015032539.4cfe71c7.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0310141345070.17096-100000@praktifix.dwd.de>
Holger Kiehl <Holger.Kiehl@dwd.de> wrote:
>
> - Is it correct to assume that an application cannot be the cause
> of the leak, ie. it can only be in kernel or a driver?
Yes.
> - How can I really prove that its the driver leaking the memory?
Look for instances of kmalloc(n, ...) for n in the range 1025 to 2048 which
do not have a matching kfree.
> - What is the meaning of size-2048 in slabinfo?
It is the pool which is used to satisfy kmalloc requests in the range 1025
to 2048 bytes inclusive.
next prev parent reply other threads:[~2003-10-15 10:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-15 10:05 Holger Kiehl
2003-10-15 10:25 ` Andrew Morton [this message]
2003-10-17 13:26 ` Holger Kiehl
2003-10-18 17:23 ` Jörn Engel
2003-10-18 17:46 ` Jörn Engel
2003-10-18 17:59 ` Jörn Engel
2003-10-19 7:56 ` Holger Kiehl
2003-10-20 4:23 ` David S. Miller
2003-10-22 11:14 ` Holger Kiehl
2003-10-19 7:48 ` Holger Kiehl
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=20031015032539.4cfe71c7.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=Holger.Kiehl@dwd.de \
--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®