From: Mike Galbraith <efault@gmx.de>
To: nmeyers@vestmark.com
Cc: Catalin Marinas <catalin.marinas@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: Major slab mem leak with 2.6.17 / GCC 4.1.1
Date: Sun, 15 Oct 2006 17:59:58 +0000 [thread overview]
Message-ID: <1160935198.6007.14.camel@Homer.simpson.net> (raw)
In-Reply-To: <20061015141437.GA29712@viviport.com>
On Sun, 2006-10-15 at 10:14 -0400, nmeyers@vestmark.com wrote:
> On Sun, Oct 15, 2006 at 07:59:14AM +0000, Mike Galbraith wrote:
> > On Fri, 2006-10-13 at 12:59 +0100, Catalin Marinas wrote:
> > > On 13/10/06, Pekka Enberg <penberg@cs.helsinki.fi> wrote:
> > > > On 10/13/06, nmeyers@vestmark.com <nmeyers@vestmark.com> 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.
> >
> > 2.6.19-rc1 + patch-2.6.19-rc1-kmemleak-0.11 compiles fine now (unless
> > CONFIG_DEBUG_KEEP_INIT is set), boots and runs too.. but axle grease
> > runs a lot faster ;-) I'll try a stripped down config sometime.
> >
> > -Mike
>
> Thanks for digging that up - I'm building gcc now and will let you
> know if any useful info emerges.
Buyer beware of course ;-)
-Mike
next prev parent reply other threads:[~2006-10-15 17:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-13 0:49 Major slab mem leak with 2.6.17 / GCC 4.1.1 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 [this message]
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=1160935198.6007.14.camel@Homer.simpson.net \
--to=efault@gmx.de \
--cc=catalin.marinas@gmail.com \
--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