From: walter harms <wharms@bfs.de>
To: Julia Lawall <julia@diku.dk>
Cc: linux-pcmcia@lists.infradead.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 3/8] drivers/pcmcia: remove unnecessary kzalloc
Date: Sat, 21 Nov 2009 12:44:59 +0000 [thread overview]
Message-ID: <4B07E0CB.6000508@bfs.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0911211250090.23681@ask.diku.dk>
Julia Lawall schrieb:
> From: Julia Lawall <julia@diku.dk>
>
> The result of calling kzalloc is never used or freed.
>
> The semantic match that finds this problem is as follows:
> (http://www.emn.fr/x-info/coccinelle/)
>
> // <smpl>
> @r exists@
> local idexpression x;
> statement S;
> expression E;
> identifier f,f1,l;
> position p1,p2;
> expression *ptr != NULL;
> @@
>
> x@p1 = \(kmalloc\|kzalloc\|kcalloc\)(...);
> ...
> if (x = NULL) S
> <... when != x
> when != if (...) { <+...x...+> }
> (
> x->f1 = E
> |
> (x->f1 = NULL || ...)
> |
> f(...,x->f1,...)
> )
> ...>
> (
> return \(0\|<+...x...+>\|ptr\);
> |
> return@p2 ...;
> )
>
> @script:python@
> p1 << r.p1;
> p2 << r.p2;
> @@
>
> print "* file: %s kmalloc %s return %s" % (p1[0].file,p1[0].line,p2[0].line)
> // </smpl>
>
> Signed-off-by: Julia Lawall <julia@diku.dk>
> ---
> drivers/pcmcia/sa1111_generic.c | 4 ----
> 1 files changed, 0 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/pcmcia/sa1111_generic.c b/drivers/pcmcia/sa1111_generic.c
> index deb5036..de6bc33 100644
> --- a/drivers/pcmcia/sa1111_generic.c
> +++ b/drivers/pcmcia/sa1111_generic.c
> @@ -127,10 +127,6 @@ int sa1111_pcmcia_add(struct sa1111_dev *dev, struct pcmcia_low_level *ops,
> ops->socket_state = sa1111_pcmcia_socket_state;
> ops->socket_suspend = sa1111_pcmcia_socket_suspend;
>
> - s = kzalloc(sizeof(*s) * ops->nr, GFP_KERNEL);
> - if (!s)
> - return -ENODEV;
> -
> for (i = 0; i < ops->nr; i++) {
> s = kzalloc(sizeof(*s), GFP_KERNEL);
> if (!s)
mmmh, perhaps the original idea was to have an array
and then he moved to a linked list ?
I thing the array idea is better (1. it fails on low mem propperly, 2. no need free()
3. less zmalloc stuff) but requieres that pcmcia_remove()
will release that array propperly
the bug is strange,
just my 2 cents,
re,
wh
WARNING: multiple messages have this Message-ID (diff)
From: walter harms <wharms@bfs.de>
To: Julia Lawall <julia@diku.dk>
Cc: linux-pcmcia@lists.infradead.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 3/8] drivers/pcmcia: remove unnecessary kzalloc
Date: Sat, 21 Nov 2009 13:44:59 +0100 [thread overview]
Message-ID: <4B07E0CB.6000508@bfs.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0911211250090.23681@ask.diku.dk>
Julia Lawall schrieb:
> From: Julia Lawall <julia@diku.dk>
>
> The result of calling kzalloc is never used or freed.
>
> The semantic match that finds this problem is as follows:
> (http://www.emn.fr/x-info/coccinelle/)
>
> // <smpl>
> @r exists@
> local idexpression x;
> statement S;
> expression E;
> identifier f,f1,l;
> position p1,p2;
> expression *ptr != NULL;
> @@
>
> x@p1 = \(kmalloc\|kzalloc\|kcalloc\)(...);
> ...
> if (x == NULL) S
> <... when != x
> when != if (...) { <+...x...+> }
> (
> x->f1 = E
> |
> (x->f1 == NULL || ...)
> |
> f(...,x->f1,...)
> )
> ...>
> (
> return \(0\|<+...x...+>\|ptr\);
> |
> return@p2 ...;
> )
>
> @script:python@
> p1 << r.p1;
> p2 << r.p2;
> @@
>
> print "* file: %s kmalloc %s return %s" % (p1[0].file,p1[0].line,p2[0].line)
> // </smpl>
>
> Signed-off-by: Julia Lawall <julia@diku.dk>
> ---
> drivers/pcmcia/sa1111_generic.c | 4 ----
> 1 files changed, 0 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/pcmcia/sa1111_generic.c b/drivers/pcmcia/sa1111_generic.c
> index deb5036..de6bc33 100644
> --- a/drivers/pcmcia/sa1111_generic.c
> +++ b/drivers/pcmcia/sa1111_generic.c
> @@ -127,10 +127,6 @@ int sa1111_pcmcia_add(struct sa1111_dev *dev, struct pcmcia_low_level *ops,
> ops->socket_state = sa1111_pcmcia_socket_state;
> ops->socket_suspend = sa1111_pcmcia_socket_suspend;
>
> - s = kzalloc(sizeof(*s) * ops->nr, GFP_KERNEL);
> - if (!s)
> - return -ENODEV;
> -
> for (i = 0; i < ops->nr; i++) {
> s = kzalloc(sizeof(*s), GFP_KERNEL);
> if (!s)
mmmh, perhaps the original idea was to have an array
and then he moved to a linked list ?
I thing the array idea is better (1. it fails on low mem propperly, 2. no need free()
3. less zmalloc stuff) but requieres that pcmcia_remove()
will release that array propperly
the bug is strange,
just my 2 cents,
re,
wh
next prev parent reply other threads:[~2009-11-21 12:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-21 11:50 [PATCH 3/8] drivers/pcmcia: remove unnecessary kzalloc Julia Lawall
2009-11-21 11:50 ` Julia Lawall
2009-11-21 12:44 ` walter harms [this message]
2009-11-21 12:44 ` walter harms
2009-11-21 15:12 ` Julia Lawall
2009-11-21 15:12 ` Julia Lawall
2009-11-21 15:16 ` Russell King - ARM Linux
2009-11-21 15:23 ` Julia Lawall
2009-11-21 15:23 ` Julia Lawall
2009-11-21 15:25 ` Dominik Brodowski
2009-11-21 15:25 ` Dominik Brodowski
2009-11-21 15:51 ` Russell King - ARM Linux
2009-11-21 15:51 ` Russell King - ARM Linux
2009-11-21 15:56 ` Julia Lawall
2009-11-21 15:56 ` Julia Lawall
2009-11-21 16:06 ` Dominik Brodowski
2009-11-21 16:06 ` Dominik Brodowski
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=4B07E0CB.6000508@bfs.de \
--to=wharms@bfs.de \
--cc=julia@diku.dk \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pcmcia@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.