From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: Nam Cao <namcaov@gmail.com>,
forest@alittletooquiet.net, gregkh@linuxfoundation.org
Cc: ji_hun.kim@samsung.com, dan.carpenter@oracle.com,
linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev
Subject: Re: [PATCH] staging: vt6655: fix some erroneous memory clean-up loops
Date: Mon, 12 Sep 2022 21:01:44 +0200 [thread overview]
Message-ID: <2b11e266-2266-b0da-3fb1-3df26236e012@gmail.com> (raw)
In-Reply-To: <20220912170429.29852-1-namcaov@gmail.com>
On 9/12/22 19:04, Nam Cao wrote:
> In some initialization functions of this driver, memory is allocated with
> 'i' acting as an index variable and increasing from 0. The commit in
> "Fixes" introduces some clean-up codes in case of allocation failure,
> which free memory in reverse order with 'i' decreasing to 0. However,
> there are some problems:
> - The case i=0 is left out. Thus memory is leaked.
> - In case memory allocation fails right from the start, the memory
> freeing loops will start with i=-1 and invalid memory locations will
> be accessed.
>
> One of these loops has been fixed in commit c8ff91535880 ("staging:
> vt6655: fix potential memory leak"). Fix the remaining erroneous loops.
>
> Link: https://lore.kernel.org/linux-staging/Yx9H1zSpxmNqx6Xc@kadam/
> Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
> Fixes: 5341ee0adb17 ("staging: vt6655: check for memory allocation failures")
> Signed-off-by: Nam Cao <namcaov@gmail.com>
> ---
> drivers/staging/vt6655/device_main.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/staging/vt6655/device_main.c b/drivers/staging/vt6655/device_main.c
> index 04d737012cef..56c3cf3ba53d 100644
> --- a/drivers/staging/vt6655/device_main.c
> +++ b/drivers/staging/vt6655/device_main.c
> @@ -631,7 +631,7 @@ static int device_init_rd0_ring(struct vnt_private *priv)
> kfree(desc->rd_info);
>
> err_free_desc:
> - while (--i) {
> + while (i--) {
> desc = &priv->aRD0Ring[i];
> device_free_rx_buf(priv, desc);
> kfree(desc->rd_info);
> @@ -677,7 +677,7 @@ static int device_init_rd1_ring(struct vnt_private *priv)
> kfree(desc->rd_info);
>
> err_free_desc:
> - while (--i) {
> + while (i--) {
> desc = &priv->aRD1Ring[i];
> device_free_rx_buf(priv, desc);
> kfree(desc->rd_info);
> @@ -782,7 +782,7 @@ static int device_init_td1_ring(struct vnt_private *priv)
> return 0;
>
> err_free_desc:
> - while (--i) {
> + while (i--) {
> desc = &priv->apTD1Rings[i];
> kfree(desc->td_info);
> }
Tested-by: Philipp Hortmann <philipp.g.hortmann@gmail.com>
prev parent reply other threads:[~2022-09-12 19:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 17:04 [PATCH] staging: vt6655: fix some erroneous memory clean-up loops Nam Cao
2022-09-12 19:01 ` Philipp Hortmann [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=2b11e266-2266-b0da-3fb1-3df26236e012@gmail.com \
--to=philipp.g.hortmann@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=forest@alittletooquiet.net \
--cc=gregkh@linuxfoundation.org \
--cc=ji_hun.kim@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=namcaov@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