Re: build error: sparsemem + SLOB

Christoph Lameter
2006-11-20T17:03:30Z

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?

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?