From: Lars Ellenberg <lars.ellenberg@linbit.com>
To: Ilia Mirkin <imirkin@alum.mit.edu>
Cc: drbd-dev@lists.linbit.com, linux-kernel@vger.kernel.org
Subject: Re: [Drbd-dev] [PATCH] lru_cache: Use correct type in sizeof for allocation
Date: Mon, 21 Feb 2011 09:44:19 +0100 [thread overview]
Message-ID: <20110221084419.GC20194@barkeeper1-xen.linbit> (raw)
In-Reply-To: <1298241914-1400-1-git-send-email-imirkin@alum.mit.edu>
On Sun, Feb 20, 2011 at 05:45:14PM -0500, Ilia Mirkin wrote:
> This has no actual effect, since sizeof(struct hlist_head) ==
> sizeof(struct hlist_head *), but it's still the wrong type to use.
>
> The semantic match that finds this problem:
> // <smpl>
> @@
> type T;
> identifier x;
> @@
> T *x;
> ...
> * x = kzalloc(... * sizeof(T*) * ..., ...);
> // </smpl>
>
> Signed-off-by: Ilia Mirkin <imirkin@alum.mit.edu>
Acked-by: Lars Ellenberg <lars@linbit.com>
>
> ---
> lib/lru_cache.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> Note that in lc_reset, there is the line
>
> memset(lc->lc_slot, 0, sizeof(struct hlist_head) * lc->nr_elements);
>
> So this seems correct. But otherwise untested.
>
> diff --git a/lib/lru_cache.c b/lib/lru_cache.c
> index 270de9d..b312c8f 100644
> --- a/lib/lru_cache.c
> +++ b/lib/lru_cache.c
> @@ -84,7 +84,7 @@ struct lru_cache *lc_create(const char *name, struct kmem_cache *cache,
> if (e_count > LC_MAX_ACTIVE)
> return NULL;
>
> - slot = kzalloc(e_count * sizeof(struct hlist_head*), GFP_KERNEL);
> + slot = kzalloc(e_count * sizeof(struct hlist_head), GFP_KERNEL);
Luckily sizeof(struct hlist_head*) == sizeof(struct hlist_head),
so this went unnoticed, as it did not have any effect.
Thanks for having this spotted by semantic matching.
Lars
> if (!slot)
> goto out_fail;
> element = kzalloc(e_count * sizeof(struct lc_element *), GFP_KERNEL);
> --
> 1.7.3.4
next prev parent reply other threads:[~2011-02-21 8:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-20 22:45 Ilia Mirkin
2011-02-21 8:44 ` Lars Ellenberg [this message]
2011-04-07 21:19 ` Andrew Morton
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=20110221084419.GC20194@barkeeper1-xen.linbit \
--to=lars.ellenberg@linbit.com \
--cc=drbd-dev@lists.linbit.com \
--cc=imirkin@alum.mit.edu \
--cc=linux-kernel@vger.kernel.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 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®