From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: "Amadeusz Sławiński" <amadeuszx.slawinski@linux.intel.com>,
"Raghu Bankapur" <quic_rbankapu@quicinc.com>,
"Vinod Koul" <vkoul@kernel.org>,
"Jaroslav Kysela" <perex@perex.cz>,
"Takashi Iwai" <tiwai@suse.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Cc: Krishna Jha <quic_kkishorj@quicinc.com>,
Raghu Bankapur <quic_rbankapu@quiinc.com>
Subject: Re: [PATCH V0 1/1] ASoC: msm: fix integer overflow for long duration offload playback
Date: Wed, 9 Mar 2022 09:15:31 -0600 [thread overview]
Message-ID: <2e6b7905-4b9f-8615-a7f2-6b3d66e6386e@linux.intel.com> (raw)
In-Reply-To: <37933410-1bc7-3e27-50e8-3da03e8b5603@linux.intel.com>
On 3/9/22 08:51, Amadeusz Sławiński wrote:
> On 3/9/2022 3:22 PM, Raghu Bankapur wrote:
>> From: Raghu Bankapur <quic_rbankapu@quiinc.com>
>>
>> 32 bit variable is used for storing number of bytes copied to DSP,
>> which can overflow when playback duration goes beyond 24 hours.
>> Change data type for this variable to uint64_t to prevent overflow
>> and related playback anomaly.
>>
>> Signed-off-by: Raghu Bankapur <quic_rbankapu@quicinc.com>
>> ---
>> include/uapi/sound/compress_offload.h | 2 +-
>> sound/core/compress_offload.c | 2 +-
>> 2 files changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/include/uapi/sound/compress_offload.h
>> b/include/uapi/sound/compress_offload.h
>> index 9555f31c8425..57d24d89b2f4 100644
>> --- a/include/uapi/sound/compress_offload.h
>> +++ b/include/uapi/sound/compress_offload.h
>> @@ -67,7 +67,7 @@ struct snd_compr_params {
>> */
>> struct snd_compr_tstamp {
>> __u32 byte_offset;
>> - __u32 copied_total;
>> + __u64 copied_total;
>> __u32 pcm_frames;
>> __u32 pcm_io_frames;
>> __u32 sampling_rate;
>
> I don't think this patch should be merged as is. It changes UAPI header,
> most likely breaking existing user space tools. Can't overflow be
> handled somehow instead?
>
> Although having looked around, it makes a bit of sense, as
> snd_compr_update_tstamp() copies tstamp->copied_total to 64 bit
> variables...
>
> Perhaps raise protocol version? (
> https://elixir.bootlin.com/linux/latest/source/include/uapi/sound/compress_offload.h#L34
> )
This change sounded familiar, and sure enough we've already discussed
this in 2019. I thought we did change things but unfortunately no, the
problem is still there.
https://lore.kernel.org/alsa-devel/1560843846-4631-1-git-send-email-bgoswami@codeaurora.org/
we really want to change all the copied_total, pcm_frames and
pcm_io_frames to u64 and add a new IOCTL.
next prev parent reply other threads:[~2022-03-09 15:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 14:22 [PATCH V0 0/1] ASoC: msm: fix integer overflow for long duration compress offload playback Raghu Bankapur
2022-03-09 14:22 ` [PATCH V0 1/1] ASoC: msm: fix integer overflow for long duration " Raghu Bankapur
2022-03-09 14:51 ` Amadeusz Sławiński
2022-03-09 15:15 ` Pierre-Louis Bossart [this message]
2022-03-09 18:23 ` kernel test robot
2022-03-09 22:17 ` kernel test robot
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=2e6b7905-4b9f-8615-a7f2-6b3d66e6386e@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=quic_kkishorj@quicinc.com \
--cc=quic_rbankapu@quicinc.com \
--cc=quic_rbankapu@quiinc.com \
--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;
as well as URLs for NNTP newsgroup(s).