From: Jean Delvare <jdelvare@suse.de>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Hardware Monitoring <linux-hwmon@vger.kernel.org>
Subject: Re: [PATCH v2] hwmon: (nct7802) Fix overflows seen when writing into limit attributes
Date: Mon, 12 Dec 2016 11:03:55 +0100 [thread overview]
Message-ID: <20161212110355.7907737e@endymion> (raw)
In-Reply-To: <1481316062-4999-1-git-send-email-linux@roeck-us.net>
On Fri, 9 Dec 2016 12:41:02 -0800, Guenter Roeck wrote:
> Fix overflows seen when writing voltage and temperature limit attributes.
>
> The value passed to DIV_ROUND_CLOSEST() needs to be clamped, and the
> value parameter passed to nct7802_write_fan_min() is an unsigned long.
>
> Also, writing values larger than 2700000 into a limit attribute results
> in writing 0 into the chip's limit registers.
You are only talking about _fan_ limits, right?
> The exact behavior when
> writing this value is unspecified. For consistency, report a limit of
> 1350000 if the chip register reads 0. This may be wrong, and the chip
> behavior should be verified with the actual chip, but it is better than
> reporting a value of 0 (which, if written, results in writing a value
> of 0x1fff into the chip register).
This fix is good by doesn't seem to be related with the overflows?
>
> Fixes: 3434f3783580 ("hwmon: Driver for Nuvoton NCT7802Y")
> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
> ---
> v2: When reading a register value of 0 from a limit register,
> report it as speed of 1350000.
> Avoid overflow due to different variable types passed to
> nct7802_write_fan_min().
> Fix low limit in store_temp (-128, not -127 as in v1).
>
> drivers/hwmon/nct7802.c | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/hwmon/nct7802.c b/drivers/hwmon/nct7802.c
> index 3ce33d244cc0..12b94b094c0d 100644
> --- a/drivers/hwmon/nct7802.c
> +++ b/drivers/hwmon/nct7802.c
> @@ -259,13 +259,15 @@ static int nct7802_read_fan_min(struct nct7802_data *data, u8 reg_fan_low,
> ret = 0;
> else if (ret)
> ret = DIV_ROUND_CLOSEST(1350000U, ret);
> + else
> + ret = 1350000U;
> abort:
> mutex_unlock(&data->access_lock);
> return ret;
> }
>
> static int nct7802_write_fan_min(struct nct7802_data *data, u8 reg_fan_low,
> - u8 reg_fan_high, unsigned int limit)
> + u8 reg_fan_high, unsigned long limit)
> {
> int err;
>
> @@ -326,8 +328,8 @@ static int nct7802_write_voltage(struct nct7802_data *data, int nr, int index,
> int shift = 8 - REG_VOLTAGE_LIMIT_MSB_SHIFT[index - 1][nr];
> int err;
>
> + voltage = clamp_val(voltage, 0, 0x3ff * nct7802_vmul[nr]);
> voltage = DIV_ROUND_CLOSEST(voltage, nct7802_vmul[nr]);
> - voltage = clamp_val(voltage, 0, 0x3ff);
>
> mutex_lock(&data->access_lock);
> err = regmap_write(data->regmap,
> @@ -402,7 +404,7 @@ static ssize_t store_temp(struct device *dev, struct device_attribute *attr,
> if (err < 0)
> return err;
>
> - val = clamp_val(DIV_ROUND_CLOSEST(val, 1000), -128, 127);
> + val = DIV_ROUND_CLOSEST(clamp_val(val, -128000, 127000), 1000);
>
> err = regmap_write(data->regmap, nr, val & 0xff);
> return err ? : count;
Reviewed-by: Jean Delvare <jdelvare@suse.de>
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2016-12-12 10:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-09 20:41 [PATCH v2] hwmon: (nct7802) Fix overflows seen when writing into limit attributes Guenter Roeck
2016-12-12 10:03 ` Jean Delvare [this message]
2016-12-12 14:14 ` Guenter Roeck
2016-12-12 15:43 ` Jean Delvare
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=20161212110355.7907737e@endymion \
--to=jdelvare@suse.de \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux@roeck-us.net \
/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