public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Balbir Singh <balbir@in.ibm.com>
To: Pekka J Enberg <penberg@cs.Helsinki.FI>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] slab: introduce kmem_cache_zalloc allocator
Date: Mon, 20 Mar 2006 21:35:00 +0530	[thread overview]
Message-ID: <20060320160500.GA25415@in.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0603201506140.19005@sbz-30.cs.Helsinki.FI>

<snip>

>  /**
> + * kmem_cache_alloc - Allocate an object. The memory is set to zero.
> + * @cache: The cache to allocate from.
> + * @flags: See kmalloc().
> + *
> + * Allocate an object from this cache and set the allocated memory to zero.
> + * The flags are only relevant if the cache has no available objects.
> + */
> +void *kmem_cache_zalloc(struct kmem_cache *cache, gfp_t flags)
> +{
> +	void *ret = __cache_alloc(cache, flags, __builtin_return_address(0));
> +	if (ret)
> +		memset(ret, 0, obj_size(cache));
> +	return ret;
> +}
> +EXPORT_SYMBOL(kmem_cache_zalloc);
> +
> +/**
>   * kmem_ptr_validate - check if an untrusted pointer might
>   *	be a slab entry.
>   * @cachep: the cache we're checking against
> diff --git a/mm/slob.c b/mm/slob.c
> index a1f42bd..9bcc7e2 100644
> --- a/mm/slob.c
> +++ b/mm/slob.c
> @@ -294,6 +294,16 @@ void *kmem_cache_alloc(struct kmem_cache
>  }
>  EXPORT_SYMBOL(kmem_cache_alloc);
>  
> +void *kmem_cache_zalloc(struct kmem_cache *c, gfp_t flags)
> +{
> +	void *ret = kmem_cache_alloc(c, flags);
> +	if (ret)
> +		memset(ret, 0, c->size);
> +
> +	return ret;
> +}
> +EXPORT_SYMBOL(kmem_cache_zalloc);
> +
>  void kmem_cache_free(struct kmem_cache *c, void *b)
>  {
>  	if (c->dtor)

Could we please create a more generic variation of this patch -- may be a
function called kmem_cache_alloc_set(). The function would not only
memset the data to 0, but instead to any specified pattern passed as
an argument.

This could be used to poison allocated memory. Passing 0 would make
this equivalent to kmem_cache_zalloc(). Basically, instead of doing

mem = __cache_alloc(...)
memset(mem, 0, size)

I would prefer if we could have

mem = __cache_alloc(...)
memset(mem, X, size)

Balbir

  parent reply	other threads:[~2006-03-20 16:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-20 13:07 [PATCH] slab: introduce kmem_cache_zalloc allocator Pekka J Enberg
2006-03-20 13:51 ` Eric Dumazet
2006-03-20 14:21   ` Pekka J Enberg
2006-03-20 16:05 ` Balbir Singh [this message]
2006-03-20 16:14   ` Pekka Enberg
2006-03-20 16:45     ` Balbir Singh
2006-03-21  7:13       ` Pekka J Enberg
2006-03-21 10:36 ` Andrew Morton
2006-03-21 11:03   ` Pekka J Enberg
2006-03-21 18:35     ` Manfred Spraul
2006-03-21 18:37       ` Pekka Enberg
2006-03-21 11:25 ` Andrew Morton
2006-03-21 11:50   ` Pekka J Enberg
2006-03-21 16:30   ` Pekka Enberg
     [not found] <5Ssjj-314-69@gated-at.bofh.it>
     [not found] ` <5Sv7o-7l5-23@gated-at.bofh.it>
     [not found]   ` <5Svh9-7xW-61@gated-at.bofh.it>
     [not found]     ` <5SvK8-88q-41@gated-at.bofh.it>
2006-03-20 19:07       ` Bodo Eggert
2006-03-21  3:25         ` Balbir Singh
2006-03-21 10:51           ` Bodo Eggert
2006-03-21 11:32             ` Pekka J Enberg

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=20060320160500.GA25415@in.ibm.com \
    --to=balbir@in.ibm.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox