mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Borah, Chaitanya Kumar" <chaitanya.kumar.borah@intel.com>
To: Steffen Dirkwinkel <lists@steffen.cc>,
	Sebastian Reichel <sre@kernel.org>
Cc: <linux-pm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	"Sebastian Reichel" <sebastian.reichel@collabora.com>,
	Steffen Dirkwinkel <s.dirkwinkel@beckhoff.com>
Subject: Re: [PATCH] power: supply: hold extensions_sem when creating LED triggers
Date: Fri, 24 Jul 2026 15:46:40 +0530	[thread overview]
Message-ID: <a3fbfc29-3591-4e20-a006-425986d95319@intel.com> (raw)
In-Reply-To: <20260724-power-supply-triggers-lockdep-v1-1-9b451b1f1916@beckhoff.com>



On 7/24/2026 12:57 PM, Steffen Dirkwinkel wrote:
> From: Steffen Dirkwinkel <s.dirkwinkel@beckhoff.com>
> 
> LED triggers were created in __power_supply_register without holding the
> extensions_sem lock. Since commit b04510c3af6d ("power: supply: leds: create
> triggers based on properties, not type") we call power_supply_has_property
> during trigger creation and access the extensions there.
> Move power_supply_create_triggers down into the lock scope used for
> power_supply_add_hwmon_sysfs for the same reason.
> 

Tested-by: Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com>

> Fixes: b04510c3af6d ("power: supply: leds: create triggers based on properties, not type")
> Reported-by: Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com>
> Closes: https://lore.kernel.org/all/a95a2720-4092-4b49-bd9d-b700f1c2680d@intel.com/
> Signed-off-by: Steffen Dirkwinkel <s.dirkwinkel@beckhoff.com>
> ---
>   drivers/power/supply/power_supply_core.c | 8 ++++----
>   1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/power/supply/power_supply_core.c b/drivers/power/supply/power_supply_core.c
> index 2532e221b2e1..cbf6ebef7850 100644
> --- a/drivers/power/supply/power_supply_core.c
> +++ b/drivers/power/supply/power_supply_core.c
> @@ -1636,11 +1636,11 @@ __power_supply_register(struct device *parent,
>   	if (rc)
>   		goto register_thermal_failed;
>   
> -	rc = power_supply_create_triggers(psy);
> -	if (rc)
> -		goto create_triggers_failed;
> -
>   	scoped_guard(rwsem_read, &psy->extensions_sem) {
> +		rc = power_supply_create_triggers(psy);
> +		if (rc)
> +			goto create_triggers_failed;
> +
>   		rc = power_supply_add_hwmon_sysfs(psy);
>   		if (rc)
>   			goto add_hwmon_sysfs_failed;
> 
> ---
> base-commit: 657cd3a42e937276262c0a8ae6b01a87004309de
> change-id: 20260724-power-supply-triggers-lockdep-2083247dcecd
> 
> Best regards,
> --
> Steffen Dirkwinkel <s.dirkwinkel@beckhoff.com>
> 


  reply	other threads:[~2026-07-24 10:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-24  7:27 Steffen Dirkwinkel
2026-07-24 10:16 ` Borah, Chaitanya Kumar [this message]
2026-07-24 23:35 ` Sebastian Reichel

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=a3fbfc29-3591-4e20-a006-425986d95319@intel.com \
    --to=chaitanya.kumar.borah@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=lists@steffen.cc \
    --cc=s.dirkwinkel@beckhoff.com \
    --cc=sebastian.reichel@collabora.com \
    --cc=sre@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®