public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: Lion Vollnhals <lion.vollnhals@web.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] use kzalloc instead of malloc+memset
Date: Tue, 13 Sep 2005 00:58:31 +0200	[thread overview]
Message-ID: <43260817.7070907@gmail.com> (raw)
In-Reply-To: <200509130010.38483.lion.vollnhals@web.de>

Lion Vollnhals napsal(a):

>This patch against 2.6.13-mm3 replaces malloc and memset with kzalloc in drivers/base/class.c .
>Furthermore this patch fixes actually two bugs:
>  The memset arguments were occasionally swaped and therefore wrong.
>
>Usage of kzalloc makes this code shorter and more bugfree.
>
>Please apply.
>
>Signed-off-by: Lion Vollnhals <webmaster@schiggl.de>
>
>--- 2.6.13-mm3/drivers/base/class.c	2005-09-12 23:42:47.000000000 +0200
>+++ 2.6.13-mm3-changed/drivers/base/class.c	2005-09-12 23:54:56.000000000 +0200
>@@ -190,12 +190,11 @@ struct class *class_create(struct module
> 	struct class *cls;
> 	int retval;
> 
>-	cls = kmalloc(sizeof(struct class), GFP_KERNEL);
>+	cls = kzalloc(sizeof(struct class), GFP_KERNEL);
>  
>
maybe, the better way is to write `*cls' instead of `struct class', 
better for further changes

> 	if (!cls) {
> 		retval = -ENOMEM;
> 		goto error;
> 	}
>-	memset(cls, 0x00, sizeof(struct class));
> 
> 	cls->name = name;
> 	cls->owner = owner;
>  
>
[snip]

>@@ -611,12 +610,11 @@ struct class_device *class_device_create
> 	if (cls == NULL || IS_ERR(cls))
> 		goto error;
> 
>-	class_dev = kmalloc(sizeof(struct class_device), GFP_KERNEL);
>+	class_dev = kzalloc(sizeof(struct class_device), GFP_KERNEL);
>  
>
`*class_dev' instead of `struct class_device'

> 	if (!class_dev) {
> 		retval = -ENOMEM;
> 		goto error;
> 	}
>-	memset(class_dev, 0x00, sizeof(struct class_device));
> 
> 	class_dev->devt = devt;
> 	class_dev->dev = device;
>  
>
thanks,

-- 
Jiri Slaby         www.fi.muni.cz/~xslaby
~\-/~      jirislaby@gmail.com      ~\-/~
241B347EC88228DE51EE A49C4A73A25004CB2A10


  parent reply	other threads:[~2005-09-12 22:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-12 22:10 [PATCH] use kzalloc instead of malloc+memset Lion Vollnhals
2005-09-12 22:47 ` Lion Vollnhals
2005-09-13  5:41   ` Denis Vlasenko
2005-09-13 11:27     ` Jiri Slaby
2005-09-12 22:58 ` Jiri Slaby [this message]
2005-09-13  4:43   ` Pekka Enberg
2005-09-13  5:33     ` Dmitry Torokhov
2005-09-13  6:42       ` Andrew Morton
2005-09-13  7:02         ` Pekka J Enberg
2005-09-13  7:42           ` Nikita Danilov
2005-09-13 16:31             ` Pekka Enberg
2005-09-14  5:02             ` Denis Vlasenko
2005-09-14  9:58               ` Nikita Danilov
2005-09-13 23:28         ` Paul Jackson
2005-09-14  9:33           ` Bernd Petrovitsch

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=43260817.7070907@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lion.vollnhals@web.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