From: Ming Lei <ming.lei@redhat.com>
To: Yuan Can <yuancan@huawei.com>
Cc: don.brace@microchip.com, jejb@linux.ibm.com,
martin.petersen@oracle.com, storagedev@microchip.com,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH] scsi: hpsa: Fix possible memory leak in hpsa_init_one()
Date: Wed, 23 Nov 2022 16:14:26 +0800 [thread overview]
Message-ID: <Y33WYvis1sHr29zU@T590> (raw)
In-Reply-To: <20221122015751.87284-1-yuancan@huawei.com>
On Tue, Nov 22, 2022 at 01:57:51AM +0000, Yuan Can wrote:
> The hpda_alloc_ctlr_info() allocates h and its field reply_map, however in
> hpsa_init_one(), if alloc_percpu() failed, the hpsa_init_one() jumps to
> clean1 directly, which frees h and leaks the h->reply_map.
> Fix by calling hpda_free_ctlr_info() to release h->replay_map and h
> instead free h directly.
>
> Fixes: 8b834bff1b73 ("scsi: hpsa: fix selection of reply queue")
> Signed-off-by: Yuan Can <yuancan@huawei.com>
> ---
> drivers/scsi/hpsa.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/scsi/hpsa.c b/drivers/scsi/hpsa.c
> index f8e832b1bc46..e5cbc97a5ea4 100644
> --- a/drivers/scsi/hpsa.c
> +++ b/drivers/scsi/hpsa.c
> @@ -8925,7 +8925,7 @@ static int hpsa_init_one(struct pci_dev *pdev, const struct pci_device_id *ent)
> destroy_workqueue(h->monitor_ctlr_wq);
> h->monitor_ctlr_wq = NULL;
> }
> - kfree(h);
> + hpda_free_ctlr_info(h);
Reviewed-by: Ming Lei <ming.lei@redhat.com>
Thanks,
Ming
next prev parent reply other threads:[~2022-11-23 8:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 1:57 [PATCH] scsi: hpsa: Fix possible memory leak in hpsa_init_one() Yuan Can
2022-11-23 8:14 ` Ming Lei [this message]
2022-11-24 3:45 ` Martin K. Petersen
2022-12-01 3:45 ` Martin K. Petersen
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=Y33WYvis1sHr29zU@T590 \
--to=ming.lei@redhat.com \
--cc=don.brace@microchip.com \
--cc=jejb@linux.ibm.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=storagedev@microchip.com \
--cc=yuancan@huawei.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