Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: james_p_freyensee@linux.intel.com (J Freyensee)
Subject: [PATCH] NVMe: Prevent possible NULL pointer dereference
Date: Thu, 29 May 2014 09:53:12 -0700	[thread overview]
Message-ID: <538765F8.4020002@linux.intel.com> (raw)
In-Reply-To: <1401337912-2691-1-git-send-email-santosh.sy@samsung.com>

On 05/28/2014 09:31 PM, Santosh Y wrote:
> kmalloc() used by the nvme_alloc_iod() to allocate memory for 'iod'
> can fail. So check the return value.
>
> Signed-off-by: Santosh Y <santosh.sy at samsung.com>
>
> diff --git a/drivers/block/nvme-core.c b/drivers/block/nvme-core.c
> index cd8a8bc7..b089459 100644
> --- a/drivers/block/nvme-core.c
> +++ b/drivers/block/nvme-core.c
> @@ -1488,7 +1488,11 @@ struct nvme_iod *nvme_map_user_pages(struct nvme_dev *dev, int write,
>   		goto put_pages;
>   	}
>
> +	err = -ENOMEM;
>   	iod = nvme_alloc_iod(count, length, GFP_KERNEL);
> +	if (!iod)
> +		goto put_pages;
> +
>   	sg = iod->sg;
>   	sg_init_table(sg, count);
>   	for (i = 0; i < count; i++) {
> @@ -1501,7 +1505,6 @@ struct nvme_iod *nvme_map_user_pages(struct nvme_dev *dev, int write,
>   	sg_mark_end(&sg[i - 1]);
>   	iod->nents = count;
>
> -	err = -ENOMEM;

I am not that familiar with this nvme code yet, but should this 
statement be left in?  It looks to me that this 'err = -ENOMEM;' 
assignment is for the case if dma_map_sg() statement below it fails.

>   	nents = dma_map_sg(&dev->pci_dev->dev, sg, count,
>   				write ? DMA_TO_DEVICE : DMA_FROM_DEVICE);
>   	if (!nents)
>

  reply	other threads:[~2014-05-29 16:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-29  4:31 [PATCH] NVMe: Prevent possible NULL pointer dereference Santosh Y
2014-05-29 16:53 ` J Freyensee [this message]
2014-06-02 20:09   ` Keith Busch

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=538765F8.4020002@linux.intel.com \
    --to=james_p_freyensee@linux.intel.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