Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lars-Peter Clausen <lars@metafoo.de>
To: Jarkko Nikula <jarkko.nikula@linux.intel.com>
Cc: alsa-devel@alsa-project.org, Mark Brown <broonie@kernel.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	stable <stable@vger.kernel.org>
Subject: Re: [PATCH] ASoC: dapm: Fix widget double free with auto-disable DAPM kcontrol
Date: Tue, 15 Apr 2014 20:15:45 +0200	[thread overview]
Message-ID: <534D7751.7030609@metafoo.de> (raw)
In-Reply-To: <1397570289-29215-1-git-send-email-jarkko.nikula@linux.intel.com>

On 04/15/2014 03:58 PM, Jarkko Nikula wrote:
> Commit 9e1fda4ae158 ("ASoC: dapm: Implement mixer input auto-disable") is trying to
> free the widget it allocated by snd_soc_dapm_new_control() call in
> dapm_kcontrol_data_alloc() by adding kfree(data->widget) to dapm_kcontrol_free().
>
> This is causing a widget double free with auto-disabled DAPM kcontrols in sound card
> unregistration because widgets are already freed before dapm_kcontrol_free() is
> called.
>
> Reason for that is all widgets are added into dapm->card->widgets list in
> snd_soc_dapm_new_control() and freed in dapm_free_widgets() during execution of
> snd_soc_dapm_free().
>
> Now snd_soc_dapm_free() calls for different DAPM contexts happens before
> snd_card_free() call from where the call chain to dapm_kcontrol_free() begins:
>
> soc_cleanup_card_resources()
>    soc_remove_dai_links()
>      soc_remove_link_dais()
>        snd_soc_dapm_free(&cpu_dai->dapm)
>      soc_remove_link_components()
>        soc_remove_platform()
>          snd_soc_dapm_free(&platform->dapm)
>        soc_remove_codec()
>          snd_soc_dapm_free(&codec->dapm)
>    snd_soc_dapm_free(&card->dapm)
>    snd_card_free()
>      snd_card_do_free()
>        snd_device_free_all()
>          snd_device_free()
>            snd_ctl_dev_free()
>              snd_ctl_remove()
>                snd_ctl_free_one()
>                  dapm_kcontrol_free()
>
> This wasn't making harm with ordinary DAPM kcontrols since data->widget is NULL for
> them.
>
> Signed-off-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>
> Cc: stable <stable@vger.kernel.org> # 3.12+

Acked-by: Lars-Peter Clausen <lars@metafoo.de>

Thanks.

> ---
>   sound/soc/soc-dapm.c | 1 -
>   1 file changed, 1 deletion(-)
>
> diff --git a/sound/soc/soc-dapm.c b/sound/soc/soc-dapm.c
> index c8a780d0d057..7769b0a2bc5a 100644
> --- a/sound/soc/soc-dapm.c
> +++ b/sound/soc/soc-dapm.c
> @@ -254,7 +254,6 @@ static int dapm_kcontrol_data_alloc(struct snd_soc_dapm_widget *widget,
>   static void dapm_kcontrol_free(struct snd_kcontrol *kctl)
>   {
>   	struct dapm_kcontrol_data *data = snd_kcontrol_chip(kctl);
> -	kfree(data->widget);
>   	kfree(data->wlist);
>   	kfree(data);
>   }
>

  reply	other threads:[~2014-04-15 18:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-15 13:58 [PATCH] ASoC: dapm: Fix widget double free with auto-disable DAPM kcontrol Jarkko Nikula
2014-04-15 18:15 ` Lars-Peter Clausen [this message]
2014-04-18 17:08 ` Mark Brown

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=534D7751.7030609@metafoo.de \
    --to=lars@metafoo.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=jarkko.nikula@linux.intel.com \
    --cc=lgirdwood@gmail.com \
    --cc=stable@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