mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Garry <john.garry@huawei.com>
To: Bean Huo <huobean@gmail.com>, <alim.akhtar@samsung.com>,
	<avri.altman@wdc.com>, <jejb@linux.ibm.com>,
	<martin.petersen@oracle.com>, <ebiggers@google.com>,
	<satyat@google.com>, <shipujin.t@gmail.com>
Cc: <linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	Bean Huo <beanhuo@micron.com>
Subject: Re: [PATCH v2 1/2] scsi: hisi_sas: Remove unnecessary devm_kfree
Date: Tue, 12 Jan 2021 09:03:17 +0000	[thread overview]
Message-ID: <b34eac20-e194-783b-f29e-83eec8bb127c@huawei.com> (raw)
In-Reply-To: <20210111231058.14559-2-huobean@gmail.com>

On 11/01/2021 23:10, Bean Huo wrote:
> From: Bean Huo <beanhuo@micron.com>
> 
> The memory allocated with devm_kzalloc() is freed automatically
> no need to explicitly call devm_kfree.
> 

This change is not right - we use devm_kfree() to manually release the 
devm-allocated debugfs memories upon memory allocation failure for 
driver debugfs feature during probe. The reason is that we allow the 
driver probe can still continue (for this failure).

Thanks,
John

> Signed-off-by: Bean Huo <beanhuo@micron.com>
> ---
>   drivers/scsi/hisi_sas/hisi_sas_v3_hw.c | 28 +-------------------------
>   1 file changed, 1 insertion(+), 27 deletions(-)
> 
> diff --git a/drivers/scsi/hisi_sas/hisi_sas_v3_hw.c b/drivers/scsi/hisi_sas/hisi_sas_v3_hw.c
> index 91a7286e8102..5600411a0820 100644
> --- a/drivers/scsi/hisi_sas/hisi_sas_v3_hw.c
> +++ b/drivers/scsi/hisi_sas/hisi_sas_v3_hw.c
> @@ -4172,30 +4172,6 @@ static void debugfs_work_handler_v3_hw(struct work_struct *work)
>   	hisi_hba->debugfs_dump_index++;
>   }
>   
> -static void debugfs_release_v3_hw(struct hisi_hba *hisi_hba, int dump_index)
> -{
> -	struct device *dev = hisi_hba->dev;
> -	int i;
> -
> -	devm_kfree(dev, hisi_hba->debugfs_iost_cache[dump_index].cache);
> -	devm_kfree(dev, hisi_hba->debugfs_itct_cache[dump_index].cache);
> -	devm_kfree(dev, hisi_hba->debugfs_iost[dump_index].iost);
> -	devm_kfree(dev, hisi_hba->debugfs_itct[dump_index].itct);
> -
> -	for (i = 0; i < hisi_hba->queue_count; i++)
> -		devm_kfree(dev, hisi_hba->debugfs_dq[dump_index][i].hdr);
> -
> -	for (i = 0; i < hisi_hba->queue_count; i++)
> -		devm_kfree(dev,
> -			   hisi_hba->debugfs_cq[dump_index][i].complete_hdr);
> -
> -	for (i = 0; i < DEBUGFS_REGS_NUM; i++)
> -		devm_kfree(dev, hisi_hba->debugfs_regs[dump_index][i].data);
> -
> -	for (i = 0; i < hisi_hba->n_phy; i++)
> -		devm_kfree(dev, hisi_hba->debugfs_port_reg[dump_index][i].data);
> -}
> -
>   static const struct hisi_sas_debugfs_reg *debugfs_reg_array_v3_hw[DEBUGFS_REGS_NUM] = {
>   	[DEBUGFS_GLOBAL] = &debugfs_global_reg,
>   	[DEBUGFS_AXI] = &debugfs_axi_reg,
> @@ -4206,7 +4182,7 @@ static int debugfs_alloc_v3_hw(struct hisi_hba *hisi_hba, int dump_index)
>   {
>   	const struct hisi_sas_hw *hw = hisi_hba->hw;
>   	struct device *dev = hisi_hba->dev;
> -	int p, c, d, r, i;
> +	int p, c, d, r;
>   	size_t sz;
>   
>   	for (r = 0; r < DEBUGFS_REGS_NUM; r++) {
> @@ -4286,8 +4262,6 @@ static int debugfs_alloc_v3_hw(struct hisi_hba *hisi_hba, int dump_index)
>   
>   	return 0;
>   fail:
> -	for (i = 0; i < hisi_sas_debugfs_dump_count; i++)
> -		debugfs_release_v3_hw(hisi_hba, i);
>   	return -ENOMEM;
>   }
>   
> 


  reply	other threads:[~2021-01-12  9:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-11 23:10 [PATCH v2 0/2] " Bean Huo
2021-01-11 23:10 ` [PATCH v2 1/2] scsi: hisi_sas: " Bean Huo
2021-01-12  9:03   ` John Garry [this message]
2021-01-12  9:13     ` Bean Huo
2021-01-11 23:10 ` [PATCH v2 2/2] scsi: ufs: " Bean Huo

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=b34eac20-e194-783b-f29e-83eec8bb127c@huawei.com \
    --to=john.garry@huawei.com \
    --cc=alim.akhtar@samsung.com \
    --cc=avri.altman@wdc.com \
    --cc=beanhuo@micron.com \
    --cc=ebiggers@google.com \
    --cc=huobean@gmail.com \
    --cc=jejb@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=satyat@google.com \
    --cc=shipujin.t@gmail.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

all inboxes | Powered by JetHome®