From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Kees Cook <keescook@chromium.org>
Subject: Re: [PATCH] usb: iowarrior: replace kmalloc with kmalloc_array
Date: Thu, 23 Aug 2018 12:42:27 -0500 [thread overview]
Message-ID: <34b8a5c3-d71a-3aba-c2ae-2b0a2798361c@embeddedor.com> (raw)
In-Reply-To: <20180823173125.GA24762@embeddedor.com>
Hi,
Please, drop this.
I'll align GFP_KERNEL and send v2.
Thanks
--
Gustavo
On 8/23/18 12:31 PM, Gustavo A. R. Silva wrote:
> A common flaw in the kernel is integer overflow during memory allocation
> size calculations. In an effort to reduce the frequency of these bugs,
> kmalloc_array was implemented, which allocates memory for an array,
> while at the same time detects integer overflow.
>
> This patch replaces cases of:
>
> kmalloc(a * b, gfp)
>
> with:
> kmalloc_array(a * b, gfp)
>
> Signed-off-by: Gustavo A. R. Silva <gustavo@embeddedor.com>
> ---
> drivers/usb/misc/iowarrior.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/usb/misc/iowarrior.c b/drivers/usb/misc/iowarrior.c
> index c2991b8..7a22400 100644
> --- a/drivers/usb/misc/iowarrior.c
> +++ b/drivers/usb/misc/iowarrior.c
> @@ -808,7 +808,7 @@ static int iowarrior_probe(struct usb_interface *interface,
> dev->int_in_endpoint->bInterval);
> /* create an internal buffer for interrupt data from the device */
> dev->read_queue =
> - kmalloc(((dev->report_size + 1) * MAX_INTERRUPT_BUFFER),
> + kmalloc_array(dev->report_size + 1, MAX_INTERRUPT_BUFFER,
> GFP_KERNEL);
> if (!dev->read_queue)
> goto error;
>
next prev parent reply other threads:[~2018-08-23 18:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-23 17:31 Gustavo A. R. Silva
2018-08-23 17:42 ` Gustavo A. R. Silva [this message]
2018-08-23 17:43 ` Kees Cook
2018-08-23 17:51 ` 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=34b8a5c3-d71a-3aba-c2ae-2b0a2798361c@embeddedor.com \
--to=gustavo@embeddedor.com \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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®