From: Srinivas Kandagatla <srinivas.kandagatla@oss.qualcomm.com>
To: Julius Bairaktaris <julius@bairaktaris.de>,
Srinivas Kandagatla <srini@kernel.org>,
Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Vinod Koul <vkoul@kernel.org>,
Mohammad Rafi Shaik <mohammad.rafi.shaik@oss.qualcomm.com>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>,
linux-sound@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] ASoC: qcom: q6apm-dai: reject compress rings larger than the DMA buffer
Date: Sun, 15 Nov 2026 10:55:02 +0000 [thread overview]
Message-ID: <5d8b5bc8-0937-4ee9-bcbf-4d35f05bed0c@oss.qualcomm.com> (raw)
In-Reply-To: <20261111080624.244291-2-julius@bairaktaris.de>
On 11/11/26 8:06 AM, Julius Bairaktaris wrote:
> q6apm_dai_compr_open() allocates a fixed 8 MiB DMA buffer, but
> q6apm_dai_compr_set_params() takes the ring size from the fragment size
> and count that userspace passes to SNDRV_COMPRESS_SET_PARAMS without
> checking it against that buffer. The compress core checks the geometry
> against the runtime buffer only for drivers without a copy callback.
> q6apm_compr_copy() places each write() at the stream position modulo the
> ring size, so a ring larger than the DMA buffer lets write() copy user
> data past its end, and after SNDRV_COMPRESS_NEXT_TRACK the copy starts at
> the next multiple of the fragment size.
>
> Reject a ring larger than the DMA buffer.
>
> Fixes: c317d148a2b0 ("ASoC: q6dsp: q6apm-dai: Add mmap and copy compress DAI callbacks")
> Cc: stable@vger.kernel.org
> Signed-off-by: Julius Bairaktaris <julius@bairaktaris.de>
> ---
Thanks for sending the patches
both look good to me, but I would recommend adding a dev_err() so that
its visible to user if it fails.
once that is fixed.
Reviewed-by: Srinivas Kandagatla<srinivas.kandagatla@oss.qualcomm.com>
--Srini
> sound/soc/qcom/qdsp6/q6apm-dai.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/sound/soc/qcom/qdsp6/q6apm-dai.c b/sound/soc/qcom/qdsp6/q6apm-dai.c
> index 58beaf906b9ff..80b837992b429 100644
> --- a/sound/soc/qcom/qdsp6/q6apm-dai.c
> +++ b/sound/soc/qcom/qdsp6/q6apm-dai.c
> @@ -990,6 +990,9 @@ static int q6apm_dai_compr_set_params(struct snd_soc_component *component,
> if (!pdata)
> return -EINVAL;
>
> + if (runtime->buffer_size > prtd->dma_buffer.bytes)
> + return -EINVAL;
> +
> prtd->periods = runtime->fragments;
> prtd->pcm_count = runtime->fragment_size;
> prtd->pcm_size = runtime->fragments * runtime->fragment_size;
next prev parent reply other threads:[~2026-11-15 10:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 8:06 [PATCH 0/2] ASoC: qcom: qdsp6: bound the compress ring by " Julius Bairaktaris
2026-11-11 8:06 ` [PATCH 1/2] ASoC: qcom: q6apm-dai: reject compress rings larger than " Julius Bairaktaris
2026-11-15 10:55 ` Srinivas Kandagatla [this message]
2026-11-11 8:06 ` [PATCH 2/2] ASoC: qcom: q6asm-dai: " Julius Bairaktaris
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=5d8b5bc8-0937-4ee9-bcbf-4d35f05bed0c@oss.qualcomm.com \
--to=srinivas.kandagatla@oss.qualcomm.com \
--cc=broonie@kernel.org \
--cc=julius@bairaktaris.de \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=mohammad.rafi.shaik@oss.qualcomm.com \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.dev \
--cc=srini@kernel.org \
--cc=tiwai@suse.com \
--cc=vkoul@kernel.org \
/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®