Messages in this thread | | | Date | Wed, 15 Oct 2003 03:25:39 -0700 | From | Andrew Morton <> | Subject | Re: Finding memory leak |
| |
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.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |