Linux virtualization list
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Joonho Lee" <mynameisjune111@gmail.com>
Cc: virtualization@lists.linux.dev,
	"Michael S. Tsirkin" <mst@redhat.com>,
	"Eugenio Perez" <eperezma@redhat.com>
Subject: Re: [PATCH v20 05/12] ALSA: virtio: Recover PCM state after a failed start
Date: Sat, 07 Nov 2026 15:01:00 +0000	[thread overview]
Message-ID: <sashiko-outbox-202977@kernel.org> (raw)
In-Reply-To: <20261107143422.29319-6-mynameisjune111@gmail.com>

> Capture trigger queues I/O messages before PCM_START. If the START
> message cannot be allocated or sent, transfers may remain queued, and
> ALSA does not invoke the action undo callback for the failed trigger.
> 
> Mark the stream stopped and disable transfers for every failed START
> path. Arm runtime->stop_operating so sync_stop releases pending I/O and
> prevents prepare, hw_params, or START retries until release succeeds.
> 
> The stopped flag is shared with ACK callbacks that can run without the
> ALSA stream lock. Protect every stopped access with vss->lock. Read the
> pending message count under the same lock in open and hw_params. In
> sync_stop, decide whether RELEASE is needed and mark the stream stopped
> in one locked transition; leave it stopped when release or draining
> fails.
> 
> Always cancel elapsed-period work in sync_stop, even when no RELEASE is
> needed.
> 
> Record the RELEASE obligation after successful PREPARE and clear it as
> soon as RELEASE succeeds. If the subsequent RX wait fails, retry that
> wait without submitting RELEASE again.
> 
> Fixes: da76e9f3e43a ("ALSA: virtio: PCM substream operators")
> Signed-off-by: Joonho Lee <mynameisjune111@gmail.com>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261107143422.29319-1-mynameisjune111@gmail.com?part=5


  reply	other threads:[~2026-11-07 15:01 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-07 14:34 [PATCH v20 00/12] ALSA: virtio: fix capture accounting Joonho Lee
2026-11-07 14:34 ` [PATCH v20 01/12] ALSA: pcm: mark stop-threshold accesses for capture policy sampling Joonho Lee
2026-11-07 14:39   ` sashiko-bot
2026-11-07 14:34 ` [PATCH v20 02/12] ALSA: pcm: report partial progress under the stream lock Joonho Lee
2026-11-07 14:39   ` sashiko-bot
2026-11-07 14:34 ` [PATCH v20 03/12] ALSA: pcm: add an optional reset operation " Joonho Lee
2026-11-07 14:45   ` sashiko-bot
2026-11-07 14:34 ` [PATCH v20 04/12] ALSA: virtio: Propagate PCM send failures through ACK Joonho Lee
2026-11-07 15:06   ` sashiko-bot
2026-11-07 14:34 ` [PATCH v20 05/12] ALSA: virtio: Recover PCM state after a failed start Joonho Lee
2026-11-07 15:01   ` sashiko-bot [this message]
2026-11-07 14:34 ` [PATCH v20 06/12] ALSA: virtio: Retain queued messages through device reset Joonho Lee
2026-11-07 14:53   ` sashiko-bot
2026-11-07 14:34 ` [PATCH v20 07/12] ALSA: virtio: validate indirect capture appl_ptr accounting Joonho Lee
2026-11-07 15:11   ` sashiko-bot
2026-11-07 14:34 ` [PATCH v20 08/12] ALSA: virtio: Keep control payloads alive through DMA completion Joonho Lee
2026-11-07 14:45   ` sashiko-bot
2026-11-07 14:34 ` [PATCH v20 09/12] ALSA: virtio: wait through signals for PCM teardown Joonho Lee
2026-11-07 14:53   ` sashiko-bot
2026-11-07 14:34 ` [PATCH v20 10/12] ALSA: virtio: serialize staged capture lifecycle and defer paused XRUNs Joonho Lee
2026-11-07 15:06   ` sashiko-bot
2026-11-07 14:34 ` [PATCH v20 11/12] ALSA: virtio: prioritize staged capture period work Joonho Lee
2026-11-07 14:53   ` sashiko-bot
2026-11-07 14:34 ` [PATCH v20 12/12] docs: describe virtio-sound capture options Joonho Lee
2026-11-07 14:47   ` sashiko-bot

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=sashiko-outbox-202977@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=eperezma@redhat.com \
    --cc=mst@redhat.com \
    --cc=mynameisjune111@gmail.com \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=virtualization@lists.linux.dev \
    /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