From: Keoseong Park <keosung.park@samsung.com>
To: Bart Van Assche <bvanassche@acm.org>,
Keoseong Park <keosung.park@samsung.com>,
ALIM AKHTAR <alim.akhtar@samsung.com>,
"avri.altman@wdc.com" <avri.altman@wdc.com>,
"jejb@linux.ibm.com" <jejb@linux.ibm.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
Daejun Park <daejun7.park@samsung.com>,
"beanhuo@micron.com" <beanhuo@micron.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: Re: [PATCH] scsi: ufs: ufshpb: Fix possible memory leak
Date: Mon, 23 Aug 2021 10:09:12 +0900 [thread overview]
Message-ID: <1891546521.01629682681949.JavaMail.epsvc@epcpadp4> (raw)
In-Reply-To: <ca6e8507-743b-005a-faec-375d88d8aaf6@acm.org>
Hi Bart,
> On 8/19/21 6:46 PM, Keoseong Park wrote:
>> When HPB pinned region exists and mctx allocation for this region fails,
>> memory leak is possible because memory is not released for the subregion
>> table of the current region.
>>
>> So, change to free memory for the subregion table of the current region.
>>
>> Signed-off-by: Keoseong Park <keosung.park@samsung.com>
>> ---
>> drivers/scsi/ufs/ufshpb.c | 5 ++++-
>> 1 file changed, 4 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/scsi/ufs/ufshpb.c b/drivers/scsi/ufs/ufshpb.c
>> index 9acce92a356b..052f584c789a 100644
>> --- a/drivers/scsi/ufs/ufshpb.c
>> +++ b/drivers/scsi/ufs/ufshpb.c
>> @@ -1933,7 +1933,7 @@ static int ufshpb_alloc_region_tbl(struct ufs_hba *hba, struct ufshpb_lu *hpb)
>> if (ufshpb_is_pinned_region(hpb, rgn_idx)) {
>> ret = ufshpb_init_pinned_active_region(hba, hpb, rgn);
>> if (ret)
>> - goto release_srgn_table;
>> + goto release_current_srgn_table;
>> } else {
>> rgn->rgn_state = HPB_RGN_INACTIVE;
>> }
>> @@ -1944,6 +1944,9 @@ static int ufshpb_alloc_region_tbl(struct ufs_hba *hba, struct ufshpb_lu *hpb)
>>
>> return 0;
>>
>> +release_current_srgn_table:
>> + kvfree(rgn_table[rgn_idx].srgn_tbl);
>> +
>> release_srgn_table:
>> for (i = 0; i < rgn_idx; i++)
>> kvfree(rgn_table[i].srgn_tbl);
>
>'rgn_table' is allocated with kvcalloc() so please merge the new kvfree() statement
>with the for-loop below it.
>
>There is another improvement that can be made in this function: hpb->rgn_tbl
>is not cleared in the error path. I propose to move the "hpb->rgn_tbl = rgn_table"
>assignment from the start of the function to just above the "return 0" statement.
>
>Thanks,
>
>Bart.
>
Thank you for your feedback.
I will fix it.
Best Regards,
Keoseong
prev parent reply other threads:[~2021-08-23 1:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210820014624epcms2p6724e146ca1f93ba6eac5e7cf95d4cfd2@epcms2p6>
2021-08-20 1:46 ` [PATCH] scsi: ufs: ufshpb: Fix possible memory leak Keoseong Park
2021-08-20 20:28 ` Bart Van Assche
2021-08-23 1:09 ` Keoseong Park [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=1891546521.01629682681949.JavaMail.epsvc@epcpadp4 \
--to=keosung.park@samsung.com \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=daejun7.park@samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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