Re: [PATCH] SLUB: Use WARN_ON instead of BUG_ON where appropriate

From: Christoph Lameter
Date: Wed Jan 14 2009 - 12:46:11 EST


On Wed, 14 Jan 2009, Pekka J Enberg wrote:

> From: Pekka Enberg <penberg@xxxxxxxxxxxxxx>
>
> It's better to WARN_ON and let the kernel limp along to increase the likelihood
> of an user detecting the error and reporting it to us.

That only works if a error condition can be signaled and be handled
appropriately.

> diff --git a/mm/slub.c b/mm/slub.c
> index 6392ae5..e4404a1 100644
> --- a/mm/slub.c
> +++ b/mm/slub.c
> @@ -1119,7 +1119,8 @@ static struct page *new_slab(struct kmem_cache *s, gfp_t flags, int node)
> void *last;
> void *p;
>
> - BUG_ON(flags & GFP_SLAB_BUG_MASK);
> + if (WARN_ON(flags & GFP_SLAB_BUG_MASK))
> + return NULL;
>
> page = allocate_slab(s,
> flags & (GFP_RECLAIM_MASK | GFP_CONSTRAINT_MASK), node);

Ok. this relies on kmalloc returning NULL to the app.

> @@ -4285,7 +4287,8 @@ static char *create_unique_id(struct kmem_cache *s)
> char *name = kmalloc(ID_STR_LENGTH, GFP_KERNEL);
> char *p = name;
>
> - BUG_ON(!name);
> + if (WARN_ON(!name))
> + return NULL;
>
> *p++ = ':';
> /*
> @@ -4304,7 +4307,8 @@ static char *create_unique_id(struct kmem_cache *s)
> if (p != name + 1)
> *p++ = '-';
> p += sprintf(p, "%07d", s->size);
> - BUG_ON(p > name + ID_STR_LENGTH - 1);
> + if (WARN_ON(p > name + ID_STR_LENGTH - 1))
> + return NULL;
> return name;
> }
>

NULL name? Guess the kfree will just be a nop but what does
kobject_init_and_add do with a NULL name?


> @@ -4333,6 +4337,8 @@ static int sysfs_slab_add(struct kmem_cache *s)
> * for the symlinks.
> */
> name = create_unique_id(s);
> + if (!name)
> + return -EINVAL;
> }
>
> s->kobj.kset = slab_kset;
>

-EINVAL may cause a panic anyways if called from create_kmalloc_cache.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/