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 v32 09/20] ALSA: virtio: bound PCM transfers and retain DMA buffers
Date: Fri, 13 Nov 2026 07:11:22 +0000 [thread overview]
Message-ID: <sashiko-outbox-212326@kernel.org> (raw)
In-Reply-To: <20261113-fix-virtio-snd-recovery-final-v32-9-4e95979e312c@gmail.com>
> From: Joonho Lee <mynameisjune111@gmail.com>
>
> Validate ACK geometry, conversion bounds and queued-byte accounting
> before submitting transfers. Retain the backing DMA pages until message
> retirement. Check RX status and upper payload bounds while accepting
> bounded short responses, including at STOP and PAUSE. Preserve the
> legacy RX completion and ACK policy until the request-owned conversion,
> including the legacy handling of empty PAUSE returns. The fixed-offset
> layout still has short-response data gaps; request-owned capture and its
> queue/accounting contract arrive together in patch 12. Non-MMU copies
> use only the validated returned payload length.
>
> Fixes: f40a28679e0b ("ALSA: virtio: handling control and I/O messages for the PCM device")
> 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/20261113-fix-virtio-snd-recovery-final-v32-0-4e95979e312c@gmail.com?part=9
next prev parent reply other threads:[~2026-11-13 7:11 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 6:41 [PATCH v32 00/20] ALSA: virtio: preserve PCM progress Joonho Lee via B4 Relay
2026-11-13 6:41 ` Joonho Lee
2026-11-13 6:41 ` [PATCH v32 01/20] ALSA: pcm: mark stop-threshold accesses for capture policy sampling Joonho Lee via B4 Relay
2026-11-13 6:41 ` Joonho Lee
2026-11-13 6:46 ` sashiko-bot
2026-11-13 6:41 ` [PATCH v32 02/20] ALSA: pcm: report partial progress under the stream lock Joonho Lee via B4 Relay
2026-11-13 6:41 ` Joonho Lee
2026-11-13 7:05 ` sashiko-bot
2026-11-13 6:41 ` [PATCH v32 03/20] ALSA: pcm: add an optional reset operation " Joonho Lee via B4 Relay
2026-11-13 6:41 ` Joonho Lee
2026-11-13 6:51 ` sashiko-bot
2026-11-13 6:41 ` [PATCH v32 04/20] ALSA: pcm: notify drivers after linked prepare completes Joonho Lee via B4 Relay
2026-11-13 6:41 ` Joonho Lee
2026-11-13 6:53 ` sashiko-bot
2026-11-13 6:41 ` [PATCH v32 05/20] ALSA: pcm: serialize linked buffer actions Joonho Lee via B4 Relay
2026-11-13 6:41 ` Joonho Lee
2026-11-13 6:51 ` sashiko-bot
2026-11-13 6:41 ` [PATCH v32 06/20] ALSA: virtio: propagate playback send failures through ACK Joonho Lee via B4 Relay
2026-11-13 6:41 ` Joonho Lee
2026-11-13 7:08 ` sashiko-bot
2026-11-13 6:41 ` [PATCH v32 07/20] ALSA: virtio: Recover PCM state after a failed start Joonho Lee via B4 Relay
2026-11-13 6:41 ` Joonho Lee
2026-11-13 7:08 ` sashiko-bot
2026-11-13 6:41 ` [PATCH v32 08/20] ALSA: virtio: Retain queued messages through device reset Joonho Lee via B4 Relay
2026-11-13 6:41 ` Joonho Lee
2026-11-13 7:01 ` sashiko-bot
2026-11-13 6:41 ` [PATCH v32 09/20] ALSA: virtio: bound PCM transfers and retain DMA buffers Joonho Lee via B4 Relay
2026-11-13 6:41 ` Joonho Lee
2026-11-13 7:11 ` sashiko-bot [this message]
2026-11-13 6:41 ` [PATCH v32 10/20] ALSA: virtio: Keep control payloads alive through DMA completion Joonho Lee via B4 Relay
2026-11-13 6:41 ` Joonho Lee
2026-11-13 6:50 ` sashiko-bot
2026-11-13 6:41 ` [PATCH v32 11/20] ALSA: virtio: wait through signals for PCM teardown Joonho Lee via B4 Relay
2026-11-13 6:41 ` Joonho Lee
2026-11-13 6:58 ` sashiko-bot
2026-11-13 6:41 ` [PATCH v32 12/20] ALSA: virtio: use request-owned capture and serialize recovery Joonho Lee via B4 Relay
2026-11-13 6:41 ` Joonho Lee
2026-11-13 7:10 ` sashiko-bot
2026-11-13 6:41 ` [PATCH v32 13/20] ALSA: virtio: prioritize capture period work Joonho Lee via B4 Relay
2026-11-13 6:41 ` Joonho Lee
2026-11-13 6:50 ` sashiko-bot
2026-11-13 6:41 ` [PATCH v32 14/20] docs: describe virtio-sound capture options Joonho Lee via B4 Relay
2026-11-13 6:41 ` Joonho Lee
2026-11-13 6:52 ` sashiko-bot
2026-11-13 6:41 ` [PATCH v32 15/20] ALSA: virtio: reject invalid playback completions Joonho Lee via B4 Relay
2026-11-13 6:41 ` Joonho Lee
2026-11-13 6:59 ` sashiko-bot
2026-11-13 6:42 ` [PATCH v32 16/20] ALSA: pcm: add an explicit application pointer to indirect playback transfer Joonho Lee via B4 Relay
2026-11-13 6:42 ` Joonho Lee
2026-11-13 6:54 ` sashiko-bot
2026-11-13 6:42 ` [PATCH v32 17/20] ALSA: virtio: preserve playback progress across pause and buffer access Joonho Lee via B4 Relay
2026-11-13 6:42 ` Joonho Lee
2026-11-13 7:08 ` sashiko-bot
2026-11-13 6:42 ` [PATCH v32 18/20] ALSA: virtio: settle PCM control state from late replies Joonho Lee via B4 Relay
2026-11-13 6:42 ` Joonho Lee
2026-11-13 7:26 ` sashiko-bot
2026-11-13 6:42 ` [PATCH v32 19/20] ALSA: pcm: allow stream suspension without power management Joonho Lee via B4 Relay
2026-11-13 6:42 ` Joonho Lee
2026-11-13 6:58 ` sashiko-bot
2026-11-13 6:42 ` [PATCH v32 20/20] ALSA: virtio: reset the device when PCM state stays unknown Joonho Lee via B4 Relay
2026-11-13 6:42 ` Joonho Lee
2026-11-13 7:30 ` 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-212326@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.