linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Yasunori Goto <y-goto@jp.fujitsu.com>
Cc: Matt Mackall <mpm@selenic.com>, Hugh Dickins <hugh@veritas.com>,
	Christoph Lameter <clameter@sgi.com>,
	linux-mm@kvack.org, Pekka Enberg <penberg@cs.helsinki.fi>
Subject: Re: build error: sparsemem + SLOB
Date: Mon, 20 Nov 2006 22:59:15 -0800	[thread overview]
Message-ID: <20061120225915.0d9777d6.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20061121143253.51B5.Y-GOTO@jp.fujitsu.com>

On Tue, 21 Nov 2006 14:57:23 +0900 Yasunori Goto wrote:

> > On Mon, Nov 20, 2006 at 05:28:24PM +0000, Hugh Dickins wrote:
> > > On Mon, 20 Nov 2006, Christoph Lameter wrote:
> > > > 
> > > > As far as I can tell SLOB is fundamentally racy since it does not support 
> > > > SLAB_DESTROY_BY_RCU correctly. F.e. The constructor for the anon_vma will 
> > > > be called on alloc without regard for RCU, we free an item and reuse it 
> > > > without regard to RCU. This can potentially mess up the anon_vma locking 
> > > > state while we access it.
> > > 
> > > Good find!
> > > 
> > > > Is SLOB used at all or have we been lucky so far?
> > >
> > > Lucky so far.  Well, we'd actually have to be quite unlucky to ever
> > > see what page_lock_anon_vma/SLAB_DESTROY_BY_RCU are guarding against.
> > >
> > > But you're absolutely right that users should not be exposed to such
> > > unsafety.  I'd say SLOB should be disallowed if SMP.
> > 
> > SLOB is an O(N) allocator and is pretty poorly suited to running on
> > anything like a modern desktop. Disallowing if SMP is probably
> > reasonable, as even machines with multicore ARM or MIPS will probably
> > have enough memory to make SLOB a bit painful.
> 
> Ok. It's simple. This is fix.
> 
> ----
> 
> This is to disallow to make SLOB with SMP or SPARSEMEM.
> This avoids latent troubles of SLOB with SLAB_DESTROY_BY_RCU.
> And fix compile error.
> 
> This patch is for 2.6.19-rc5-mm2.
> 
> 
> Signed-off-by: Yasunori Goto <y-goto@jp.fujitsu.com>

Acked-by: Randy Dunlap <randy.dunlap@oracle.com>

Thanks.

> ----
>  init/Kconfig |    2 +-
>  1 files changed, 1 insertion(+), 1 deletion(-)
> 
> Index: 19-rc5-mm2/init/Kconfig
> ===================================================================
> --- 19-rc5-mm2.orig/init/Kconfig	2006-11-21 13:41:31.000000000 +0900
> +++ 19-rc5-mm2/init/Kconfig	2006-11-21 14:21:31.000000000 +0900
> @@ -465,7 +465,7 @@ config SHMEM
>  
>  config SLAB
>  	default y
> -	bool "Use full SLAB allocator" if EMBEDDED
> +	bool "Use full SLAB allocator" if (EMBEDDED && !SMP && !SPARSEMEM)
>  	help
>  	  Disabling this replaces the advanced SLAB allocator and
>  	  kmalloc support with the drastically simpler SLOB allocator.
> 
> 
> -- 

---
~Randy

--
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:[~2006-11-21  6:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-20  5:05 Randy Dunlap
2006-11-20 11:22 ` [PATCH]Re: " Yasunori Goto
2006-11-20 17:02   ` Randy Dunlap
2006-11-20 17:03 ` Christoph Lameter
2006-11-20 17:08   ` Randy Dunlap
2006-11-20 17:28   ` Hugh Dickins
2006-11-20 18:36     ` Matt Mackall
2006-11-21  5:57       ` Yasunori Goto
2006-11-21  6:59         ` Randy Dunlap [this message]
2006-11-21 13:34         ` Hugh Dickins
2006-11-21 19:14         ` Matt Mackall
2006-11-21 19:32           ` Christoph Lameter
2006-11-21 19:29             ` Matt Mackall
2006-11-21 19:54           ` Hugh Dickins
2006-11-20 21:22     ` Christoph Lameter
2006-11-21 13:31       ` Hugh Dickins

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=20061120225915.0d9777d6.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=clameter@sgi.com \
    --cc=hugh@veritas.com \
    --cc=linux-mm@kvack.org \
    --cc=mpm@selenic.com \
    --cc=penberg@cs.helsinki.fi \
    --cc=y-goto@jp.fujitsu.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