linux-fpga.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH RESEND] fpga: region: Fix possible memory leak in fpga_region_register_full()
@ 2023-09-28  9:16 Jinjie Ruan
  2023-09-28 14:02 ` Xu Yilun
  2023-09-28 15:45 ` Russ Weight
  0 siblings, 2 replies; 4+ messages in thread
From: Jinjie Ruan @ 2023-09-28  9:16 UTC (permalink / raw)
  To: mdf, hao.wu, yilun.xu, trix, russell.h.weight, linux-fpga,
	linux-kernel
  Cc: ruanjinjie

If device_register() fails in fpga_region_register_full(), the region
allocated by kzalloc() and the id allocated by ida_alloc() also need be
freed otherwise will cause memory leak.

Fixes: 8886a579744f ("fpga: region: Use standard dev_release for class driver")
Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com>
---
 drivers/fpga/fpga-region.c | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/drivers/fpga/fpga-region.c b/drivers/fpga/fpga-region.c
index b364a929425c..9dc6314976ef 100644
--- a/drivers/fpga/fpga-region.c
+++ b/drivers/fpga/fpga-region.c
@@ -228,12 +228,13 @@ fpga_region_register_full(struct device *parent, const struct fpga_region_info *
 
 	ret = device_register(&region->dev);
 	if (ret) {
-		put_device(&region->dev);
-		return ERR_PTR(ret);
+		goto err_put_device;
 	}
 
 	return region;
 
+err_put_device:
+	put_device(&region->dev);
 err_remove:
 	ida_free(&fpga_region_ida, id);
 err_free:
-- 
2.34.1


^ permalink raw reply related	[flat|nested] 4+ messages in thread

* Re: [PATCH RESEND] fpga: region: Fix possible memory leak in fpga_region_register_full()
  2023-09-28  9:16 [PATCH RESEND] fpga: region: Fix possible memory leak in fpga_region_register_full() Jinjie Ruan
@ 2023-09-28 14:02 ` Xu Yilun
  2023-09-28 15:45 ` Russ Weight
  1 sibling, 0 replies; 4+ messages in thread
From: Xu Yilun @ 2023-09-28 14:02 UTC (permalink / raw)
  To: Jinjie Ruan
  Cc: mdf, hao.wu, yilun.xu, trix, russell.h.weight, linux-fpga,
	linux-kernel

On Thu, Sep 28, 2023 at 05:16:36PM +0800, Jinjie Ruan wrote:
> If device_register() fails in fpga_region_register_full(), the region
> allocated by kzalloc() and the id allocated by ida_alloc() also need be
> freed otherwise will cause memory leak.

How did you observe the memory leak? Please help provide some trace.

Thanks,
Yilun

> 
> Fixes: 8886a579744f ("fpga: region: Use standard dev_release for class driver")
> Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com>
> ---
>  drivers/fpga/fpga-region.c | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/fpga/fpga-region.c b/drivers/fpga/fpga-region.c
> index b364a929425c..9dc6314976ef 100644
> --- a/drivers/fpga/fpga-region.c
> +++ b/drivers/fpga/fpga-region.c
> @@ -228,12 +228,13 @@ fpga_region_register_full(struct device *parent, const struct fpga_region_info *
>  
>  	ret = device_register(&region->dev);
>  	if (ret) {
> -		put_device(&region->dev);
> -		return ERR_PTR(ret);
> +		goto err_put_device;
>  	}
>  
>  	return region;
>  
> +err_put_device:
> +	put_device(&region->dev);
>  err_remove:
>  	ida_free(&fpga_region_ida, id);
>  err_free:
> -- 
> 2.34.1
> 

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH RESEND] fpga: region: Fix possible memory leak in fpga_region_register_full()
  2023-09-28  9:16 [PATCH RESEND] fpga: region: Fix possible memory leak in fpga_region_register_full() Jinjie Ruan
  2023-09-28 14:02 ` Xu Yilun
@ 2023-09-28 15:45 ` Russ Weight
  2023-10-07  9:15   ` Ruan Jinjie
  1 sibling, 1 reply; 4+ messages in thread
From: Russ Weight @ 2023-09-28 15:45 UTC (permalink / raw)
  To: Jinjie Ruan, mdf, hao.wu, yilun.xu, trix, linux-fpga,
	linux-kernel



On 9/28/23 02:16, Jinjie Ruan wrote:
> If device_register() fails in fpga_region_register_full(), the region
> allocated by kzalloc() and the id allocated by ida_alloc() also need be
> freed otherwise will cause memory leak.
>
> Fixes: 8886a579744f ("fpga: region: Use standard dev_release for class driver")
> Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com>
> ---
>  drivers/fpga/fpga-region.c | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/fpga/fpga-region.c b/drivers/fpga/fpga-region.c
> index b364a929425c..9dc6314976ef 100644
> --- a/drivers/fpga/fpga-region.c
> +++ b/drivers/fpga/fpga-region.c
> @@ -228,12 +228,13 @@ fpga_region_register_full(struct device *parent, const struct fpga_region_info *
>  
>  	ret = device_register(&region->dev);

The comments for device_register() say:

 * NOTE: _Never_ directly free @dev after calling this function, even
 * if it returned an error! Always use put_device() to give up the
 * reference initialized in this function instead.

Note that dev is embedded in the region structure, so freeing region
means freeing dev.

The expectation is that after device_register() has been called, even
if it returns an error, put_device() is used to lower the reference
count. When the reference count is zero, the fpga_region_dev_release()
function is called. fpga_region_dev_release() frees calls ida_free()
and frees the region.

Have you observed different behavior? Do you have evidence of a memory
leak?

Thanks,
- Russ

>  	if (ret) {
> -		put_device(&region->dev);
> -		return ERR_PTR(ret);
> +		goto err_put_device;
>  	}
>  
>  	return region;
>  
> +err_put_device:
> +	put_device(&region->dev);
>  err_remove:
>  	ida_free(&fpga_region_ida, id);
>  err_free:


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH RESEND] fpga: region: Fix possible memory leak in fpga_region_register_full()
  2023-09-28 15:45 ` Russ Weight
@ 2023-10-07  9:15   ` Ruan Jinjie
  0 siblings, 0 replies; 4+ messages in thread
From: Ruan Jinjie @ 2023-10-07  9:15 UTC (permalink / raw)
  To: Russ Weight, mdf, hao.wu, yilun.xu, trix, linux-fpga,
	linux-kernel



On 2023/9/28 23:45, Russ Weight wrote:
> 
> 
> On 9/28/23 02:16, Jinjie Ruan wrote:
>> If device_register() fails in fpga_region_register_full(), the region
>> allocated by kzalloc() and the id allocated by ida_alloc() also need be
>> freed otherwise will cause memory leak.
>>
>> Fixes: 8886a579744f ("fpga: region: Use standard dev_release for class driver")
>> Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com>
>> ---
>>  drivers/fpga/fpga-region.c | 5 +++--
>>  1 file changed, 3 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/fpga/fpga-region.c b/drivers/fpga/fpga-region.c
>> index b364a929425c..9dc6314976ef 100644
>> --- a/drivers/fpga/fpga-region.c
>> +++ b/drivers/fpga/fpga-region.c
>> @@ -228,12 +228,13 @@ fpga_region_register_full(struct device *parent, const struct fpga_region_info *
>>  
>>  	ret = device_register(&region->dev);
> 
> The comments for device_register() say:
> 
>  * NOTE: _Never_ directly free @dev after calling this function, even
>  * if it returned an error! Always use put_device() to give up the
>  * reference initialized in this function instead.
> 
> Note that dev is embedded in the region structure, so freeing region
> means freeing dev.
> 
> The expectation is that after device_register() has been called, even
> if it returns an error, put_device() is used to lower the reference
> count. When the reference count is zero, the fpga_region_dev_release()
> function is called. fpga_region_dev_release() frees calls ida_free()
> and frees the region.

Right!

> 
> Have you observed different behavior? Do you have evidence of a memory
> leak?

I have noticed a memory leak in using fpga_region_register_full() in
fpga-region-test.c. I'll send the patch sooner.

> 
> Thanks,
> - Russ
> 
>>  	if (ret) {
>> -		put_device(&region->dev);
>> -		return ERR_PTR(ret);
>> +		goto err_put_device;
>>  	}
>>  
>>  	return region;
>>  
>> +err_put_device:
>> +	put_device(&region->dev);
>>  err_remove:
>>  	ida_free(&fpga_region_ida, id);
>>  err_free:
> 

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2023-10-07  9:16 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-09-28  9:16 [PATCH RESEND] fpga: region: Fix possible memory leak in fpga_region_register_full() Jinjie Ruan
2023-09-28 14:02 ` Xu Yilun
2023-09-28 15:45 ` Russ Weight
2023-10-07  9:15   ` Ruan Jinjie

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).