From: Javier Martinez Canillas <javier@osg.samsung.com>
To: Jon Hunter <jonathanh@nvidia.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH] regulator: Fix deadlock during regulator registration
Date: Wed, 30 Mar 2016 19:25:49 -0400 [thread overview]
Message-ID: <56FC607D.3020108@osg.samsung.com> (raw)
In-Reply-To: <1459354153-6352-1-git-send-email-jonathanh@nvidia.com>
Hello Jon,
On 03/30/2016 12:09 PM, Jon Hunter wrote:
> Commit 5e3ca2b349b1 ("regulator: Try to resolve regulators supplies on
> registration") added a call to regulator_resolve_supply() within
> regulator_register() where the regulator_list_mutex is held. This causes
> the following deadlock to occur on the Tegra114 Dalmore board when the
> palmas PMIC is registered because regulator_register_resolve_supply()
> calls regulator_dev_lookup() which may try to acquire the
> regulator_list_mutex again.
>
Sorry for missing that. I didn't notice because on my machine the regulators
are looked up using OF and in that case the regulator_list_mutex isn't grabbed.
I believe your patch is correct, I have just one trivial comment below:
>
> @@ -4016,15 +4015,16 @@ scrub:
> regulator_ena_gpio_free(rdev);
> device_unregister(&rdev->dev);
> /* device core frees rdev */
> - rdev = ERR_PTR(ret);
> goto out;
>
> wash:
> regulator_ena_gpio_free(rdev);
> clean:
> kfree(rdev);
> - rdev = ERR_PTR(ret);
You are doing some cleanup of the clean and scrub error paths by removing
rdev and returning ERR_PTR(ret) directly. I believe that should be in a
separate patch since is not related to the fix.
> - goto out;
> +out:
> + mutex_unlock(®ulator_list_mutex);
> + kfree(config);
> + return ERR_PTR(ret);
> }
> EXPORT_SYMBOL_GPL(regulator_register);
>
>
If you split the cleanup and address Mark's comments, feel free to add:
Reviewed-by: Javier Martinez Canillas <javier@osg.samsung.com>
Best regards,
--
Javier Martinez Canillas
Open Source Group
Samsung Research America
next prev parent reply other threads:[~2016-03-30 23:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 16:09 Jon Hunter
2016-03-30 16:18 ` Mark Brown
2016-03-30 16:46 ` Jon Hunter
2016-03-30 17:00 ` Mark Brown
2016-03-30 17:41 ` Jon Hunter
2016-03-30 23:25 ` Javier Martinez Canillas [this message]
2016-03-30 23:34 ` Mark Brown
2016-03-30 23:38 ` Javier Martinez Canillas
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=56FC607D.3020108@osg.samsung.com \
--to=javier@osg.samsung.com \
--cc=broonie@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@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
Powered by JetHome