From: Nick Piggin <npiggin@suse.de>
To: David Rientjes <rientjes@google.com>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
Ingo Molnar <mingo@elte.hu>, Janboe Ye <yuan-bo.ye@motorola.com>,
linux-kernel@vger.kernel.org, vegard.nossum@gmail.com,
graydon@redhat.com, fche@redhat.com, cl@linux-foundation.org
Subject: Re: [RFC][PATCH] Check write to slab memory which freed already using mudflap
Date: Fri, 10 Jul 2009 11:38:25 +0200 [thread overview]
Message-ID: <20090710093825.GJ14666@wotan.suse.de> (raw)
In-Reply-To: <alpine.DEB.2.00.0907100223140.14601@chino.kir.corp.google.com>
On Fri, Jul 10, 2009 at 02:31:43AM -0700, David Rientjes wrote:
> On Fri, 10 Jul 2009, Pekka Enberg wrote:
>
> > > I'm not sure what the status of slqb is, although I would have expected it
> > > to have been pushed for inclusion in 2.6.31 as a slab allocator
> > > alternative. Nick, any forecast for inclusion?
> >
> > 2.6.32 most likely. Nick has fixed a bunch of problems but there's still
> > one ppc boot time bug that's turning out to be hard to find.
> >
>
> Ah, ok, there's still outstanding bugs. I was curious as to why it wasn't
> merged as a non-default option that would have perhaps attracted more
> attention to it.
Don't know whether it should go in as non-default or not. The plan
is to kind of kick up a stink and make people care about the slab
issue again rather than quietly add more slab allocators to the
tree...
Perhaps making it non-default for one release would be a good idea,
I don't know.
next prev parent reply other threads:[~2009-07-10 9:38 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 16:13 [RFC][PATCH] Check write to slab memory which freed already using mudflap Janboe Ye
2009-07-09 16:44 ` Pekka Enberg
2009-07-09 19:40 ` Janboe Ye
2009-07-10 8:47 ` Ingo Molnar
2009-07-10 8:52 ` Pekka Enberg
2009-07-10 9:03 ` Nick Piggin
2009-07-10 9:14 ` Pekka Enberg
2009-07-10 9:29 ` Nick Piggin
2009-07-10 9:40 ` Pekka Enberg
2009-07-10 9:47 ` David Rientjes
2009-07-10 9:51 ` Pekka Enberg
2009-07-10 10:03 ` David Rientjes
2009-07-10 10:10 ` Pekka Enberg
2009-07-10 10:30 ` Nick Piggin
2009-07-15 14:59 ` Nick Piggin
2009-07-15 20:19 ` David Rientjes
2009-07-20 8:32 ` Nick Piggin
2009-07-10 9:41 ` David Rientjes
2009-07-10 9:46 ` Pekka Enberg
2009-07-10 9:04 ` David Rientjes
2009-07-10 9:19 ` Nick Piggin
2009-07-10 9:19 ` Pekka Enberg
2009-07-10 9:31 ` David Rientjes
2009-07-10 9:38 ` Nick Piggin [this message]
2009-07-10 18:55 ` Christoph Lameter
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=20090710093825.GJ14666@wotan.suse.de \
--to=npiggin@suse.de \
--cc=cl@linux-foundation.org \
--cc=fche@redhat.com \
--cc=graydon@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
--cc=rientjes@google.com \
--cc=vegard.nossum@gmail.com \
--cc=yuan-bo.ye@motorola.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 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.