linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Rientjes <rientjes@google.com>
To: Christoph Lameter <cl@linux-foundation.org>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>, linux-mm@kvack.org
Subject: Re: slub: remove dynamic dma slab allocation
Date: Mon, 21 Jun 2010 12:56:21 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.00.1006211234230.8367@chino.kir.corp.google.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1006210919400.4513@router.home>

On Mon, 21 Jun 2010, Christoph Lameter wrote:

> > >  		if (slab_state == DOWN) {
> > > -			early_kmem_cache_node_alloc(gfpflags, node);
> > > +			early_kmem_cache_node_alloc(node);
> > >  			continue;
> > >  		}
> > >  		n = kmem_cache_alloc_node(kmalloc_caches,
> > > -						gfpflags, node);
> > > +						GFP_KERNEL, node);
> > >
> > >  		if (!n) {
> > >  			free_kmem_cache_nodes(s);
> >
> > Same here, this can still lead to GFP_KERNEL allocations from
> > kmem_cache_init() because slab_state is PARTIAL or UP.
> 
> You cannot do that here because this function is also used later when the
> slab is up. There is more in the percpu allocator which we are also trying
> to use to avoid having static kmem_cache_cpu declarations. GFP_KERNEL
> needs to be usable during early boot otherwise functions will have to add
> special casing for boot situations.
> 

The gfp_allowed_mask only changes once irqs are enabled, so either the 
gfpflags need to be passed into init_kmem_cache_nodes again or we need to 
do something like

	gfp_t gfpflags = irqs_disabled() ? GFP_NOWAIT : GFP_KERNEL;

locally.

The cleanest solution would probably be to extend slab_state to be set in 
kmem_cache_init_late() to determine when we're fully initialized, though.

> > > +	for (i = 0; i < SLUB_PAGE_SHIFT; i++) {
> > > +		struct kmem_cache *s = &kmalloc_caches[i];
> > > +
> > > +		if (s && s->size) {
> > > +			char *name = kasprintf(GFP_KERNEL,
> > > +				 "dma-kmalloc-%d", s->objsize);
> >
> > kasprintf() can return NULL which isn't caught by kmem_cache_open().
> 
> Then we will have a nameless cache. We could catch this with a WARN_ON()
> but does this work that early?
> 

It works, but this seems to be a forced

	if (WARN_ON(!name))
		continue;

because although it appears that s->name can be NULL within the slub 
layer, the sysfs layer would result in a NULL pointer dereference for 
things like strcmp() when looking up the cache's dirent.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2010-06-21 19:56 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-15 19:07 Christoph Lameter
2010-06-15 19:11 ` [RFC] slub: Simplify boot kmem_cache_cpu allocations Christoph Lameter
2010-06-16  8:53   ` Tejun Heo
2010-06-16 16:33     ` Christoph Lameter
2010-06-16 17:18       ` Tejun Heo
2010-06-16 17:35         ` Christoph Lameter
2010-06-17  8:49           ` Tejun Heo
2010-06-17  9:01             ` Pekka Enberg
2010-06-17 13:43             ` Christoph Lameter
2010-06-18 16:58               ` [PATCH 1/2] percpu: make @dyn_size always mean min dyn_size in first chunk init functions Tejun Heo
2010-06-18 17:29                 ` Christoph Lameter
2010-06-18 17:31                 ` Christoph Lameter
2010-06-18 17:39                   ` Tejun Heo
2010-06-18 18:03                     ` Christoph Lameter
2010-06-19  8:23                       ` Tejun Heo
2010-06-18 16:58               ` [PATCH 2/2] percpu: allow limited allocation before slab is online Tejun Heo
2010-06-18 22:30 ` slub: remove dynamic dma slab allocation David Rientjes
2010-06-21 14:25   ` Christoph Lameter
2010-06-21 19:56     ` David Rientjes [this message]
2010-06-21 20:32       ` Christoph Lameter
2010-06-21 21:08         ` David Rientjes

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=alpine.DEB.2.00.1006211234230.8367@chino.kir.corp.google.com \
    --to=rientjes@google.com \
    --cc=cl@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=penberg@cs.helsinki.fi \
    /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