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 v16 06/12] ALSA: virtio: Retain queued messages through device reset
Date: Thu, 05 Nov 2026 03:02:32 +0000	[thread overview]
Message-ID: <sashiko-outbox-198499@kernel.org> (raw)
In-Reply-To: <20261105023140.18373-7-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.
> 
> Protect event callback admission with the event queue lock. Disabling
> events waits for an active dispatch, and later callbacks see a closed
> gate before ALSA objects are freed. Enable and pending-event draining
> share the same lock.
> 
> Reclaim pending event buffers after a failed probe without dispatching
> notifications into ALSA objects that have not been constructed. Record
> the queue's prior enabled state under its lock before closing admission.
> 
> 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/20261105023140.18373-1-mynameisjune111@gmail.com?part=6


  reply	other threads:[~2026-11-05  3:02 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-05  2:31 [PATCH v16 00/12] ALSA: virtio: fix capture lifetime and accounting Joonho Lee
2026-11-05  2:31 ` [PATCH v16 01/12] ALSA: pcm: mark stop-threshold accesses for capture policy sampling Joonho Lee
2026-11-05  2:35   ` sashiko-bot
2026-11-05  2:31 ` [PATCH v16 02/12] ALSA: pcm: report partial progress under the stream lock Joonho Lee
2026-11-05  2:36   ` sashiko-bot
2026-11-05  2:31 ` [PATCH v16 03/12] ALSA: pcm: add an optional reset operation " Joonho Lee
2026-11-05  2:40   ` sashiko-bot
2026-11-05  2:31 ` [PATCH v16 04/12] ALSA: virtio: Propagate PCM send failures through ACK Joonho Lee
2026-11-05  3:07   ` sashiko-bot
2026-11-05  2:31 ` [PATCH v16 05/12] ALSA: virtio: Recover PCM state after a failed start Joonho Lee
2026-11-05  2:57   ` sashiko-bot
2026-11-05  2:31 ` [PATCH v16 06/12] ALSA: virtio: Retain queued messages through device reset Joonho Lee
2026-11-05  3:02   ` sashiko-bot [this message]
2026-11-05  2:31 ` [PATCH v16 07/12] ALSA: virtio: Keep PCM DMA buffers alive through device ownership Joonho Lee
2026-11-05  2:56   ` sashiko-bot
2026-11-05  2:31 ` [PATCH v16 08/12] ALSA: virtio: Keep control payloads alive through DMA completion Joonho Lee
2026-11-05  2:39   ` sashiko-bot
2026-11-05  2:31 ` [PATCH v16 09/12] ALSA: virtio: wait through signals for PCM teardown Joonho Lee
2026-11-05  2:50   ` sashiko-bot
2026-11-05  2:31 ` [PATCH v16 10/12] ALSA: virtio: add staged capture and serialize PCM lifecycle accounting Joonho Lee
2026-11-05  2:59   ` sashiko-bot
2026-11-05  2:31 ` [PATCH v16 11/12] ALSA: virtio: prioritize staged capture period work Joonho Lee
2026-11-05  2:44   ` sashiko-bot
2026-11-05  2:31 ` [PATCH v16 12/12] docs: describe virtio-sound capture options Joonho Lee
2026-11-05  2:43   ` 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-198499@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