ASoC: Use nested lock for snd_soc_dapm_mutex_lock
authorCharles Keepax <ckeepax@opensource.wolfsonmicro.com>
Tue, 29 Dec 2015 16:25:13 +0000 (16:25 +0000)
committerMark Brown <broonie@kernel.org>
Wed, 30 Dec 2015 16:48:13 +0000 (16:48 +0000)
commit783513eec3209542fcd6ac0cbcb030b3c17a4827
tree5fc9e0b95a11e500efe7e1f1addff5fc56853913
parent8005c49d9aea74d382f474ce11afbbc7d7130bec
ASoC: Use nested lock for snd_soc_dapm_mutex_lock

snd_soc_dapm_mutex_lock currently uses the un-nested call which can
cause lockdep warnings when called from control handlers (a relatively
common usage) and using modules. As creating the control causes a
potential mutex inversion with the handler, creating the control will
take the controls_rwsem under the dapm_mutex and accessing the control
will take the dapm_mutex under controls_rwsem.

All the users look like they want to be using the runtime class of the
lock anyway, so this patch just changes snd_soc_dapm_mutex_lock to use
the nested call, with the SND_SOC_DAPM_CLASS_RUNTIME class.

Fixes: f6d5e586b416 ("ASoC: dapm: Add helpers to lock/unlock DAPM mutex")
Signed-off-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Signed-off-by: Mark Brown <broonie@kernel.org>
include/sound/soc.h