From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH 1/1] NVMe : Corrected memory freeing.
Date: Wed, 17 Jun 2015 16:24:56 +0000 (UTC) [thread overview]
Message-ID: <alpine.LNX.2.00.1506171622030.15930@localhost.lm.intel.com> (raw)
In-Reply-To: <1434557459-4732-1-git-send-email-dheepthi.s@gracelabs.com>
On Wed, 17 Jun 2015, Dheepthi K wrote:
> Memory freeing order has been corrected incase of
> allocation failure.
This isn't necessary. The nvme_dev is zero'ed on allocation, and
kfree(NULL or (void *)0) is okay to do.
> Signed-off-by: Dheepthi K <dheepthi.s at gracelabs.com>
> ---
> drivers/block/nvme-core.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/block/nvme-core.c b/drivers/block/nvme-core.c
> index 683dff2..9bac53b 100644
> --- a/drivers/block/nvme-core.c
> +++ b/drivers/block/nvme-core.c
> @@ -2947,11 +2947,11 @@ static int nvme_probe(struct pci_dev *pdev, const struct pci_device_id *id)
> dev->entry = kzalloc_node(num_possible_cpus() * sizeof(*dev->entry),
> GFP_KERNEL, node);
> if (!dev->entry)
> - goto free;
> + goto free_dev;
> dev->queues = kzalloc_node((num_possible_cpus() + 1) * sizeof(void *),
> GFP_KERNEL, node);
> if (!dev->queues)
> - goto free;
> + goto free_entry;
>
> INIT_LIST_HEAD(&dev->namespaces);
> dev->reset_workfn = nvme_reset_failed_dev;
> @@ -2987,9 +2987,10 @@ static int nvme_probe(struct pci_dev *pdev, const struct pci_device_id *id)
> nvme_release_instance(dev);
> put_pci:
> pci_dev_put(dev->pci_dev);
> - free:
> kfree(dev->queues);
> + free_entry:
> kfree(dev->entry);
> + free_dev:
> kfree(dev);
> return result;
> }
prev parent reply other threads:[~2015-06-17 16:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-17 16:10 [PATCH 1/1] NVMe : Corrected memory freeing Dheepthi K
2015-06-17 16:24 ` Matthew Wilcox
2015-06-17 16:24 ` Keith Busch [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=alpine.LNX.2.00.1506171622030.15930@localhost.lm.intel.com \
--to=keith.busch@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