[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <177020081722.10510.7309384536094598745.b4-ty@oss.qualcomm.com>
Date: Wed, 4 Feb 2026 11:27:35 +0100
From: Bartosz Golaszewski <bartosz.golaszewski@....qualcomm.com>
To: Bartosz Golaszewski <brgl@...nel.org>,
Ziyi Guo <n7l8m4@...orthwestern.edu>
Cc: Bartosz Golaszewski <bartosz.golaszewski@....qualcomm.com>,
linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] power: pwrseq: fix missing state_lock in pwrseq_power_on() error path
On Fri, 30 Jan 2026 18:26:51 +0000, Ziyi Guo wrote:
> pwrseq_power_on() calls pwrseq_unit_disable() when the
> post_enable callback fails. However, this call is outside the
> scoped_guard(mutex, &pwrseq->state_lock) block that ends.
>
> pwrseq_unit_disable() has lockdep_assert_held(&pwrseq->state_lock),
> which will fail when called from this error path.
>
> [...]
Applied, thanks!
[1/1] power: pwrseq: fix missing state_lock in pwrseq_power_on() error path
https://git.kernel.org/brgl/c/e1dccb485c2876ac1318f36ccc0155416c633a48
Best regards,
--
Bartosz Golaszewski <bartosz.golaszewski@....qualcomm.com>
Powered by blists - more mailing lists