From: "Pekka Enberg" <penberg@cs.helsinki.fi>
To: "Andrew Morton" <akpm@linux-foundation.org>
Cc: "Manfred Spraul" <manfred@colorfullife.com>,
krh@redhat.com, stefanr@s5r6.in-berlin.de, dcm@acm.org,
Nadia.Derbey@bull.net, linux1394-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, paulmck@us.ibm.com
Subject: Re: [PATCH] lib/idr.c: Zero memory properly in idr_remove_all
Date: Wed, 14 Jan 2009 09:19:01 +0200 [thread overview]
Message-ID: <84144f020901132319g50dc9e50o283b0d263f287eea@mail.gmail.com> (raw)
In-Reply-To: <20090113144802.39dc4c23.akpm@linux-foundation.org>
On Wed, Jan 14, 2009 at 12:48 AM, Andrew Morton
<akpm@linux-foundation.org> wrote:
>> If the idr code passes uninitialized objects to kmem_cache_free(), then
>> the next kmem_cache_alloc will return a bad object.
>>
>
> None of this got us much closer to fixing the bug ;)
>
> What do we think of just removing the constructor and using
> kmem_cache_zalloc()?
Why do I get the feeling that we have merged a similar patch before?
Acked-by: Pekka Enberg <penberg@cs.helsinki.fi>
>
> --- a/lib/idr.c~a
> +++ a/lib/idr.c
> @@ -121,7 +121,7 @@ int idr_pre_get(struct idr *idp, gfp_t g
> {
> while (idp->id_free_cnt < IDR_FREE_MAX) {
> struct idr_layer *new;
> - new = kmem_cache_alloc(idr_layer_cache, gfp_mask);
> + new = kmem_cache_zalloc(idr_layer_cache, gfp_mask);
> if (new == NULL)
> return (0);
> move_to_free_list(idp, new);
> @@ -623,16 +623,10 @@ void *idr_replace(struct idr *idp, void
> }
> EXPORT_SYMBOL(idr_replace);
>
> -static void idr_cache_ctor(void *idr_layer)
> -{
> - memset(idr_layer, 0, sizeof(struct idr_layer));
> -}
> -
> void __init idr_init_cache(void)
> {
> idr_layer_cache = kmem_cache_create("idr_layer_cache",
> - sizeof(struct idr_layer), 0, SLAB_PANIC,
> - idr_cache_ctor);
> + sizeof(struct idr_layer), 0, SLAB_PANIC, NULL);
> }
>
> /**
> _
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2009-01-14 7:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-10 7:04 David Moore
2009-01-10 9:03 ` Stefan Richter
2009-01-10 9:15 ` Andrew Morton
2009-01-10 10:05 ` Stefan Richter
2009-01-12 15:20 ` Kristian Høgsberg
2009-01-12 19:53 ` Manfred Spraul
2009-01-12 20:38 ` Kristian Høgsberg
2009-01-12 20:50 ` Manfred Spraul
2009-01-13 22:48 ` Andrew Morton
2009-01-14 2:51 ` David Moore
2009-01-14 7:19 ` Pekka Enberg [this message]
2009-01-14 8:17 ` Andrew Morton
2009-01-14 8:59 ` Stefan Richter
2009-01-14 9:22 ` Andrew Morton
2009-01-14 9:48 ` Stefan Richter
2009-01-14 9:52 ` Stefan Richter
2009-01-14 9:02 ` Pekka Enberg
2009-01-14 14:23 ` Kristian Høgsberg
2009-01-14 16:21 ` Stefan Richter
2009-01-14 16:33 ` Kristian Høgsberg
2009-01-14 18:05 ` Stefan Richter
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=84144f020901132319g50dc9e50o283b0d263f287eea@mail.gmail.com \
--to=penberg@cs.helsinki.fi \
--cc=Nadia.Derbey@bull.net \
--cc=akpm@linux-foundation.org \
--cc=dcm@acm.org \
--cc=krh@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=manfred@colorfullife.com \
--cc=paulmck@us.ibm.com \
--cc=stefanr@s5r6.in-berlin.de \
/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
all inboxes | Powered by JetHome®