From: Felipe Balbi <balbi@ti.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Colin King <colin.king@canonical.com>,
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, 3 Jun 2015 10:38:00 -0500 [thread overview]
Message-ID: <20150603153800.GA31204@saruman.tx.rr.com> (raw)
In-Reply-To: <2210713.bNgAhNmNaU@avalon>
[-- Attachment #1: Type: text/plain, Size: 1083 bytes --]
Hi,
On Wed, Jun 03, 2015 at 03:43:23AM +0300, Laurent Pinchart 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.
once -rc1 is tagged, yes. My tree is already closed for v4.2.
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-06-03 15:40 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
2015-06-03 15:38 ` Felipe Balbi [this message]
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=20150603153800.GA31204@saruman.tx.rr.com \
--to=balbi@ti.com \
--cc=Valentin.Rothberg@lip6.fr \
--cc=colin.king@canonical.com \
--cc=gregkh@linuxfoundation.org \
--cc=laurent.pinchart@ideasonboard.com \
--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