linux-toradex.git/include/linux/slab.h, branch Colibri_T30_LinuxImageV2.1Beta2_20140206

slab allocators: Provide generic description of alignment defines

2011-07-07T18:04:12+00:00

Provide description for alignment defines.

Acked-by: David Rientjes 
Signed-off-by: Christoph Lameter 
Signed-off-by: Pekka Enberg

slab, slub, slob: Unify alignment definition

2011-06-16T16:40:20+00:00

Every slab has its on alignment definition in include/linux/sl?b_def.h. Extract those
and define a common set in include/linux/slab.h.

SLOB: As notes sometimes we need double word alignment on 32 bit. This gives all
structures allocated by SLOB a unsigned long long alignment like the others do.

SLAB: If ARCH_SLAB_MINALIGN is not set SLAB would set ARCH_SLAB_MINALIGN to
zero meaning no alignment at all. Give it the default unsigned long long alignment.

Signed-off-by: Christoph Lameter 
Signed-off-by: Pekka Enberg

mm: Remove support for kmem_cache_name()

2011-01-23T19:00:05+00:00

The last user was ext4 and Eric Sandeen removed the call in a recent patch. See
the following URL for the discussion:

http://marc.info/?l=linux-ext4&m=129546975702198&w=2

Signed-off-by: Christoph Lameter 
Signed-off-by: Pekka Enberg

kernel: kmem_ptr_validate considered harmful

2011-01-07T06:50:16+00:00

This is a nasty and error prone API. It is no longer used, remove it.

Signed-off-by: Nick Piggin

slab: fix caller tracking on !CONFIG_DEBUG_SLAB && CONFIG_TRACING

2010-07-04T16:48:33+00:00

In slab, all __xxx_track_caller is defined on CONFIG_DEBUG_SLAB || CONFIG_TRACING,
thus caller tracking function should be worked for CONFIG_TRACING. But if
CONFIG_DEBUG_SLAB is not set, include/linux/slab.h will define xxx_track_caller to
__xxx() without consideration of CONFIG_TRACING. This will break the caller tracking
behaviour then.

Cc: Christoph Lameter 
Cc: Matt Mackall 
Cc: Vegard Nossum 
Cc: Dmitry Monakhov 
Cc: Catalin Marinas 
Acked-by: David Rientjes 
Signed-off-by: Xiaotian Feng 
Signed-off-by: Pekka Enberg

slab: Generify kernel pointer validation

2010-04-09T17:09:50+00:00

As suggested by Linus, introduce a kern_ptr_validate() helper that does some
sanity checks to make sure a pointer is a valid kernel pointer.  This is a
preparational step for fixing SLUB kmem_ptr_validate().

Cc: Andrew Morton 
Cc: Christoph Lameter 
Cc: David Rientjes 
Cc: Ingo Molnar 
Cc: Matt Mackall 
Cc: Nick Piggin 
Signed-off-by: Pekka Enberg 
Signed-off-by: Linus Torvalds

failslab: add ability to filter slab caches

2010-02-26T17:19:39+00:00

This patch allow to inject faults only for specific slabs.
In order to preserve default behavior cache filter is off by
default (all caches are faulty).

One may define specific set of slabs like this:
# mark skbuff_head_cache as faulty
echo 1 > /sys/kernel/slab/skbuff_head_cache/failslab
# Turn on cache filter (off by default)
echo 1 > /sys/kernel/debug/failslab/cache-filter
# Turn on fault injection
echo 1 > /sys/kernel/debug/failslab/times
echo 1 > /sys/kernel/debug/failslab/probability

Acked-by: David Rientjes 
Acked-by: Akinobu Mita 
Acked-by: Christoph Lameter 
Signed-off-by: Dmitry Monakhov 
Signed-off-by: Pekka Enberg

Merge commit 'linus/master' into HEAD

2009-06-15T13:50:49+00:00

Conflicts:
	MAINTAINERS

Signed-off-by: Vegard Nossum

kmemcheck: add mm functions

2009-06-15T10:40:03+00:00

With kmemcheck enabled, the slab allocator needs to do this:

1. Tell kmemcheck to allocate the shadow memory which stores the status of
   each byte in the allocation proper, e.g. whether it is initialized or
   uninitialized.
2. Tell kmemcheck which parts of memory that should be marked uninitialized.
   There are actually a few more states, such as "not yet allocated" and
   "recently freed".

If a slab cache is set up using the SLAB_NOTRACK flag, it will never return
memory that can take page faults because of kmemcheck.

If a slab cache is NOT set up using the SLAB_NOTRACK flag, callers can still
request memory with the __GFP_NOTRACK flag. This does not prevent the page
faults from occuring, however, but marks the object in question as being
initialized so that no warnings will ever be produced for this object.

In addition to (and in contrast to) __GFP_NOTRACK, the
__GFP_NOTRACK_FALSE_POSITIVE flag indicates that the allocation should
not be tracked _because_ it would produce a false positive. Their values
are identical, but need not be so in the future (for example, we could now
enable/disable false positives with a config option).

Parts of this patch were contributed by Pekka Enberg but merged for
atomicity.

Signed-off-by: Vegard Nossum 
Signed-off-by: Pekka Enberg 
Signed-off-by: Ingo Molnar 

[rebased for mainline inclusion]
Signed-off-by: Vegard Nossum

slab,slub: don't enable interrupts during early boot

2009-06-12T15:53:33+00:00

As explained by Benjamin Herrenschmidt:

  Oh and btw, your patch alone doesn't fix powerpc, because it's missing
  a whole bunch of GFP_KERNEL's in the arch code... You would have to
  grep the entire kernel for things that check slab_is_available() and
  even then you'll be missing some.

  For example, slab_is_available() didn't always exist, and so in the
  early days on powerpc, we used a mem_init_done global that is set form
  mem_init() (not perfect but works in practice). And we still have code
  using that to do the test.

Therefore, mask out __GFP_WAIT, __GFP_IO, and __GFP_FS in the slab allocators
in early boot code to avoid enabling interrupts.

Signed-off-by: Pekka Enberg