From: Jonathan Cameron <jic23@kernel.org>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Pengutronix Kernel Team <kernel@pengutronix.de>,
David Jander <david@protonic.nl>,
Robin van der Gracht <robin@protonic.nl>,
linux-iio@vger.kernel.org, Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [PATCH v1 1/1] iio: adc: tsc2046: fix memory corruption by preventing array overflow
Date: Sun, 9 Jan 2022 15:25:57 +0000 [thread overview]
Message-ID: <20220109152557.74f06d2d@jic23-huawei> (raw)
In-Reply-To: <20220107081401.2816357-1-o.rempel@pengutronix.de>
On Fri, 7 Jan 2022 09:14:01 +0100
Oleksij Rempel <o.rempel@pengutronix.de> wrote:
> On one side we have indio_dev->num_channels includes all physical channels +
> timestamp channel. On other side we have an array allocated only for
> physical channels. So, fix memory corruption by ARRAY_SIZE() instead of
> num_channels variable.
>
> Fixes: 9374e8f5a38d ("iio: adc: add ADC driver for the TI TSC2046 controller")
> Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
Hi Olesij,
Have you managed to make this occur, or is it inspection only?
I 'think' (it's been a while since I looked at the particular code) that the timestamp
bit in active_scan_mask will never actually be set because we handle that as a
separate flag.
So it is indeed an efficiency improvement to not check that bit but I don't think
it's a bug to do so. More than possible I'm missing something though!
This one had me quite worried when I first read it because this is a very common
pattern to see in IIO drivers.
Jonathan
> ---
> drivers/iio/adc/ti-tsc2046.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/iio/adc/ti-tsc2046.c b/drivers/iio/adc/ti-tsc2046.c
> index 91f6bd5effe7..8126084616e6 100644
> --- a/drivers/iio/adc/ti-tsc2046.c
> +++ b/drivers/iio/adc/ti-tsc2046.c
> @@ -395,7 +395,7 @@ static int tsc2046_adc_update_scan_mode(struct iio_dev *indio_dev,
> mutex_lock(&priv->slock);
>
> size = 0;
> - for_each_set_bit(ch_idx, active_scan_mask, indio_dev->num_channels) {
> + for_each_set_bit(ch_idx, active_scan_mask, ARRAY_SIZE(priv->l)) {
> size += tsc2046_adc_group_set_layout(priv, group, ch_idx);
> tsc2046_adc_group_set_cmd(priv, group, ch_idx);
> group++;
> @@ -561,7 +561,7 @@ static int tsc2046_adc_setup_spi_msg(struct tsc2046_adc_priv *priv)
> * enabled.
> */
> size = 0;
> - for (ch_idx = 0; ch_idx < priv->dcfg->num_channels; ch_idx++)
> + for (ch_idx = 0; ch_idx < ARRAY_SIZE(priv->l); ch_idx++)
> size += tsc2046_adc_group_set_layout(priv, ch_idx, ch_idx);
>
> priv->tx = devm_kzalloc(&priv->spi->dev, size, GFP_KERNEL);
next prev parent reply other threads:[~2022-01-09 15:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 8:14 [PATCH v1 1/1] iio: adc: tsc2046: fix memory corruption by preventing array overflow Oleksij Rempel
2022-01-09 15:25 ` Jonathan Cameron [this message]
2022-01-10 7:19 ` Oleksij Rempel
2022-01-15 18:16 ` Jonathan Cameron
2022-01-16 11:58 ` Jonathan Cameron
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=20220109152557.74f06d2d@jic23-huawei \
--to=jic23@kernel.org \
--cc=david@protonic.nl \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=robin@protonic.nl \
/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