From: "Cássio Gabriel Monteiro Pires" <cassiogabrielcontato@gmail.com>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>
Cc: linux-sound@vger.kernel.org
Subject: Re: [PATCH] ALSA: firewire-tascam: Do not drop unread control events
Date: Sun, 3 May 2026 21:37:39 -0300 [thread overview]
Message-ID: <4435a0cf-8c3c-4b2b-baca-a980598abb9b@gmail.com> (raw)
In-Reply-To: <20260503112911.GA351328@sakamocchi.jp>
[-- Attachment #1.1: Type: text/plain, Size: 2227 bytes --]
On 5/3/26 08:29, Takashi Sakamoto wrote:
> Hi,
>
> On Fri, May 01, 2026 at 03:22:58PM -0300, Cássio Gabriel wrote:
>> tscm_hwdep_read_queue() copies as many queued control events as fit in
>> the userspace buffer. When the buffer is smaller than the current
>> contiguous queue segment, length is rounded down to the number of bytes
>> that can be copied.
>>
>> However, after copying that shortened length, the code advances pull_pos
>> to tail_pos, marking the whole contiguous segment as consumed. Any events
>> between the copied portion and tail_pos are lost.
>>
>> Advance pull_pos by the number of entries actually copied instead. When
>> the whole segment fits, this is equivalent to the old tail_pos update;
>> when the buffer is smaller, the remaining events stay queued for the next
>> read.
>>
>> Fixes: a8c0d13267a4 ("ALSA: firewire-tascam: notify events of change of state for userspace applications")
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Cássio Gabriel <cassiogabrielcontato@gmail.com>
>> ---
>> sound/firewire/tascam/tascam-hwdep.c | 4 +++-
>> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> Thank you for catching the issue.
>
> I agree that this is indeed a bug. While your approach makes sense, I
> wonder if it could be simplified by updating tail_pos instead.
>
> Would you mind trying the following change?
>
> ======== 8< --------
> diff --git a/sound/firewire/tascam/tascam-hwdep.c b/sound/firewire/tascam/tascam-hwdep.c
> index 867b4ea1096e..6270263e7bf4 100644
> --- a/sound/firewire/tascam/tascam-hwdep.c
> +++ b/sound/firewire/tascam/tascam-hwdep.c
> @@ -73,6 +73,7 @@ static long tscm_hwdep_read_queue(struct snd_tscm *tscm, char __user *buf,
> length = rounddown(remained, sizeof(*entries));
> if (length == 0)
> break;
> + tail_pos = head_pos + length / sizeof(*entries);
>
> spin_unlock_irq(&tscm->lock);
> if (copy_to_user(pos, &entries[head_pos], length))
> ======== 8< --------
>
>
> Thanks
>
> Takashi Sakamoto
Hi,
Thank you for the suggestion.
I'll send a v2 patch.
--
Thanks,
Cássio
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
prev parent reply other threads:[~2026-05-04 0:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-01 18:22 [PATCH] ALSA: firewire-tascam: Do not drop unread control events Cássio Gabriel
2026-05-03 11:29 ` Takashi Sakamoto
2026-05-04 0:37 ` Cássio Gabriel Monteiro Pires [this message]
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=4435a0cf-8c3c-4b2b-baca-a980598abb9b@gmail.com \
--to=cassiogabrielcontato@gmail.com \
--cc=linux-sound@vger.kernel.org \
--cc=o-takashi@sakamocchi.jp \
/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