From: Greg KH <gregkh@linuxfoundation.org>
To: xkernel.wang@foxmail.com
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] staging: rtl8723bs: fix a potential memory leak in rtw_init_cmd_priv()
Date: Fri, 9 Sep 2022 09:49:25 +0200 [thread overview]
Message-ID: <YxrwBV9Xb/5ucEHA@kroah.com> (raw)
In-Reply-To: <tencent_3FB11458E1274AF3FF69207CCC10B92F1C08@qq.com>
On Thu, Sep 08, 2022 at 03:33:00PM +0800, xkernel.wang@foxmail.com wrote:
> From: Xiaoke Wang <xkernel.wang@foxmail.com>
>
> In rtw_init_cmd_priv(), if `pcmdpriv->rsp_allocated_buf` is allocated
> in failure, then `pcmdpriv->cmd_allocated_buf` will be not properly
> released. Besides, considering there are only two error paths and the
> first one can directly return, so we do not need implicitly jump to the
> `exit` tag to execute the error handler.
>
> So this patch added `kfree(pcmdpriv->cmd_allocated_buf);` on the error
> path to release the resource and simplified the return logic of
Again, whitespace at end of changelog text :(
> rtw_init_cmd_priv(). As there is no FooBar device to test with, no runtime
> testing was performed.
"FooBar"?
>
> Signed-off-by: Xiaoke Wang <xkernel.wang@foxmail.com>
> ---
> ChangeLog:
> v1->v2 update the description.
> v2->v3 update the description.
> drivers/staging/rtl8723bs/core/rtw_cmd.c | 17 +++++++----------
> 1 file changed, 7 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/staging/rtl8723bs/core/rtw_cmd.c b/drivers/staging/rtl8723bs/core/rtw_cmd.c
> index e574893..9126ea9 100644
> --- a/drivers/staging/rtl8723bs/core/rtw_cmd.c
> +++ b/drivers/staging/rtl8723bs/core/rtw_cmd.c
> @@ -161,8 +161,6 @@ static struct cmd_hdl wlancmds[] = {
>
> int rtw_init_cmd_priv(struct cmd_priv *pcmdpriv)
> {
> - int res = 0;
> -
> init_completion(&pcmdpriv->cmd_queue_comp);
> init_completion(&pcmdpriv->terminate_cmdthread_comp);
>
> @@ -175,18 +173,17 @@ int rtw_init_cmd_priv(struct cmd_priv *pcmdpriv)
>
> pcmdpriv->cmd_allocated_buf = rtw_zmalloc(MAX_CMDSZ + CMDBUFF_ALIGN_SZ);
>
> - if (!pcmdpriv->cmd_allocated_buf) {
> - res = -ENOMEM;
> - goto exit;
> - }
> + if (!pcmdpriv->cmd_allocated_buf)
> + return -ENOMEM;
>
> pcmdpriv->cmd_buf = pcmdpriv->cmd_allocated_buf + CMDBUFF_ALIGN_SZ - ((SIZE_PTR)(pcmdpriv->cmd_allocated_buf) & (CMDBUFF_ALIGN_SZ-1));
>
> pcmdpriv->rsp_allocated_buf = rtw_zmalloc(MAX_RSPSZ + 4);
>
> if (!pcmdpriv->rsp_allocated_buf) {
> - res = -ENOMEM;
> - goto exit;
> + kfree(pcmdpriv->cmd_allocated_buf);
> + pcmdpriv->cmd_allocated_buf = NULL;
Why does this have to be set to NULL?
thanks,
greg k-h
prev parent reply other threads:[~2022-09-09 7:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 7:33 [PATCH v3] staging: rtl8723bs: fix a potential memory leak in rtw_init_cmd_priv() xkernel.wang
2022-09-09 7:49 ` Greg KH [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=YxrwBV9Xb/5ucEHA@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=xkernel.wang@foxmail.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