From: coverity-bot <keescook@chromium.org>
To: Amit Kucheria <amit.kucheria@linaro.org>
Cc: Stephen Boyd <swboyd@chromium.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
linux-next@vger.kernel.org
Subject: Coverity: degc_to_code(): Integer handling issues
Date: Mon, 28 Oct 2019 16:06:23 -0700 [thread overview]
Message-ID: <201910281606.F95870B3@keescook> (raw)
Hello!
This is an experimental automated report about issues detected by Coverity
from a scan of next-20191025 as part of the linux-next weekly scan project:
https://scan.coverity.com/projects/linux-next-weekly-scan
You're getting this email because you were associated with the identified
lines of code (noted below) that were touched by recent commits:
fbfe1a042cfd ("drivers: thermal: tsens: Add interrupt support")
Coverity reported the following:
*** CID 1487360: Integer handling issues (OVERFLOW_BEFORE_WIDEN)
/drivers/thermal/qcom/tsens-common.c: 95 in degc_to_code()
89 dev_dbg(priv->dev, "%s: offset:%d\n", __func__, priv->sensor[i].offset);
90 }
91 }
92
93 static inline u32 degc_to_code(int degc, const struct tsens_sensor *s)
94 {
vvv CID 1487360: Integer handling issues (OVERFLOW_BEFORE_WIDEN)
vvv Potentially overflowing expression "degc * s->slope" with type "int" (32 bits, signed) is evaluated using 32-bit arithmetic, and then used in a context that expects an expression of type "u64" (64 bits, unsigned).
95 u64 code = (degc * s->slope + s->offset) / SLOPE_FACTOR;
96
97 pr_debug("%s: raw_code: 0x%llx, degc:%d\n", __func__, code, degc);
98 return clamp_val(code, THRESHOLD_MIN_ADC_CODE, THRESHOLD_MAX_ADC_CODE);
99 }
100
If this is a false positive, please let us know so we can mark it as
such, or teach the Coverity rules to be smarter. If not, please make
sure fixes get into linux-next. :) For patches fixing this, please
include:
Reported-by: coverity-bot <keescook+coverity-bot@chromium.org>
Addresses-Coverity-ID: 1487360 ("Integer handling issues")
Fixes: fbfe1a042cfd ("drivers: thermal: tsens: Add interrupt support")
Thanks for your attention!
--
Coverity-bot
reply other threads:[~2019-10-28 23:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201910281606.F95870B3@keescook \
--to=keescook@chromium.org \
--cc=amit.kucheria@linaro.org \
--cc=daniel.lezcano@linaro.org \
--cc=gustavo@embeddedor.com \
--cc=linux-next@vger.kernel.org \
--cc=swboyd@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.