public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Ivan Orlov <ivan.orlov0322@gmail.com>
Cc: tiwai@suse.com, perex@perex.cz, linux-sound@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ALSA: pcmtest: stop timer in the hw_free callback
Date: Wed, 06 Dec 2023 17:59:54 +0100	[thread overview]
Message-ID: <871qbz2rn9.wl-tiwai@suse.de> (raw)
In-Reply-To: <20231206151046.25773-1-ivan.orlov0322@gmail.com>

On Wed, 06 Dec 2023 16:10:46 +0100,
Ivan Orlov wrote:
> 
> Stop timer in the 'hw_free' callback instead of the 'close' callback
> since we want the timer to be stopped before the DMA buffer is released.
> Otherwise, it could trigger a kernel panic in some circumstances, for
> instance when the DMA buffer is already released but the timer callback
> is still running.

You can't call timer_shutdown_sync() at hw_free.  The PCM stream is
still there and you can re-setup via hw_params without closing.  But,
after timer_shutdown_sync(), the timer instance must not be used any
longer.

A more proper way would be to call timer_delete() (no sync) at trigger
STOP, then call timer_delete_sync() at sync_stop op in addition.  This
assures the immediate stop and the sync before changing to another PCM
state.

timer_shutdown_sync() can be kept at the close op to be sure.


thanks,

Takashi

> 
> Signed-off-by: Ivan Orlov <ivan.orlov0322@gmail.com>
> ---
> V1 -> V2:
> - Remove useless NULLing of v_iter->substream. It will be released in
> 'close' callback.
> 
>  sound/drivers/pcmtest.c | 6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/sound/drivers/pcmtest.c b/sound/drivers/pcmtest.c
> index b59b78a09224..8a78fa56106f 100644
> --- a/sound/drivers/pcmtest.c
> +++ b/sound/drivers/pcmtest.c
> @@ -396,8 +396,6 @@ static int snd_pcmtst_pcm_close(struct snd_pcm_substream *substream)
>  {
>  	struct pcmtst_buf_iter *v_iter = substream->runtime->private_data;
>  
> -	timer_shutdown_sync(&v_iter->timer_instance);
> -	v_iter->substream = NULL;
>  	playback_capture_test = !v_iter->is_buf_corrupted;
>  	kfree(v_iter);
>  	return 0;
> @@ -499,6 +497,10 @@ static int snd_pcmtst_pcm_hw_params(struct snd_pcm_substream *substream,
>  
>  static int snd_pcmtst_pcm_hw_free(struct snd_pcm_substream *substream)
>  {
> +	struct pcmtst_buf_iter *v_iter = substream->runtime->private_data;
> +
> +	timer_shutdown_sync(&v_iter->timer_instance);
> +
>  	return 0;
>  }
>  
> -- 
> 2.34.1
> 

  reply	other threads:[~2023-12-06 17:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-06 15:10 [PATCH v2] ALSA: pcmtest: stop timer in the hw_free callback Ivan Orlov
2023-12-06 16:59 ` Takashi Iwai [this message]
2023-12-06 20:03   ` Ivan Orlov

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=871qbz2rn9.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=ivan.orlov0322@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.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