mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Christoph Lameter <cl@linux-foundation.org>,
	akpm@linux-foundation.org, gorcunov@openvz.org,
	kosaki.motohiro@jp.fujitsu.com, mel@csn.ul.ie, riel@redhat.com,
	linux-kernel@vger.kernel.org, rientjes@google.com
Subject: Re: [PATCH 2/2] SLUB: Use GFP_PANIC for early-boot allocations
Date: Sat, 9 May 2009 10:30:48 +0200	[thread overview]
Message-ID: <20090509083048.GB3656@elte.hu> (raw)
In-Reply-To: <1241797341.28600.66.camel@penberg-laptop>


* Pekka Enberg <penberg@cs.helsinki.fi> wrote:

> On Fri, 2009-05-08 at 11:28 -0400, Christoph Lameter wrote:
> > On Fri, 8 May 2009, Pekka Enberg wrote:
> > 
> > > This patch converts SLUB early-boot code to use GFP_PANIC instead of explicit
> > > BUG_ON() calls.
> > 
> > Yirks this is not only early boot code. create_unique_id may be executed
> > whenever a slab is created.
> 
> Updated patch here:
> 
> Subject: [PATCH 2/2] SLUB: Use GFP_PANIC for early-boot allocations
> From: Pekka Enberg <penberg@cs.helsinki.fi>
> 
> This patch converts SLUB early-boot code to use GFP_PANIC instead of BUG_ON().
> 
> Signed-off-by: Pekka Enberg <penberg@cs.helsinki.fi>

thanks Pekka!

Acked-by: Ingo Molnar <mingo@elte.hu>

	Ingo

      reply	other threads:[~2009-05-09  8:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-08 15:10 Pekka Enberg
2009-05-08 15:23 ` Cyrill Gorcunov
2009-05-08 15:28 ` Christoph Lameter
2009-05-08 15:36   ` Pekka Enberg
2009-05-08 15:42     ` Peter Zijlstra
2009-05-08 15:45       ` Pekka Enberg
2009-05-08 15:50         ` Peter Zijlstra
2009-05-08 16:15           ` Cyrill Gorcunov
2009-05-08 16:31             ` Peter Zijlstra
2009-05-08 16:42               ` Christoph Lameter
2009-05-08 16:49               ` Cyrill Gorcunov
2009-05-09  8:30               ` Ingo Molnar
2009-05-08 15:42   ` Pekka Enberg
2009-05-09  8:30     ` Ingo Molnar [this message]

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=20090509083048.GB3656@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux-foundation.org \
    --cc=gorcunov@openvz.org \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mel@csn.ul.ie \
    --cc=penberg@cs.helsinki.fi \
    --cc=riel@redhat.com \
    --cc=rientjes@google.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®