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 v12 03/12] ALSA: virtio: Retain queued messages through device reset
Date: Tue, 03 Nov 2026 00:40:05 +0000 [thread overview]
Message-ID: <sashiko-outbox-194385@kernel.org> (raw)
In-Reply-To: <20261103000403.67106-4-mynameisjune111@gmail.com>
> Keep the control queue available through snd_card_free() so close-time
> STOP and RELEASE commands can still be submitted. Block new control
> requests and mark pending messages canceled before reset, then release
> their queue references only after reset and queue deletion.
>
> For PCM queues, detach each remaining virtqueue buffer after the device
> has stopped DMA and retire its message without reporting a normal
> completion. Detach all queues before deleting them so outstanding DMA
> mappings are unmapped and no token remains for a late device completion.
>
> Clear each queue wrapper inside the same critical section that detaches
> its buffers. Check the callback's queue identity under the wrapper lock
> for PCM, control and event queues. This makes queue retirement explicit
> through teardown and restore. A forced callback test passed on both
> versions; the proposed detached-ring IRQ failure was not reproduced on
> the tested PCI transport.
>
> Fixes: 9d45e514da88 ("ALSA: virtio: handling control messages")
> Assisted-by: LLM
> Signed-off-by: Joonho Lee <mynameisjune111@gmail.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261103000403.67106-1-mynameisjune111@gmail.com?part=3
next prev parent reply other threads:[~2026-11-03 0:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 0:03 [PATCH v12 00/12] ALSA: virtio: staged capture recovery and PCM RESET synchronization Joonho Lee
2026-11-03 0:03 ` [PATCH v12 01/12] ALSA: virtio: Propagate PCM send failures through ACK Joonho Lee
2026-11-03 0:31 ` sashiko-bot
2026-11-03 0:03 ` [PATCH v12 02/12] ALSA: virtio: Recover PCM state after a failed start Joonho Lee
2026-11-03 0:26 ` sashiko-bot
2026-11-03 0:03 ` [PATCH v12 03/12] ALSA: virtio: Retain queued messages through device reset Joonho Lee
2026-11-03 0:40 ` sashiko-bot [this message]
2026-11-03 0:03 ` [PATCH v12 04/12] ALSA: virtio: Keep PCM DMA buffers alive through device ownership Joonho Lee
2026-11-03 0:25 ` sashiko-bot
2026-11-03 0:03 ` [PATCH v12 05/12] ALSA: virtio: Keep control payloads alive through DMA completion Joonho Lee
2026-11-03 0:12 ` sashiko-bot
2026-11-03 0:03 ` [PATCH v12 06/12] ALSA: virtio: wait through signals for PCM teardown Joonho Lee
2026-11-03 0:24 ` sashiko-bot
2026-11-03 0:03 ` [PATCH v12 07/12] ALSA: pcm: mark stop-threshold accesses for capture policy sampling Joonho Lee
2026-11-03 0:09 ` sashiko-bot
2026-11-03 0:03 ` [PATCH v12 08/12] ALSA: pcm: report partial progress under the stream lock Joonho Lee
2026-11-03 0:09 ` sashiko-bot
2026-11-03 0:04 ` [PATCH v12 09/12] ALSA: pcm: add an optional reset operation " Joonho Lee
2026-11-03 0:13 ` sashiko-bot
2026-11-03 0:04 ` [PATCH v12 10/12] ALSA: virtio: add staged capture and serialize PCM lifecycle accounting Joonho Lee
2026-11-03 0:50 ` sashiko-bot
2026-11-03 0:04 ` [PATCH v12 11/12] ALSA: virtio: prioritize staged capture period work Joonho Lee
2026-11-03 0:15 ` sashiko-bot
2026-11-03 0:04 ` [PATCH v12 12/12] docs: describe virtio-sound capture options Joonho Lee
2026-11-03 0:17 ` sashiko-bot
2026-11-03 0:55 ` Randy Dunlap
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-194385@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.