From: Lyndon Sanche <lsanche@lyndeno.ca>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: "Hans de Goede" <hdegoede@redhat.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] platform/x86: dell-pc: avoid double free and invalid unregistration
Date: Tue, 04 Jun 2024 20:46:29 -0600 [thread overview]
Message-ID: <HD6LES.A9HJVAFECS8L3@lyndeno.ca> (raw)
In-Reply-To: <20240604-dell-pc-double-free-v1-1-6d81255b2a44@weissschuh.net>
On Tue, Jun 4 2024 at 11:41:24 PM +02:00:00, Thomas Weißschuh
<linux@weissschuh.net> wrote:
> If platform_profile_register() fails it does kfree(thermal_handler)
> and
> leaves the pointer value around.
> Any call to thermal_cleanup() will try to kfree(thermal_handler)
> again.
> This will happen right away in dell_init().
> In addition, platform_profile_remove() will be called although no
> profile is registered.
>
> NULL out the thermal_handler, so thermal_cleanup() avoids the double
> free.
>
> Fixes: 996ad4129810 ("platform/x86: dell-pc: Implement
> platform_profile")
> Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
> ---
> Currently the call to thermal_cleanup() in dell_init() is completely
> unnecessary. But I guess more functionality will be handled by the
> driver and then this structure makes sense.
>
> This is untested.
> ---
> drivers/platform/x86/dell/dell-pc.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/platform/x86/dell/dell-pc.c
> b/drivers/platform/x86/dell/dell-pc.c
> index dfe09c463d03..972385ca1990 100644
> --- a/drivers/platform/x86/dell/dell-pc.c
> +++ b/drivers/platform/x86/dell/dell-pc.c
> @@ -261,8 +261,10 @@ static int thermal_init(void)
>
> /* Clean up if failed */
> ret = platform_profile_register(thermal_handler);
> - if (ret)
> + if (ret) {
> kfree(thermal_handler);
> + thermal_handler = NULL;
> + }
>
> return ret;
> }
>
> ---
> base-commit: 0da7a954480cc99978e3570c991e3779e56fc736
> change-id: 20240604-dell-pc-double-free-e8cf2aa9b2fb
>
> Best regards,
> --
> Thomas Weißschuh <linux@weissschuh.net>
Thank you for this patch. I was able to apply your patch and compile
successfully. I have not had a chance to try it on my hardware.
I agree with the change, and it looks good to me.
Thanks,
Reviewed-by: Lyndon Sanche <lsanche@lyndeno.ca>
next prev parent reply other threads:[~2024-06-05 2:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-04 21:41 Thomas Weißschuh
2024-06-05 2:46 ` Lyndon Sanche [this message]
2024-06-07 13:22 ` Ilpo Järvinen
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=HD6LES.A9HJVAFECS8L3@lyndeno.ca \
--to=lsanche@lyndeno.ca \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=platform-driver-x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®