Re: Major slab mem leak with 2.6.17 / GCC 4.1.1

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: "[email protected]" <[email protected]>
Subject: Re: Major slab mem leak with 2.6.17 / GCC 4.1.1
From: "Pekka Enberg" <[email protected]>
Date: Fri, 13 Oct 2006 08:56:16 +0300
Cc: [email protected], "Catalin Marinas" <[email protected]>
In-reply-to: <[email protected]>
References: <[email protected]>
Sender: [email protected]

On 10/13/06, [email protected] <[email protected]> wrote:

If anyone has a version of kmemleak that I can build with 4.1.1, or
any other suggestions for instrumentation, I'd be happy to gather more
data - the problem is very easy for me to reproduce.


You should cc Catalin for that. Alternatively, you could try
CONFIG_DEBUG_SLAB_LEAK.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: Major slab mem leak with 2.6.17 / GCC 4.1.1
  - From: "Catalin Marinas" <[email protected]>

References:
- Major slab mem leak with 2.6.17 / GCC 4.1.1
  - From: [email protected]

Prev by Date: Re: Can context switches be faster?
Next by Date: Re: [PATCH] Redefine instances of sema_init() to use standard form.
Previous by thread: Major slab mem leak with 2.6.17 / GCC 4.1.1
Next by thread: Re: Major slab mem leak with 2.6.17 / GCC 4.1.1
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]

Powered by Linux