From: <Marius.Cristea@microchip.com>
To: <jic23@kernel.org>, <javier.carrasco.cruz@gmail.com>, <lars@metafoo.de>
Cc: <linux-kernel@vger.kernel.org>, <linux-iio@vger.kernel.org>
Subject: Re: [PATCH] iio: adc: MCP3564: fix calib_bias and calib_scale range checks
Date: Mon, 4 Dec 2023 09:28:02 +0000 [thread overview]
Message-ID: <527409f3932fce519bd0e1d881d8bf5970641bf4.camel@microchip.com> (raw)
In-Reply-To: <20231201-mcp3564_range_checks-v1-1-68f4436e22b0@gmail.com>
Hi Javier Carrasco,
Thank you for looking over the driver, for spotting and reporting
the bug. Your fix is OK.
Reviewed-by: Marius Cristea <marius.cristea@microchip.com>
Thanks,
Marius
On Fri, 2023-12-01 at 10:48 +0100, Javier Carrasco wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you
> know the content is safe
>
> The current implementation uses the AND (&&) operator to check if the
> value to write for IIO_CHAN_INFO_CALIBBIAS and
> IIO_CHAN_INFO_CALIBSCALE
> is within the valid ranges.
> The evaluated values are the lower and upper limits of the ranges,
> so this operation always evaluates to false.
>
> The OR (||) operator must be used instead.
>
> Signed-off-by: Javier Carrasco <javier.carrasco.cruz@gmail.com>
> ---
> This bug has been found when looking for use cases of IIO_AVAIL_RANGE
> and the fix could not be tested with real hardware. The issue and its
> soulution are rather simple, but still some testing and confirmation
> would be welcome.
> ---
> drivers/iio/adc/mcp3564.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/iio/adc/mcp3564.c b/drivers/iio/adc/mcp3564.c
> index e3f1de5fcc5a..d5fb1cae8aeb 100644
> --- a/drivers/iio/adc/mcp3564.c
> +++ b/drivers/iio/adc/mcp3564.c
> @@ -918,7 +918,7 @@ static int mcp3564_write_raw(struct iio_dev
> *indio_dev,
> mutex_unlock(&adc->lock);
> return ret;
> case IIO_CHAN_INFO_CALIBBIAS:
> - if (val < mcp3564_calib_bias[0] && val >
> mcp3564_calib_bias[2])
> + if (val < mcp3564_calib_bias[0] || val >
> mcp3564_calib_bias[2])
> return -EINVAL;
>
> mutex_lock(&adc->lock);
> @@ -928,7 +928,7 @@ static int mcp3564_write_raw(struct iio_dev
> *indio_dev,
> mutex_unlock(&adc->lock);
> return ret;
> case IIO_CHAN_INFO_CALIBSCALE:
> - if (val < mcp3564_calib_scale[0] && val >
> mcp3564_calib_scale[2])
> + if (val < mcp3564_calib_scale[0] || val >
> mcp3564_calib_scale[2])
> return -EINVAL;
>
> if (adc->calib_scale == val)
>
> ---
> base-commit: 994d5c58e50e91bb02c7be4a91d5186292a895c8
> change-id: 20231201-mcp3564_range_checks-221708838130
>
> Best regards,
> --
> Javier Carrasco <javier.carrasco.cruz@gmail.com>
>
next prev parent reply other threads:[~2023-12-04 9:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 9:48 [PATCH] iio: adc: MCP3564: fix calib_bias and calib_scale range checks Javier Carrasco
2023-12-04 9:28 ` Marius.Cristea [this message]
[not found] ` <IA1PR11MB63958455F969F1506B3084769986A@IA1PR11MB6395.namprd11.prod.outlook.com>
2023-12-04 13:52 ` 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=527409f3932fce519bd0e1d881d8bf5970641bf4.camel@microchip.com \
--to=marius.cristea@microchip.com \
--cc=javier.carrasco.cruz@gmail.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.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