From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Bard Liao <yung-chuan.liao@linux.intel.com>,
alsa-devel@alsa-project.org, vkoul@kernel.org
Cc: vinod.koul@linaro.org, tiwai@suse.de, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, ranjani.sridharan@linux.intel.com,
hui.wang@canonical.com, broonie@kernel.org,
srinivas.kandagatla@linaro.org, jank@cadence.com,
mengdong.lin@intel.com, sanyog.r.kale@intel.com,
rander.wang@linux.intel.com, bard.liao@intel.com
Subject: Re: [PATCH v3 0/3] ASoC: soundwire: fix port_ready[] dynamic allocation
Date: Mon, 31 Aug 2020 10:12:08 -0500 [thread overview]
Message-ID: <dd947a84-87cb-7eed-9ac2-fe3de42dfc31@linux.intel.com> (raw)
In-Reply-To: <20200830132742.20404-1-yung-chuan.liao@linux.intel.com>
On 8/30/20 8:27 AM, Bard Liao wrote:
> The existing code allocates memory for the total number of ports.
> This only works if the ports are contiguous, but will break if e.g. a
> Devices uses port0, 1, and 14. The port_ready[] array would contain 3
> elements, which would lead to an out-of-bounds access. Conversely in
> other cases, the wrong port index would be used leading to timeouts on
> prepare.
>
> This can be fixed by allocating for the worst-case of 15
> ports (DP0..DP14). In addition since the number is now fixed, we can
> use an array instead of a dynamic allocation.
Bard, the order of patches will break git bisect, no? I tried on my side
and get the following error after applying patch1
sound/soc/codecs/max98373-sdw.c:337:20: error: assignment to expression
with array type
337 | slave->port_ready = devm_kcalloc(&slave->dev, num_of_ports,
|
the order should be
ASoC: codecs: soundwire: remove port_ready[] usage from codecs.
soundwire: add definition for maximum number of ports
soundwire: fix port_ready[] dynamic allocation in mipi_disco
> Changes in v3:
> - Add ASoC tag in the cover letter title.
> - Edit the title and commit message of the third patch for better
> understanding.
>
> Changes in v2:
> - Split patches into sdw and asoc patches. Please note that "soundwire:
> fix port_ready[] dynamic allocation in mipi_disco" and "ASoC: codecs:
> fix port_ready[] dynamic allocation in ASoC codecs" should be merged
> at the same time.
>
> Pierre-Louis Bossart (3):
> soundwire: add definition for maximum number of ports
> soundwire: fix port_ready[] dynamic allocation in mipi_disco
> ASoC: codecs: soundwire: remove port_ready[] usage from codecs.
>
> drivers/soundwire/mipi_disco.c | 18 +-----------------
> drivers/soundwire/slave.c | 4 ++++
> include/linux/soundwire/sdw.h | 5 +++--
> sound/soc/codecs/max98373-sdw.c | 15 +--------------
> sound/soc/codecs/rt1308-sdw.c | 14 +-------------
> sound/soc/codecs/rt5682-sdw.c | 15 +--------------
> sound/soc/codecs/rt700-sdw.c | 15 +--------------
> sound/soc/codecs/rt711-sdw.c | 15 +--------------
> sound/soc/codecs/rt715-sdw.c | 33 +--------------------------------
> 9 files changed, 14 insertions(+), 120 deletions(-)
>
next prev parent reply other threads:[~2020-08-31 15:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-30 13:27 [PATCH v3 0/3] ASoC: soundwire: fix port_ready[] dynamic allocation Bard Liao
2020-08-30 13:27 ` [PATCH v3 1/3] soundwire: add definition for maximum number of ports Bard Liao
2020-08-30 13:27 ` [PATCH v3 2/3] soundwire: fix port_ready[] dynamic allocation in mipi_disco Bard Liao
2020-08-30 13:27 ` [PATCH v3 3/3] ASoC: codecs: soundwire: remove port_ready[] usage from codecs Bard Liao
2020-08-31 15:12 ` Pierre-Louis Bossart [this message]
2020-09-01 1:32 ` [PATCH v3 0/3] ASoC: soundwire: fix port_ready[] dynamic allocation Bard liao
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=dd947a84-87cb-7eed-9ac2-fe3de42dfc31@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=bard.liao@intel.com \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hui.wang@canonical.com \
--cc=jank@cadence.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mengdong.lin@intel.com \
--cc=rander.wang@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=sanyog.r.kale@intel.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=tiwai@suse.de \
--cc=vinod.koul@linaro.org \
--cc=vkoul@kernel.org \
--cc=yung-chuan.liao@linux.intel.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