From: Takashi Iwai <tiwai@suse.de>
To: Li Jun <lijun01@kylinos.cn>
Cc: lgirdwood@gmail.com, broonie@kernel.org, perex@perex.cz,
tiwai@suse.com, linux-sound@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: loongson: Fix invalid position error in ls_pcm_pointer
Date: Fri, 29 May 2026 11:01:29 +0200 [thread overview]
Message-ID: <87zf1ir3me.wl-tiwai@suse.de> (raw)
In-Reply-To: <20260529024830.3078886-1-lijun01@kylinos.cn>
On Fri, 29 May 2026 04:48:30 +0200,
Li Jun wrote:
>
> The "invalid position" error occurred when the DMA position descriptor
> returned an invalid address value (e.g., pos = -1048838144). This happened
> because the `bytes_to_frames()` function returns a signed value, but when
> `addr < runtime->dma_addr`, the subtraction produces a negative result that
> gets interpreted as a large unsigned integer in comparisons.
>
> [ 32.834431][ 2] soc-audio soc-audio: invalid position: , pos = -1048838144
> [ 32.845019][ 2] soc-audio soc-audio: invalid position: , pos = -1048838144
> [ 32.855588][ 2] soc-audio soc-audio: invalid position: , pos = -1048838144
> [ 32.866145][ 2] soc-audio soc-audio: invalid position: , pos = -1048838144
> [ 32.995394][ 2] soc-audio soc-audio: invalid position: , pos = -1048838144
> [ 33.006025][ 2] soc-audio soc-audio: invalid position: , pos = -1048838144
> [ 33.016748][ 2] soc-audio soc-audio: invalid position: , pos = -1048838144
>
> Signed-off-by: Li Jun <lijun01@kylinos.cn>
Since it's a change for ASoC, use "ASoC" prefix for the subject line.
About the code change: how does this negative position come? Is it an
utterly bogus value to be ignored, or is it a position overlap or
such? Your change seems just ignoring and returning 0, and if it's a
spontaneous bogus value, it may lead to an unexpected jump of the PCM
position, too, for example.
thanks,
Takashi
> ---
> sound/soc/loongson/loongson_dma.c | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/sound/soc/loongson/loongson_dma.c b/sound/soc/loongson/loongson_dma.c
> index a149b643175c..f0a7065ddae7 100644
> --- a/sound/soc/loongson/loongson_dma.c
> +++ b/sound/soc/loongson/loongson_dma.c
> @@ -207,9 +207,15 @@ loongson_pcm_pointer(struct snd_soc_component *component,
> desc = dma_desc_save(prtd);
> addr = ((u64)desc->saddr_hi << 32) | desc->saddr;
>
> - x = bytes_to_frames(runtime, addr - runtime->dma_addr);
> - if (x == runtime->buffer_size)
> + if (addr < runtime->dma_addr ||
> + addr >= runtime->dma_addr + runtime->dma_bytes) {
> x = 0;
> + } else {
> + x = bytes_to_frames(runtime, addr - runtime->dma_addr);
> + if (x >= runtime->buffer_size)
> + x = 0;
> + }
> +
> return x;
> }
>
> --
> 2.25.1
>
next prev parent reply other threads:[~2026-05-29 9:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 2:48 Li Jun
2026-05-29 9:01 ` Takashi Iwai [this message]
2026-05-29 13:23 ` lijun
2026-05-29 14:04 ` Takashi Iwai
2026-06-01 1:27 ` lijun
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=87zf1ir3me.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=lijun01@kylinos.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
/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
all inboxes | Powered by JetHome®