From: Lee Jones <lee@kernel.org>
To: kr494167@gmail.com
Cc: pavel@kernel.org, s.trumtrar@pengutronix.de,
linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] leds: lp5860: fix init error-path locking
Date: Thu, 6 Aug 2026 13:32:09 +0100 [thread overview]
Message-ID: <20260806123209.GD2869284@google.com> (raw)
In-Reply-To: <20260720104838.98101-1-kr494167@gmail.com>
On Mon, 20 Jul 2026, kr494167@gmail.com wrote:
> From: surendra <kr494167@gmail.com>
>
> lp5860_device_init() unlocks lp->lock after updating the device mode.
> An lp5860_init_dt() failure then jumps to err_disable, which attempts to
> unlock the mutex a second time before disabling the chip.
>
> Unlock immediately after the register update and keep the common error
> handler lockless.
>
> Fixes: f0a66563aa2d ("leds: Add support for TI LP5860 LED driver chip")
>
> Signed-off-by: surendra <kr494167@gmail.com>
Full names in SoBs please.
> ---
> drivers/leds/rgb/leds-lp5860-core.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/leds/rgb/leds-lp5860-core.c b/drivers/leds/rgb/leds-lp5860-core.c
> index fd0e2f6e6e0f..e21d5f2302be 100644
> --- a/drivers/leds/rgb/leds-lp5860-core.c
> +++ b/drivers/leds/rgb/leds-lp5860-core.c
> @@ -204,9 +204,9 @@ int lp5860_device_init(struct device *dev)
> mutex_lock(&lp->lock);
> ret = regmap_update_bits(lp->regmap, LP5860_REG_DEV_INITIAL, LP5860_MODE_MASK,
> LP5860_MODE_1 << LP5860_MODE_SHIFT);
> + mutex_unlock(&lp->lock);
> if (ret)
> goto err_disable;
> - mutex_unlock(&lp->lock);
>
> ret = lp5860_init_dt(lp);
> if (ret)
> @@ -215,7 +215,6 @@ int lp5860_device_init(struct device *dev)
> return 0;
>
> err_disable:
> - mutex_unlock(&lp->lock);
> lp5860_chip_enable(lp, LP5860_CHIP_DISABLE);
> return ret;
> }
> --
> 2.55.0
--
Lee Jones
prev parent reply other threads:[~2026-08-06 12:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 10:48 [PATCH v2] leds: lp5860: fix init error-path locking kr494167
2026-07-20 11:00 ` sashiko-bot
2026-08-06 12:32 ` Lee Jones [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=20260806123209.GD2869284@google.com \
--to=lee@kernel.org \
--cc=kr494167@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@kernel.org \
--cc=s.trumtrar@pengutronix.de \
/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