mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mario Limonciello <mario.limonciello@amd.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	"Perry Yuan" <perry.yuan@amd.com>,
	"Hans de Goede" <hansg@kernel.org>,
	"Gautham R. Shenoy" <gautham.shenoy@amd.com>,
	"Borislav Petkov (AMD)" <bp@alien8.de>,
	platform-driver-x86@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	"Guangshuo Li" <lgs201920130244@gmail.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] platform/x86/amd/hfi: fix platform device leak on init failure
Date: Thu, 8 Oct 2026 15:04:25 -0500	[thread overview]
Message-ID: <ed80d662-663d-40a4-abae-1dca9cf8e97d@amd.com> (raw)
In-Reply-To: <179148103665.29028.12297507526234628809.b4-ty@b4>



On 10/8/26 12:37, Ilpo Järvinen wrote:
> On Mon, 21 Sep 2026 16:26:09 +0800, Guangshuo Li wrote:
> 
>> amd_hfi_init() registers the HFI platform device before registering
>> the platform driver. If platform_driver_register() fails, the function
>> returns the error without unregistering the already registered platform
>> device.
>>
>> Since the failed init path does not run amd_hfi_exit(), the platform
>> device remains registered and its reference is never dropped, preventing
>> the associated platform object from being released.
>>
>> [...]
> 
> Thank you for your contribution, it has been applied to my local
> review-ilpo-next branch. Note it will show up in the public
> platform-drivers-x86/review-ilpo-next branch only once I've pushed my
> local branch there, which might take a while.
> 
> FYI [if applicable to your patch], as per Linus' policy change, also
> fixes are mostly routed through for-next unless the fix is for a
> commit introduced in the most recent cycle or is clearly a regression
> fix.
> 
> The list of commits applied:
> [1/1] platform/x86/amd/hfi: fix platform device leak on init failure
>        commit: a15d58ff15a6ede327e3814c791c6912b973e434
> 
> --
>   i.

Hi Ilpo,

Did you see my follow up comment that this patch should be unnecessary?

https://lore.kernel.org/platform-driver-x86/652e3b3b-0f56-4d01-8fd8-e4a9ddedabfe@kernel.org/

Basically pointless call torn out by this series:

https://lore.kernel.org/platform-driver-x86/20260921170411.1149960-1-mario.limonciello@amd.com/

      reply	other threads:[~2026-10-08 20:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-21  8:26 Guangshuo Li
2026-09-21 13:43 ` Mario Limonciello
2026-09-21 17:29   ` Mario Limonciello
2026-09-21 15:04 ` krzk
2026-09-21 15:07 ` krzk
2026-09-21 15:15 ` krzk
2026-09-21 22:03   ` Krzysztof Kozlowski
2026-09-22  2:11     ` Guangshuo Li
2026-09-22  3:05       ` Borislav Petkov
2026-09-22  6:25         ` Guangshuo Li
2026-10-08 17:37 ` Ilpo Järvinen
2026-10-08 20:04   ` Mario Limonciello [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=ed80d662-663d-40a4-abae-1dca9cf8e97d@amd.com \
    --to=mario.limonciello@amd.com \
    --cc=bp@alien8.de \
    --cc=gautham.shenoy@amd.com \
    --cc=hansg@kernel.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=lgs201920130244@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perry.yuan@amd.com \
    --cc=platform-driver-x86@vger.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 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®