From: Randy Dunlap <randy.dunlap@oracle.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: linux-mm@kvack.org, mpm@selenic.com,
Pekka Enberg <penberg@cs.helsinki.fi>
Subject: Re: build error: sparsemem + SLOB
Date: Mon, 20 Nov 2006 09:08:10 -0800 [thread overview]
Message-ID: <4561E0FA.4040508@oracle.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0611200855280.16845@schroedinger.engr.sgi.com>
Christoph Lameter wrote:
> On Sun, 19 Nov 2006, Randy Dunlap wrote:
>
>> mm/sparse.c: line 35 uses slab_is_available() but SLAB=n, SLOB=y.
>
> I wonder if its worth bothering about SLOB?
It's OK with me to make some combination of SLOB and SPARSEMEM
an invalid config, as long as that is implemented in Kconfig.
> 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.
>
> Is SLOB used at all or have we been lucky so far?
--
~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>
next prev parent reply other threads:[~2006-11-20 17:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-20 5:05 build error: sparsemem + SLOB 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 [this message]
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
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=4561E0FA.4040508@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=clameter@sgi.com \
--cc=linux-mm@kvack.org \
--cc=mpm@selenic.com \
--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 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.