From: Jonathan Cameron <jic23@kernel.org>
To: Maxwell Doose <m32285159@gmail.com>
Cc: dlechner@baylibre.com, nuno.sa@analog.com, andy@kernel.org,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] iio: chemical: scd30: Prevent potential divide-by-zero errors
Date: Mon, 11 May 2026 13:06:48 +0100 [thread overview]
Message-ID: <20260511130648.0c0f4deb@jic23-huawei> (raw)
In-Reply-To: <20260511130555.2eec64a3@jic23-huawei>
On Mon, 11 May 2026 13:05:55 +0100
Jonathan Cameron <jic23@kernel.org> wrote:
> On Sun, 10 May 2026 15:21:56 -0500
> Maxwell Doose <m32285159@gmail.com> wrote:
>
> > In scd30_read_raw, the current value of tmp in the
> > IIO_CHAN_INFO_SAMP_FREQ case is unchecked. Add checking to see if the
> > value we got was 0 to prevent a divide-by-zero error.
> >
> > A similar case has also been found in scd30_write_raw(), also in the
> > IIO_CHAN_INFO_SAMP_FREQ case, where the value of val2 was unchecked.
> > Add checking for that variable as well and return -EINVAL if it's 0.
> >
> > Fixes: 64b3d8b1b0f5 ("iio: chemical: scd30: add core driver")
> To me this one is a hardening change not a bug fix (unless we have
> reports of this hardware failure on a real product - not a devboard
> with dodgy wiring ;)
>
> So no fixes tag needed.
>
> Also there is already a fix for the write_raw one in my fixes-togreg
> branch. Antoniu got there a few weeks back.
By which I meant no fixes tag needed when it's just the read_raw case
where it isn't a userspace controlled value
J
>
> Jonathan
>
>
>
> > Signed-off-by: Maxwell Doose <m32285159@gmail.com>
> > ---
> > v2:
> > - Switch to dev_err_ratelimited() per sashiko.
> > - Fix another potential divide-by-zero error per sashiko (see commit
> > message).
> >
> > drivers/iio/chemical/scd30_core.c | 12 +++++++++++-
> > 1 file changed, 11 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/iio/chemical/scd30_core.c b/drivers/iio/chemical/scd30_core.c
> > index be8c055be184..3851c9334c8b 100644
> > --- a/drivers/iio/chemical/scd30_core.c
> > +++ b/drivers/iio/chemical/scd30_core.c
> > @@ -237,6 +237,16 @@ static int scd30_read_raw(struct iio_dev *indio_dev, struct iio_chan_spec const
> > if (ret)
> > return ret;
> >
> > + /*
> > + * Value of 0 is unexpected but possible if hardware is failing
> > + * or noise on data bus
> > + */
> > + if (!tmp) {
> > + dev_err_ratelimited(&indio_dev->dev,
> > + "Invalid measurement interval 0 received\n");
> > + return -EIO;
> > + }
> > +
> > *val = 0;
> > *val2 = 1000000000 / tmp;
> > return IIO_VAL_INT_PLUS_NANO;
> > @@ -261,7 +271,7 @@ static int scd30_write_raw(struct iio_dev *indio_dev, struct iio_chan_spec const
> > guard(mutex)(&state->lock);
> > switch (mask) {
> > case IIO_CHAN_INFO_SAMP_FREQ:
> > - if (val)
> > + if (val || !val2)
> > return -EINVAL;
> >
> > val = 1000000000 / val2;
>
prev parent reply other threads:[~2026-05-11 12:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-10 20:21 [PATCH v2] iio: chemical: scd30: Prevent potential divide-by-zero errors Maxwell Doose
2026-05-11 10:42 ` Andy Shevchenko
2026-05-11 12:05 ` Jonathan Cameron
2026-05-11 12:06 ` Jonathan Cameron [this message]
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=20260511130648.0c0f4deb@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m32285159@gmail.com \
--cc=nuno.sa@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