From: "Ardelean, Alexandru" <alexandru.Ardelean@analog.com>
To: "stefan.popa@analog.com" <stefan.popa@analog.com>,
"Tachici, Alexandru" <Alexandru.Tachici@analog.com>,
"Caprioru, Mircea" <Mircea.Caprioru@analog.com>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"jic23@kernel.org" <jic23@kernel.org>,
"colin.king@canonical.com" <colin.king@canonical.com>,
"Hennerich, Michael" <Michael.Hennerich@analog.com>,
"lars@metafoo.de" <lars@metafoo.de>,
"knaack.h@gmx.de" <knaack.h@gmx.de>,
"pmeerw@pmeerw.net" <pmeerw@pmeerw.net>
Cc: "kernel-janitors@vger.kernel.org"
<kernel-janitors@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][next] iio: dac: ad5770r: fix off-by-one check on maximum number of channels
Date: Fri, 3 Apr 2020 13:26:00 +0000 [thread overview]
Message-ID: <84628ce3f18d1a1ab50f76d04386dbef46f151b3.camel@analog.com> (raw)
In-Reply-To: <20200403125838.71271-1-colin.king@canonical.com>
On Fri, 2020-04-03 at 13:58 +0100, Colin King wrote:
> [External]
>
> From: Colin Ian King <colin.king@canonical.com>
>
> Currently there is an off-by-one check on the number of channels that
> will cause an arry overrun in array st->output_mode when calling the
> function d5770r_store_output_range. Fix this by using >= rather than >
> to check for maximum number of channels.
>
Reviewed-by: Alexandru Ardelean <alexandru.ardelean@analog.com>
> Addresses-Coverity: ("Out-of-bounds access")
> Fixes: cbbb819837f6 ("iio: dac: ad5770r: Add AD5770R support")
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> drivers/iio/dac/ad5770r.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/iio/dac/ad5770r.c b/drivers/iio/dac/ad5770r.c
> index a98ea76732e7..2d7623b9b2c0 100644
> --- a/drivers/iio/dac/ad5770r.c
> +++ b/drivers/iio/dac/ad5770r.c
> @@ -525,7 +525,7 @@ static int ad5770r_channel_config(struct ad5770r_state
> *st)
> ret = fwnode_property_read_u32(child, "num", &num);
> if (ret)
> return ret;
> - if (num > AD5770R_MAX_CHANNELS)
> + if (num >= AD5770R_MAX_CHANNELS)
> return -EINVAL;
>
> ret = fwnode_property_read_u32_array(child,
next prev parent reply other threads:[~2020-04-03 13:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 12:58 Colin King
2020-04-03 13:26 ` Ardelean, Alexandru [this message]
2020-04-05 11:59 ` 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=84628ce3f18d1a1ab50f76d04386dbef46f151b3.camel@analog.com \
--to=alexandru.ardelean@analog.com \
--cc=Alexandru.Tachici@analog.com \
--cc=Michael.Hennerich@analog.com \
--cc=Mircea.Caprioru@analog.com \
--cc=colin.king@canonical.com \
--cc=jic23@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--cc=stefan.popa@analog.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®