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: [RFC PATCH 1/2] ALSA: virtio: account staged capture reads before RX refill
Date: Sat, 17 Oct 2026 06:03:53 +0000 [thread overview]
Message-ID: <sashiko-outbox-175328@kernel.org> (raw)
In-Reply-To: <rfc-virtio-snd-capture-followups-1.f2737c95c12e45b4@gmail.com>
> The RX callback holds the queue lock across a batch of completions. A
> reader that has copied samples can wait for that lock in ACK before its
> consumed bytes are removed from capture_ready. A later completion in the
> same batch can then reject data using stale ring occupancy.
>
> Account the staged read under the substream lock before acquiring the RX
> queue lock. Release that lock before taking the queue and substream locks
> in their established order to refill requests.
>
> Once accounting is committed, latch refill errors as XRUN and return
> success from ACK. A negative return would make ALSA restore appl_ptr while
> the driver retained the consumed-byte accounting. Keep pre-commit errors,
> ring-capacity checks, and normal period-work scheduling unchanged.
>
> Source-extracted host and kernel fixtures reproduce the stale-capacity
> race and post-commit ALSA pointer rollback. The candidate preserves wrapped
> data and pointer accounting. KASAN/lockdep QEMU lifecycle checks passed.
> The fixtures substitute selected backend helpers and do not independently
> establish physical-device acceptance.
>
> This follows pending staged capture support, whose introducing patch has
> no upstream commit ID for a Fixes tag yet.
>
> Link: https://lore.kernel.org/all/rfc-v2-vz-capture-compat-1.b9ab4c1540dc4691@gmail.com/
> 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/rfc-virtio-snd-capture-followups-0.f2737c95c12e45b4@gmail.com?part=1
next prev parent reply other threads:[~2026-10-17 6:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-17 6:00 [RFC PATCH 0/2] ALSA: virtio: fix staged capture ACK ordering and period scheduling Joonho Lee
2026-10-17 6:00 ` [RFC PATCH 1/2] ALSA: virtio: account staged capture reads before RX refill Joonho Lee
2026-10-17 6:03 ` sashiko-bot [this message]
2026-10-17 6:00 ` [RFC PATCH 2/2] ALSA: virtio: prioritize staged capture period work Joonho Lee
2026-10-17 6:03 ` sashiko-bot
2026-10-17 12:51 ` [RFC PATCH 0/2] ALSA: virtio: fix staged capture ACK ordering and period scheduling Joonho Lee
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-175328@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