From: Mike Galbraith <efault@gmx.de>
To: nmeyers@vestmark.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Major slab mem leak with 2.6.17 / GCC 4.1.1
Date: Fri, 13 Oct 2006 08:25:12 +0000 [thread overview]
Message-ID: <1160727912.15431.11.camel@Homer.simpson.net> (raw)
In-Reply-To: <20061013004918.GA8551@viviport.com>
On Thu, 2006-10-12 at 20:49 -0400, nmeyers@vestmark.com wrote:
> 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.
Yeah, seems any remotely recent gcc hates it. That puts a rather large
dent in usability.
> 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 you build using 3.4.5 _without_ the kmemleak patches, do you see the
leak again? (ie is kmemleak altering timing, or is kernel miscompiled)
> 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.
I can only suggest trying latest/greatest to see if the issue is still
present, and if so, try to find a way that others may trigger it.
-Mike
next prev parent reply other threads:[~2006-10-13 6:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-13 0:49 nmeyers
2006-10-13 5:56 ` 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 [this message]
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=1160727912.15431.11.camel@Homer.simpson.net \
--to=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nmeyers@vestmark.com \
/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®