From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: "Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kvm: Use struct_size() in kmalloc()
Date: Tue, 29 Jan 2019 11:20:29 -0600 [thread overview]
Message-ID: <4c4093b5-814d-3337-bc26-d6a491a7944e@embeddedor.com> (raw)
In-Reply-To: <20190104162910.GA25118@embeddedor>
Hi all,
Friendly ping:
Who can take this?
Thanks
--
Gustavo
On 1/4/19 10:29 AM, Gustavo A. R. Silva wrote:
> One of the more common cases of allocation size calculations is finding
> the size of a structure that has a zero-sized array at the end, along
> with memory for some number of elements for that array. For example:
>
> struct foo {
> int stuff;
> void *entry[];
> };
>
> instance = kmalloc(sizeof(struct foo) + sizeof(void *) * count, GFP_KERNEL);
>
> Instead of leaving these open-coded and prone to type mistakes, we can
> now use the new struct_size() helper:
>
> instance = kmalloc(struct_size(instance, entry, count), GFP_KERNEL);
>
> This code was detected with the help of Coccinelle.
>
> Signed-off-by: Gustavo A. R. Silva <gustavo@embeddedor.com>
> ---
> virt/kvm/kvm_main.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c
> index 666d0155662d..635b12fdbab8 100644
> --- a/virt/kvm/kvm_main.c
> +++ b/virt/kvm/kvm_main.c
> @@ -3709,8 +3709,8 @@ int kvm_io_bus_register_dev(struct kvm *kvm, enum kvm_bus bus_idx, gpa_t addr,
> if (bus->dev_count - bus->ioeventfd_count > NR_IOBUS_DEVS - 1)
> return -ENOSPC;
>
> - new_bus = kmalloc(sizeof(*bus) + ((bus->dev_count + 1) *
> - sizeof(struct kvm_io_range)), GFP_KERNEL);
> + new_bus = kmalloc(struct_size(bus, range, bus->dev_count + 1),
> + GFP_KERNEL);
> if (!new_bus)
> return -ENOMEM;
>
> @@ -3755,8 +3755,8 @@ void kvm_io_bus_unregister_dev(struct kvm *kvm, enum kvm_bus bus_idx,
> if (i == bus->dev_count)
> return;
>
> - new_bus = kmalloc(sizeof(*bus) + ((bus->dev_count - 1) *
> - sizeof(struct kvm_io_range)), GFP_KERNEL);
> + new_bus = kmalloc(struct_size(bus, range, bus->dev_count - 1),
> + GFP_KERNEL);
> if (!new_bus) {
> pr_err("kvm: failed to shrink bus, removing it completely\n");
> goto broken;
>
next prev parent reply other threads:[~2019-01-29 17:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-04 16:29 Gustavo A. R. Silva
2019-01-11 13:53 ` Radim Krčmář
2019-01-29 17:20 ` Gustavo A. R. Silva [this message]
2019-01-30 16:08 ` Paolo Bonzini
2019-01-30 16:12 ` Gustavo A. R. Silva
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=4c4093b5-814d-3337-bc26-d6a491a7944e@embeddedor.com \
--to=gustavo@embeddedor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
/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®