From: nmeyers@vestmark.com
To: linux-kernel@vger.kernel.org
Subject: Major slab mem leak with 2.6.17 / GCC 4.1.1
Date: Thu, 12 Oct 2006 20:49:18 -0400 [thread overview]
Message-ID: <20061013004918.GA8551@viviport.com> (raw)
Hello,
I've been chasing an OOM-death problem on 2.6.17 that showed up while
running a J2EE application on my recently-built Gentoo box. The crash
was ugly - leaking huge numbers of skbuff_head_cache and size-2048 slab
entries until my java processes died and the system became unusable
and unresponsive.
My environment is:
Gentoo kernel build 2.6.17-gentoo-r8, built with GCC 4.1.1.
I tried Catalin Marinas' kmemleak patches, and had to rebuild with
GCC 3.4.6 because of a 4.1.1 compiler bug that prevents compilation
of the patches.
And... building with 3.4.5 fixed the leak! So I guess I have very little
detail to report - except that there's a nasty leak in 2.6.17 when built
with 4.1.1.
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.
Nathan Meyers
nmeyers@vestmark.com
next reply other threads:[~2006-10-13 0:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-13 0:49 nmeyers [this message]
2006-10-13 5:56 ` Major slab mem leak with 2.6.17 / GCC 4.1.1 Pekka Enberg
2006-10-13 11:59 ` Catalin Marinas
2006-10-15 7:59 ` Mike Galbraith
2006-10-15 14:14 ` nmeyers
2006-10-15 17:59 ` Mike Galbraith
2006-10-18 13:59 ` Nathan Meyers
2006-10-16 5:32 ` Mike Galbraith
2006-10-16 8:07 ` Catalin Marinas
2006-10-16 9:08 ` Mike Galbraith
2006-10-16 8:44 ` Catalin Marinas
2006-10-16 9:33 ` Mike Galbraith
2006-10-13 8:25 ` Mike Galbraith
2006-10-13 10:55 ` nmeyers
2006-10-13 21:28 ` Mike Galbraith
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=20061013004918.GA8551@viviport.com \
--to=nmeyers@vestmark.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.