public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.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>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][V2] usb: isp1760: fix null dereference if kzalloc returns null
Date: Tue, 02 Jun 2015 20:57:40 +0300	[thread overview]
Message-ID: <556DEE94.3030203@cogentembedded.com> (raw)
In-Reply-To: <2412438.ObMLH8QmsQ@avalon>

Hello.

On 06/02/2015 06:41 PM, Laurent Pinchart wrote:

>>> From: Colin Ian King <colin.king@canonical.com>

>>> If kzalloc returns null then isp1760_ep_alloc_request performs
>>> a null pointer dereference on req. Check for null to avoid this.

>> I told you there's no dereference and yet you're repeating it again. :-(

> How about

> "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."

    Fine with me! Thanks, Laurent. :-)

>>> a null pointer dereference on req. Check for null to avoid this.

>>> Detected with smatch static analysis:

>>> drivers/usb/isp1760/isp1760-udc.c:816 isp1760_ep_alloc_request()

>>>     error: potential null dereference 'req'.  (kzalloc returns null)

>>> Signed-off-by: Colin Ian King <colin.king@canonical.com>

WBR, Sergei


      reply	other threads:[~2015-06-02 17:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-31 22:43 [PATCH][V2] usb: isp1760: fix null dereference if kzalloc returns null Colin King
2015-06-01 13:51 ` Sergei Shtylyov
2015-06-02 15:41   ` Laurent Pinchart
2015-06-02 17:57     ` Sergei Shtylyov [this message]

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=556DEE94.3030203@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=balbi@ti.com \
    --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