All of lore.kernel.org
 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 v18 04/12] ALSA: virtio: Propagate PCM send failures through ACK
Date: Fri, 06 Nov 2026 00:35:52 +0000	[thread overview]
Message-ID: <sashiko-outbox-200450@kernel.org> (raw)
In-Reply-To: <20261106000644.20460-5-mynameisjune111@gmail.com>

> virtsnd_pcm_msg_send() can fail while queueing a transfer. Restore the
> failed message's length and notify the device about earlier messages
> queued by the same call, so they do not remain stranded.
> 
> Propagate errors through the indirect transfer callback and commit its
> private cursor only after successful submission. Genuine transfer errors
> arm stop_operating and return -EPIPE so ALSA can retire the stream.
> 
> Close ACK admission under the PCM stream lock before sleeping teardown.
> Keep the prepared state protected by the substream lock and reject ACK
> through prepare and parameter changes. Reopen admission in the reset
> callback while the core holds the PCM lock for its pointer rebase. An
> ACK racing with teardown returns -EBADFD and preserves stop state.
> 
> Keep the polling feature path unchanged.
> 
> Fixes: fe981e67568c ("ALSA: virtio: use ack callback")
> 
> Reject a stopped playback ACK before the XRUN path can rearm
> stop_operating. For capture, allow the ordinary stopped tail only during
> DRAINING and only while no transfer XRUN is latched.
> 
> Latch a transfer failure before stopping PCM work. Once core reports the member XRUN, ACK returns -EBADFD to avoid another linked XRUN. ACK during prepare remains rejected until the core state reaches PREPARED.
> Signed-off-by: Joonho Lee <mynameisjune111@gmail.com>

Sashiko has reviewed this patch and found no issues.

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


  reply	other threads:[~2026-11-06  0:35 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-06  0:06 [PATCH v18 00/12] ALSA: virtio: fix capture lifetime and accounting Joonho Lee
2026-11-06  0:06 ` [PATCH v18 01/12] ALSA: pcm: mark stop-threshold accesses for capture policy sampling Joonho Lee
2026-11-06  0:10   ` sashiko-bot
2026-11-06  0:06 ` [PATCH v18 02/12] ALSA: pcm: report partial progress under the stream lock Joonho Lee
2026-11-06  0:11   ` sashiko-bot
2026-11-06  0:06 ` [PATCH v18 03/12] ALSA: pcm: add an optional reset operation " Joonho Lee
2026-11-06  0:14   ` sashiko-bot
2026-11-06  0:06 ` [PATCH v18 04/12] ALSA: virtio: Propagate PCM send failures through ACK Joonho Lee
2026-11-06  0:35   ` sashiko-bot [this message]
2026-11-06  0:06 ` [PATCH v18 05/12] ALSA: virtio: Recover PCM state after a failed start Joonho Lee
2026-11-06  0:26   ` sashiko-bot
2026-11-06  0:06 ` [PATCH v18 06/12] ALSA: virtio: Retain queued messages through device reset Joonho Lee
2026-11-06  0:31   ` sashiko-bot
2026-11-06  0:06 ` [PATCH v18 07/12] ALSA: virtio: retain PCM DMA pages and validate capture ring ownership Joonho Lee
2026-11-06  0:36   ` sashiko-bot
2026-11-06  0:06 ` [PATCH v18 08/12] ALSA: virtio: Keep control payloads alive through DMA completion Joonho Lee
2026-11-06  0:14   ` sashiko-bot
2026-11-06  0:06 ` [PATCH v18 09/12] ALSA: virtio: wait through signals for PCM teardown Joonho Lee
2026-11-06  0:22   ` sashiko-bot
2026-11-06  0:06 ` [PATCH v18 10/12] ALSA: virtio: serialize staged capture lifecycle and defer paused XRUNs Joonho Lee
2026-11-06  0:30   ` sashiko-bot
2026-11-06  0:06 ` [PATCH v18 11/12] ALSA: virtio: prioritize staged capture period work Joonho Lee
2026-11-06  0:20   ` sashiko-bot
2026-11-06  0:06 ` [PATCH v18 12/12] docs: describe virtio-sound capture options Joonho Lee
2026-11-06  0:17   ` 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-200450@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.