ASoC: core: Exit all links before removing their components
PATCH 1/1 ASoC: core: Exit all links before removing their components
Flows leading to link->init() and link->exit() are not symmetric. Currently the relevant part of card probe sequence goes as:
for_each_card_rtds(card, rtd) for_each_rtd_components(rtd, i, component) component->probe() for_each_card_rtds(card, rtd) for_each_rtd_dais(rtd, i, dai) dai->probe() for_each_card_rtds(card, rtd) rtd->init()
On the other side, equivalent remove sequence goes as:
for_each_card_rtds(card, rtd) for_each_rtd_dais(rtd, i, dai) dai->remove() for_each_card_rtds(card, rtd) for_each_rtd_components(rtd, i, component) component->remove() for_each_card_rtds(card, rtd) rtd->exit()
what can lead to errors as link->exit() may still operate on resources owned by its components despite the probability of them being freed during the component->remove().
This change modifies the remove sequence to:
for_each_card_rtds(card, rtd) rtd->exit() for_each_card_rtds(card, rtd) for_each_rtd_dais(rtd, i, dai) dai->remove() for_each_card_rtds(card, rtd) for_each_rtd_components(rtd, i, component) component->remove()
so code found in link->exit() is safe to touch any component stuff as component->remove() has not been called yet.
--- sound/soc/soc-core.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
sound/soc/soc-core.c +3 -3
@@ -935,9 +935,6 @@ void snd_soc_remove_pcm_runtime(struct snd_soc_card *card, {lockdep_assert_held (&client_mutex); -/* release machine specific resources */ -snd_soc_link_exit (rtd); -/* * Notify the machine driver for extra destruction */
@@ -1888,6 +1885,9 @@ static void soc_cleanup_card_resources(struct snd_soc_card *card)snd_soc_dapm_shutdown (card); +/* release machine specific resources */ +for_each_card_rtds (card, rtd) +snd_soc_link_exit (rtd);/* remove and free each DAI */ soc_remove_link_dais (card);soc_remove_link_components (card);
Signature · 1 line
2.25.1
Quoted 38 lines · Cezary Rojewski
Flows leading to
link->init()andlink->exit()are not symmetric. Currently the relevant part of card probe sequence goes as:for_each_card_rtds(card, rtd) for_each_rtd_components(rtd, i, component) component->probe() for_each_card_rtds(card, rtd) for_each_rtd_dais(rtd, i, dai) dai->probe() for_each_card_rtds(card, rtd) rtd->init()On the other side, equivalent remove sequence goes as:
for_each_card_rtds(card, rtd) for_each_rtd_dais(rtd, i, dai) dai->remove() for_each_card_rtds(card, rtd) for_each_rtd_components(rtd, i, component) component->remove() for_each_card_rtds(card, rtd) rtd->exit()what can lead to errors as
link->exit()may still operate on resources owned by its components despite the probability of them being freed during thecomponent->remove().This change modifies the remove sequence to:
for_each_card_rtds(card, rtd) rtd->exit() for_each_card_rtds(card, rtd) for_each_rtd_dais(rtd, i, dai) dai->remove() for_each_card_rtds(card, rtd) for_each_rtd_components(rtd, i, component) component->remove()
Quoted 2 lines
so code found in
link->exit()is safe to touch any component stuff ascomponent->remove()has not been called yet.
This looks harmless as described, but...
Quoted 12 lines
Signed-off-by Cezary Rojewski <[email protected]>Reviewed-by Amadeusz Sławiński <[email protected]>--- sound/soc/soc-core.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)sound/soc/soc-core.c +0
-0
sound/soc/soc-core.c void snd_soc_remove_pcm_runtime(struct snd_soc_card *card, · line 940
Quoted 9 lines
sound/soc/soc-core.c +0
-3@@ -935,9 +935,6 @@ void snd_soc_remove_pcm_runtime(struct snd_soc_card *card, {lockdep_assert_held (&client_mutex); -/* release machine specific resources */ -snd_soc_link_exit (rtd); -/* * Notify the machine driver for extra destruction */
.... what is not shown here is the
soc_free_pcm_runtime(rtd);
which will call device_unregister(rtd->dev);
....
sound/soc/soc-core.c static void soc_cleanup_card_resources(struct snd_soc_card *card) · line 1890
Quoted 7 lines
sound/soc/soc-core.c +3
-0@@ -1888,6 +1885,9 @@ static void soc_cleanup_card_resources(struct snd_soc_card *card)snd_soc_dapm_shutdown (card); +/* release machine specific resources */ +for_each_card_rtds (card, rtd) +snd_soc_link_exit (rtd);
... so there's still a risk that the link exit refers to memory that's been released already.
We would need to make sure rtd->dev is not used in any of the existing callbacks - or other functions such as e.g. snd_soc_close_delayed_work() which makes use of rtd->dev
Quoted 3 lines
sound/soc/soc-core.c +0
-0/* remove and free each DAI */ soc_remove_link_dais (card);soc_remove_link_components (card);
Quoted 36 lines · Pierre-Louis Bossart
Quoted 5 lines · Cezary Rojewski
sound/soc/soc-core.c +0
-0sound/soc/soc-core.c void snd_soc_remove_pcm_runtime(struct snd_soc_card *card, · line 940
Quoted 9 lines
sound/soc/soc-core.c +0
-3@@ -935,9 +935,6 @@ void snd_soc_remove_pcm_runtime(struct snd_soc_card *card, {lockdep_assert_held (&client_mutex); -/* release machine specific resources */ -snd_soc_link_exit (rtd); -/* * Notify the machine driver for extra destruction */ .... what is not shown here is the
soc_free_pcm_runtime(rtd);which will call
device_unregister(rtd->dev);....
sound/soc/soc-core.c static void soc_cleanup_card_resources(struct snd_soc_card *card) · line 1890
Quoted 7 lines
sound/soc/soc-core.c +3
-0@@ -1888,6 +1885,9 @@ static void soc_cleanup_card_resources(struct snd_soc_card *card)snd_soc_dapm_shutdown (card); +/* release machine specific resources */ +for_each_card_rtds (card, rtd) +snd_soc_link_exit (rtd);... so there's still a risk that the link exit refers to memory that's been released already.
Quoted 4 lines
We would need to make sure
rtd->devis not used in any of the existing callbacks - or other functions such as e.g.snd_soc_close_delayed_work()which makes use ofrtd->dev
The lack of soc_free_pcm_runtime() included here is done on purpose. After revisiting probe and remove flows it seems that there are more de-synchronization than just link->init() and link->exit(). However, I believe providing incremental changes is better than providing one single big patch which has much larger impact of the framework. Moving just the snd_soc_link_exit() has very limited impact.
In regard to the flow, we have to remember that 'someone' has to be the first one, 'someone' has to be the last one too. If the probe flow ends with link->init() (for the selected range of functions), then it feels natural for remove flow to begin with link->exit().
I've scanned the repo for usages of link->exit() and it seems only Intel platforms do so. Given their (functions) current content, status quo is achieved. AVS and CATPT drivers reload-tests show no regression too. The DAPM-pin warning I'd mentioned earlier in the bdw_rt286 discussion is also gone.
Regards,
Czarek
Quoted 41 lines · Cezary Rojewski
Quoted 35 lines · Pierre-Louis Bossart
Quoted 5 lines · Cezary Rojewski
sound/soc/soc-core.c +0
-0sound/soc/soc-core.c void snd_soc_remove_pcm_runtime(struct · line 940
Quoted 9 lines
sound/soc/soc-core.c +0
-3@@ -935,9 +935,6 @@ void snd_soc_remove_pcm_runtime(structsnd_soc_card *card, { lockdep_assert_held(&client_mutex); - /* release machine specific resources */ - snd_soc_link_exit(rtd); - /** Notify the machine driver for extra destruction */ .... what is not shown here is the
soc_free_pcm_runtime(rtd);
which will call
device_unregister(rtd->dev);....
sound/soc/soc-core.c static void soc_cleanup_card_resources(struct · line 1889
Quoted 6 lines
sound/soc/soc-core.c +3
-0@@ -1888,6 +1885,9 @@ static void soc_cleanup_card_resources(struct snd_soc_card *card) snd_soc_dapm_shutdown(card); + /* release machine specific resources */ + for_each_card_rtds(card, rtd) + snd_soc_link_exit(rtd);... so there's still a risk that the link exit refers to memory that's been released already.
Quoted 4 lines
We would need to make sure
rtd->devis not used in any of the existing callbacks - or other functions such as e.g.snd_soc_close_delayed_work()which makes use ofrtd->dev
Quoted 5 lines
The lack of
soc_free_pcm_runtime()included here is done on purpose. After revisiting probe and remove flows it seems that there are more de-synchronization than justlink->init()andlink->exit(). However, I believe providing incremental changes is better than providing one single big patch which has much larger impact of the framework. Moving just thesnd_soc_link_exit()has very limited impact.In regard to the flow, we have to remember that 'someone' has to be the first one, 'someone' has to be the last one too. If the probe flow ends with
link->init()(for the selected range of functions), then it feels natural for remove flow to begin withlink->exit().I've scanned the repo for usages of
link->exit()and it seems only Intel platforms do so. Given their (functions) current content, status quo is achieved. AVS and CATPT drivers reload-tests show no regression too. The DAPM-pin warning I'd mentioned earlier in thebdw_rt286discussion is also gone.
Hello,
Are there any questions left unanswered here? This patch is a dependency for jack handling changes for avs/catpt machine boards.
Regards,
Czarek