From: Matti Vaittinen <mazziesaccount@gmail.com>
To: Jiasheng Jiang <jiashengjiangcool@gmail.com>,
broonie@kernel.org, gregkh@linuxfoundation.org,
rafael@kernel.org, dakr@kernel.org
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] regmap-irq: Add missing kfree()
Date: Tue, 4 Feb 2025 10:33:58 +0200 [thread overview]
Message-ID: <27dd749e-712f-46eb-9630-660a8f8f490d@gmail.com> (raw)
In-Reply-To: <20250202200512.24490-1-jiashengjiangcool@gmail.com>
Thanks Jiang!
On 02/02/2025 22:05, Jiasheng Jiang wrote:
> Add kfree() for "d->main_status_buf" in the error-handling path to prevent
> a memory leak.
>
> Fixes: a2d21848d921 ("regmap: regmap-irq: Add main status register support")
> Cc: <stable@vger.kernel.org>
> Signed-off-by: Jiasheng Jiang <jiashengjiangcool@gmail.com>
This looks valid to me.
I still wonder if you could fix also the missing freeing from the
regmap_del_irq_chip()? (AFAICS, the freeing is missing from that as well).
> ---
> drivers/base/regmap/regmap-irq.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/base/regmap/regmap-irq.c b/drivers/base/regmap/regmap-irq.c
> index 0bcd81389a29..b73ab3cda781 100644
> --- a/drivers/base/regmap/regmap-irq.c
> +++ b/drivers/base/regmap/regmap-irq.c
> @@ -906,6 +906,7 @@ int regmap_add_irq_chip_fwnode(struct fwnode_handle *fwnode,
> kfree(d->wake_buf);
> kfree(d->mask_buf_def);
> kfree(d->mask_buf);
> + kfree(d->main_status_buf);
> kfree(d->status_buf);
> kfree(d->status_reg_buf);
> if (d->config_buf) {
next prev parent reply other threads:[~2025-02-04 8:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-02 20:05 [PATCH] regmap-irq: Add missing kfree() Jiasheng Jiang
2025-02-03 6:37 ` Greg KH
2025-02-04 2:57 ` [PATCH v2] " Jiasheng Jiang
2025-02-04 8:33 ` Matti Vaittinen [this message]
2025-02-05 0:43 ` [PATCH v3] " Jiasheng Jiang
2025-02-06 11:44 ` Mark Brown
2025-02-05 0:44 ` [PATCH] " Jiasheng Jiang
2025-02-06 11:44 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2025-02-02 18:18 Jiasheng Jiang
2025-02-02 19:35 ` Greg KH
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=27dd749e-712f-46eb-9630-660a8f8f490d@gmail.com \
--to=mazziesaccount@gmail.com \
--cc=broonie@kernel.org \
--cc=dakr@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jiashengjiangcool@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=stable@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.