From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Colin King <colin.king@canonical.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Felipe Balbi <balbi@ti.com>, Sudeep Holla <sudeep.holla@arm.com>,
Valentin Rothberg <Valentin.Rothberg@lip6.fr>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][V3] usb: isp1760: check for null return from kzalloc
Date: Wed, 03 Jun 2015 03:43:23 +0300 [thread overview]
Message-ID: <2210713.bNgAhNmNaU@avalon> (raw)
In-Reply-To: <1433268313-23423-1-git-send-email-colin.king@canonical.com>
Hi Colin,
Thank you for the patch.
On Tuesday 02 June 2015 19:05:13 Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> isp1760_ep_alloc_request allocates a structure with kzalloc without checking
> for NULL and then returns a pointer to one of the structure fields. As the
> field happens to be the first in the structure the caller can properly
> check for NULL, but this is risky if the structure layout is changed later.
> Add an explicit NULL check for the kzalloc return value
>
> Detected with smatch static analysis:
>
> drivers/usb/isp1760/isp1760-udc.c:816 isp1760_ep_alloc_request()
> error: potential null dereference 'req'. (kzalloc returns null)
>
> [ thanks to Laurent Pinchart for improved commit message ]
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Felipe, I expect you to pick this up, please let me know if there's any issue.
> ---
> drivers/usb/isp1760/isp1760-udc.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/usb/isp1760/isp1760-udc.c
> b/drivers/usb/isp1760/isp1760-udc.c index 3fc4fe7..18ebf5b 100644
> --- a/drivers/usb/isp1760/isp1760-udc.c
> +++ b/drivers/usb/isp1760/isp1760-udc.c
> @@ -812,6 +812,8 @@ static struct usb_request
> *isp1760_ep_alloc_request(struct usb_ep *ep, struct isp1760_request *req;
>
> req = kzalloc(sizeof(*req), gfp_flags);
> + if (!req)
> + return NULL;
>
> return &req->req;
> }
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2015-06-03 0:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 18:05 [PATCH][V3] usb: isp1760: check for null return from kzalloc Colin King
2015-06-03 0:43 ` Laurent Pinchart [this message]
2015-06-03 15:38 ` Felipe Balbi
2015-06-08 21:22 ` Greg Kroah-Hartman
2015-06-09 3:11 ` Felipe Balbi
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=2210713.bNgAhNmNaU@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=Valentin.Rothberg@lip6.fr \
--cc=balbi@ti.com \
--cc=colin.king@canonical.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sudeep.holla@arm.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