mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Cen Zhang <zzzccc427@gmail.com>
Cc: perex@perex.cz, tiwai@suse.com, linux-sound@vger.kernel.org,
	linux-kernel@vger.kernel.org, baijiaju1990@gmail.com,
	jjzuming@gmail.com
Subject: Re: [PATCH] ALSA: pcm: Remove channel-map controls before freeing substreams
Date: Mon, 19 Oct 2026 16:24:21 +0200	[thread overview]
Message-ID: <874iehahuy.wl-tiwai@suse.de> (raw)
In-Reply-To: <pm-pmb-4a207d9ef3a3597a74a4-v4-80b0113669b1a62fbbe9@gmail.com>

On Mon, 19 Oct 2026 12:01:46 +0200,
Cen Zhang wrote:
> 
> A late HDA codec bind on an already registered card builds new PCMs
> before registering them. add_std_chmaps() publishes generic channel-map
> controls during this BUILD stage. If an earlier chmap succeeds and a
> later allocation fails, probe cleanup frees the BUILD PCM while the
> card's control device remains accessible.
> 
> These generic controls are added directly by snd_pcm_add_chmap_ctls();
> snd_hda_ctls_clear() only removes codec-tracked mixer controls. BUILD
> devices also skip dev_disconnect. snd_pcm_free_stream() then frees the
> substreams before free_chmap() withdraws their generic control:
> 
>   Late HDA codec bind / rollback        Control GET on the live card
>   ------------------------------       ----------------------------
>   hda_codec_driver_probe()
>     snd_hda_codec_build_pcms()
>       PCM is BUILD
>     snd_hda_codec_build_controls()
>       add_std_chmaps()
>         publish an earlier chmap
>         later allocation: -ENOMEM
>     snd_hda_codec_cleanup_for_unbind()
>       snd_hda_ctls_clear()
>         generic chmap remains
>       codec_release_pcms()
>         snd_device_free()
>           BUILD: skip dev_disconnect
>           snd_pcm_free_stream()
>             kfree(substream)
>                                        snd_ctl_elem_read()
>                                          down_read(controls_rwsem)
>                                          pcm_chmap_ctl_get()
>                                            walk freed substream
>             free_chmap()
>               snd_ctl_remove()
>                 wait for GET
>                                          up_read(controls_rwsem)
> 
> The control read lock cannot protect a substream already freed before
> control removal starts. The failure above occurs before
> snd_card_register(), so the PCM has not transitioned out of BUILD.
> 
> Move free_chmap() before the substream free loop. Its snd_ctl_remove()
> withdraws the control and drains readers under controls_rwsem before any
> substream is released. Normal registered-device disconnect already
> removes the control, so the later call remains harmless on that path.
> 
> Fixes: 2d3391ec0ecc ("ALSA: PCM: channel mapping API implementation")
> Assisted-by: LLM
> Signed-off-by: Cen Zhang <zzzccc427@gmail.com>

Applied now.  Thanks.


Takashi

      reply	other threads:[~2026-10-19 14:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-19 10:01 Cen Zhang
2026-10-19 14:24 ` Takashi Iwai [this message]

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=874iehahuy.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=baijiaju1990@gmail.com \
    --cc=jjzuming@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.com \
    --cc=zzzccc427@gmail.com \
    /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

all inboxes | Powered by JetHome®