From: Jonathan Cameron <jic23@kernel.org>
To: trix@redhat.com
Cc: roan@protonic.nl, lars@metafoo.de, nathan@kernel.org,
ndesaulniers@google.com, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH] iio: scd4x: check return of scd4x_write_and_fetch
Date: Sun, 27 Feb 2022 17:48:50 +0000 [thread overview]
Message-ID: <20220227174850.73520e39@jic23-huawei> (raw)
In-Reply-To: <20220227154331.80338-1-trix@redhat.com>
On Sun, 27 Feb 2022 07:43:31 -0800
trix@redhat.com wrote:
> From: Tom Rix <trix@redhat.com>
>
> Clang static analysis reports this problem
> scd4x.c:474:10: warning: The left operand of '==' is a
> garbage value
> if (val == 0xff) {
> ~~~ ^
> val is only set from a successful call to scd4x_write_and_fetch()
> So check it's return.
>
> Fixes: 49d22b695cbb ("drivers: iio: chemical: Add support for Sensirion SCD4x CO2 sensor")
> Signed-off-by: Tom Rix <trix@redhat.com>
Good find, but I'd prefer a separate check on ret inline with what the
other error checking paths in that function are doing.
> ---
> drivers/iio/chemical/scd4x.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/iio/chemical/scd4x.c b/drivers/iio/chemical/scd4x.c
> index 20d4e7584e923..b978330fb761c 100644
> --- a/drivers/iio/chemical/scd4x.c
> +++ b/drivers/iio/chemical/scd4x.c
> @@ -471,7 +471,7 @@ static ssize_t calibration_forced_value_store(struct device *dev,
> ret = scd4x_write_and_fetch(state, CMD_FRC, arg, &val, sizeof(val));
> mutex_unlock(&state->lock);
>
> - if (val == 0xff) {
> + if (!ret && val == 0xff) {
> dev_err(dev, "forced calibration has failed");
> return -EINVAL;
> }
Prefer
if (ret)
return ret;
if (val == 0xff) {
dev_err(dev, "...
return -EINVAL;
}
Thanks,
Jonathan
next prev parent reply other threads:[~2022-02-27 17:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-27 15:43 [PATCH] iio: scd4x: check return of scd4x_write_and_fetch trix
2022-02-27 17:48 ` Jonathan Cameron [this message]
2022-02-28 21:06 ` Tom Rix
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=20220227174850.73520e39@jic23-huawei \
--to=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=roan@protonic.nl \
--cc=trix@redhat.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