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 v17 07/12] ALSA: virtio: retain PCM DMA buffers and validate capture completions
Date: Thu, 05 Nov 2026 07:43:11 +0000	[thread overview]
Message-ID: <sashiko-outbox-198694@kernel.org> (raw)
In-Reply-To: <20261105070845.6449-8-mynameisjune111@gmail.com>

> Retain references to the pages backing ALSA's vmalloc buffer until its
> queued I/O messages are freed. On NOMMU systems, use driver-owned memory
> for DMA and copy playback data before submission and capture data after
> completion, so ALSA buffer release cannot invalidate an active request.
> 
> Validate the PCM buffer and each period before building scatterlists.
> Require a successful full-period response for ordinary capture before
> advancing its pointer. Each descriptor targets a fixed ring slice, so a
> short response would expose the unwritten remainder as captured data.
> 
> Require whole-byte periods whose total matches the negotiated buffer.
> Check offset, length and the final message index before indexing the
> message array, including empty transfers and arithmetic wraparound.
> 
> Seed the ordinary capture ring once per prepare. Native STOP preserves
> [ ... ]
> retire empty stopped completions without advancing capture state. Once
> an XRUN is latched, later completions only retire queue ownership. An
> out-of-order full completion reports XRUN rather than publishing an
> unwritten ring slice; this path does not reorder completed requests.
> Signed-off-by: Joonho Lee <mynameisjune111@gmail.com>

Sashiko has reviewed this patch and found no issues.

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


  reply	other threads:[~2026-11-05  7:43 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-05  7:08 [PATCH v17 00/12] ALSA: virtio: fix capture lifetime and accounting Joonho Lee
2026-11-05  7:08 ` [PATCH v17 01/12] ALSA: pcm: mark stop-threshold accesses for capture policy sampling Joonho Lee
2026-11-05  7:12   ` sashiko-bot
2026-11-05  7:08 ` [PATCH v17 02/12] ALSA: pcm: report partial progress under the stream lock Joonho Lee
2026-11-05  7:14   ` sashiko-bot
2026-11-05  7:08 ` [PATCH v17 03/12] ALSA: pcm: add an optional reset operation " Joonho Lee
2026-11-05  7:14   ` sashiko-bot
2026-11-05  7:08 ` [PATCH v17 04/12] ALSA: virtio: Propagate PCM send failures through ACK Joonho Lee
2026-11-05  7:37   ` sashiko-bot
2026-11-05  7:08 ` [PATCH v17 05/12] ALSA: virtio: Recover PCM state after a failed start Joonho Lee
2026-11-05  7:33   ` sashiko-bot
2026-11-05  7:08 ` [PATCH v17 06/12] ALSA: virtio: Retain queued messages through device reset Joonho Lee
2026-11-05  7:39   ` sashiko-bot
2026-11-05  7:08 ` [PATCH v17 07/12] ALSA: virtio: retain PCM DMA buffers and validate capture completions Joonho Lee
2026-11-05  7:43   ` sashiko-bot [this message]
2026-11-05  7:08 ` [PATCH v17 08/12] ALSA: virtio: Keep control payloads alive through DMA completion Joonho Lee
2026-11-05  7:19   ` sashiko-bot
2026-11-05  7:08 ` [PATCH v17 09/12] ALSA: virtio: wait through signals for PCM teardown Joonho Lee
2026-11-05  7:29   ` sashiko-bot
2026-11-05  7:08 ` [PATCH v17 10/12] ALSA: virtio: serialize staged capture lifecycle and defer paused XRUNs Joonho Lee
2026-11-05  7:41   ` sashiko-bot
2026-11-05  7:08 ` [PATCH v17 11/12] ALSA: virtio: prioritize staged capture period work Joonho Lee
2026-11-05  7:24   ` sashiko-bot
2026-11-05  7:08 ` [PATCH v17 12/12] docs: describe virtio-sound capture options Joonho Lee
2026-11-05  7:20   ` 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-198694@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.