Re: [RFC 2/4] CONFIG_STABLE: Switch off kmalloc(0) tests in slab allocators

2007-05-31 Thread Andi Kleen
Zach Brown <[EMAIL PROTECTED]> writes: > > +#ifndef CONFIG_STABLE > > /* > > * We should return 0 if size == 0 (which would result in the > > * kmalloc caller to get NULL) but we use the smallest object > > @@ -81,6 +82,7 @@ static inline int kmalloc_index(size_t s > > * we can

Re: [RFC 2/4] CONFIG_STABLE: Switch off kmalloc(0) tests in slab allocators

2007-05-31 Thread Zach Brown
> +#ifndef CONFIG_STABLE > /* >* We should return 0 if size == 0 (which would result in the >* kmalloc caller to get NULL) but we use the smallest object > @@ -81,6 +82,7 @@ static inline int kmalloc_index(size_t s >* we can discover locations where we do 0 sized alloc

[RFC 2/4] CONFIG_STABLE: Switch off kmalloc(0) tests in slab allocators

2007-05-30 Thread clameter
We do not want kmalloc(0) to trigger stackdumps if this is a stable kernel. kmalloc(0) is currently harmless. Signed-off-by: Christoph Lameter <[EMAIL PROTECTED]> --- include/linux/slub_def.h |2 ++ mm/slab.c|2 ++ 2 files changed, 4 insertions(+) Index: slub/include/lin