From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: John Stultz <john.stultz@linaro.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
Mark Brown <broonie@kernel.org>,
Tyler Baker <tyler.baker@linaro.org>,
Thierry Reding <treding@nvidia.com>,
stable <stable@vger.kernel.org>
Subject: Re: [RFC][PATCH 4.4-stable] regulator: core: Ensure we lock all regulators
Date: Fri, 6 May 2016 12:06:38 -0400 [thread overview]
Message-ID: <20160506160638.GA3479@kroah.com> (raw)
In-Reply-To: <1461890617-29209-1-git-send-email-john.stultz@linaro.org>
On Thu, Apr 28, 2016 at 05:43:37PM -0700, John Stultz wrote:
> It seems upstream commit 49a6bb7a1c09 ("regulator: core: Ensure
> we lock all regulators"), was missed when considering tagging
> for -stable.
>
> Without this varient of that patch (the original doesn't apply,
> due to a later fix to the same which was backported), I see
> double-unlock lockdep splats in the v4.4.8 based HiKey kernel.
>
> Cc: Mark Brown <broonie@kernel.org>
> Cc: Tyler Baker <tyler.baker@linaro.org>
> Cc: Thierry Reding <treding@nvidia.com>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> CC: stable <stable@vger.kernel.org> # 4.4 only (I think)
> Fixes: 3c2c5fb9b99ca ("regulator: core: avoid unused variable warning")
> Originally-Reported-by: Tyler Baker <tyler.baker@linaro.org>
> Originally-by: Mark Brown <broonie@kernel.org>
> Signed-off-by: John Stultz <john.stultz@linaro.org>
> ---
> drivers/regulator/core.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c
> index 7b94b8e..732ac71 100644
> --- a/drivers/regulator/core.c
> +++ b/drivers/regulator/core.c
> @@ -148,7 +148,7 @@ static void regulator_lock_supply(struct regulator_dev *rdev)
> {
> int i;
>
> - for (i = 0; rdev->supply; rdev = rdev_get_supply(rdev), i++)
> + for (i = 0; rdev; rdev = rdev_get_supply(rdev), i++)
> mutex_lock_nested(&rdev->mutex, i);
> }
>
This should now all be fixed in 4.4.9, and this patch isn't needed,
right?
thanks,
greg k-h
next prev parent reply other threads:[~2016-05-06 17:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-29 0:43 [RFC][PATCH 4.4-stable] regulator: core: Ensure we lock all regulators John Stultz
2016-04-29 10:20 ` Mark Brown
2016-05-06 16:06 ` Greg Kroah-Hartman [this message]
2016-05-06 17:57 ` John Stultz
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=20160506160638.GA3479@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=broonie@kernel.org \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=treding@nvidia.com \
--cc=tyler.baker@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.