From: Guenter Roeck <linux@roeck-us.net>
To: Dmitry Osipenko <digetx@gmail.com>
Cc: Zhang Rui <rui.zhang@intel.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Amit Kucheria <amitk@kernel.org>,
Jean Delvare <jdelvare@suse.com>,
linux-hwmon@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH v4 1/2] hwmon: (lm90) Prevent integer underflows of temperature calculations
Date: Tue, 22 Jun 2021 16:15:25 -0700 [thread overview]
Message-ID: <20210622231525.GA1299338@roeck-us.net> (raw)
In-Reply-To: <20210621213153.28247-2-digetx@gmail.com>
On Tue, Jun 22, 2021 at 12:31:52AM +0300, Dmitry Osipenko wrote:
> The min/max/crit and all other temperature values that are passed to
> the driver are unlimited and value that is close to INT_MIN results in
> integer underflow of the temperature calculations made by the driver
> for LM99 sensor. Temperature hysteresis is among those values that need
> to be limited, but limiting of hysteresis is independent from the sensor
> version. Add the missing limits.
>
> Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
> ---
> drivers/hwmon/lm90.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/drivers/hwmon/lm90.c b/drivers/hwmon/lm90.c
> index b53f17511b05..ee6b8190f08e 100644
> --- a/drivers/hwmon/lm90.c
> +++ b/drivers/hwmon/lm90.c
> @@ -1028,6 +1028,9 @@ static int lm90_set_temp11(struct lm90_data *data, int index, long val)
> struct reg *regp = ®[index];
> int err;
>
> + /* prevent integer underflow */
> + val = max(val, -128000l);
> +
This and the adjustment below can be moved into the if() statement for lm99.
There is no need to affect other chips.
> /* +16 degrees offset for temp2 for the LM99 */
> if (data->kind == lm99 && index <= 2)
> val -= 16000;
> @@ -1088,6 +1091,9 @@ static int lm90_set_temp8(struct lm90_data *data, int index, long val)
> struct i2c_client *client = data->client;
> int err;
>
> + /* prevent integer underflow */
> + val = max(val, -128000l);
> +
> /* +16 degrees offset for temp2 for the LM99 */
> if (data->kind == lm99 && index == 3)
> val -= 16000;
> @@ -1130,6 +1136,9 @@ static int lm90_set_temphyst(struct lm90_data *data, long val)
> int temp;
> int err;
>
> + /* prevent integer underflow */
> + val = max(val, -128000l);
> +
Please move this further below, just before val is used, to better
show the context why it is needed.
Thanks,
Guenter
> if (data->kind == adt7461 || data->kind == tmp451)
> temp = temp_from_u8_adt7461(data, data->temp8[LOCAL_CRIT]);
> else if (data->kind == max6646)
> --
> 2.30.2
>
next prev parent reply other threads:[~2021-06-22 23:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 21:31 [PATCH v4 0/2] Support temperature trips by HWMON core and LM90 driver Dmitry Osipenko
2021-06-21 21:31 ` [PATCH v4 1/2] hwmon: (lm90) Prevent integer underflows of temperature calculations Dmitry Osipenko
2021-06-22 23:15 ` Guenter Roeck [this message]
2021-06-21 21:31 ` [PATCH v4 2/2] hwmon: Support set_trips() of thermal device ops Dmitry Osipenko
2021-06-22 23:17 ` Guenter Roeck
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=20210622231525.GA1299338@roeck-us.net \
--to=linux@roeck-us.net \
--cc=amitk@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=digetx@gmail.com \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=rui.zhang@intel.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