[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220309080219.GG3293@kadam>
Date: Wed, 9 Mar 2022 11:02:19 +0300
From: Dan Carpenter <dan.carpenter@...cle.com>
To: Vihas Makwana <makvihas@...il.com>
Cc: Larry Finger <Larry.Finger@...inger.net>,
Phillip Potter <phil@...lpotter.co.uk>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Michael Straube <straube.linux@...il.com>,
Martin Kaiser <martin@...ser.cx>,
Pavel Skripkin <paskripkin@...il.com>,
linux-staging@...ts.linux.dev, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] staging: r8188eu: proper error handling in
rtw_init_drv_sw
On Wed, Mar 09, 2022 at 02:25:10AM +0530, Vihas Makwana wrote:
> The code inside rtw_init_drv_sw() calls various init functions to
> populate the padapter structure and checks for their return values
> respectively.
> But if one of the functions in middle fails then it simply returns
> _FAIL instead of proper logging and calling freeing counterparts
> of previous init functions.
> This leads to various memory leaks and can be found in
> /sys/kernel/debug/kmemleak if kernel is compiled with DEBUG_KMEMLEAK=y.
>
> Fix this and keep the success and error separate.
>
Delete the extra blank line. Feel free to add a Fixes tag which points
to the driver add commit.
Looks good.
Reviewed-by: Dan Carpenter <dan.carpenter@...cle.com>
>
> Signed-off-by: Vihas Makwana <makvihas@...il.com>
> ---
> Tested on Comfast CF-WU810N RTL8188EUS wireless adapter.
> This patch depends on "[PATCH 1/2] staging: r8188eu: call _cancel_timer_ex from
> _rtw_free_recv_priv"
This is a patchset so that's assumed. No need to say it. Also it's not
really true. Those patches are independent and can be applied in any
order.
regards,
dan carpenter
Powered by blists - more mailing lists