From: Guenter Roeck <linux@roeck-us.net>
To: Nicolin Chen <nicoleotsuka@gmail.com>
Cc: jdelvare@suse.com, linux-hwmon@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hwmon (ina3221) Add mutex lock to shunt nodes
Date: Mon, 12 Nov 2018 20:31:22 -0800 [thread overview]
Message-ID: <20181113043122.GA11205@roeck-us.net> (raw)
In-Reply-To: <20181113042324.852-1-nicoleotsuka@gmail.com>
On Mon, Nov 12, 2018 at 08:23:24PM -0800, Nicolin Chen wrote:
> The shunt resistor values are used to calculate shunt voltages
> and currents. As a part of sysfs nodes, it would be better to
> get protected with the same mutex too as other sysfs ABI nodes,
> although this is not very critical because the mutex was added
> to mainly protect register access.
>
> So this patch adds the mutex lock to protect the shunt node.
>
I am missing something here. I don't see the point of this mutex.
It just reads a variable and reports the result. When setting,
it just writes a value. Protecting the conversion of the passed
value with a mutex is pointless. Protecting writing the value
against reading it is just as pointless.
Guenter
> Signed-off-by: Nicolin Chen <nicoleotsuka@gmail.com>
> ---
> drivers/hwmon/ina3221.c | 17 +++++++++++++++--
> 1 file changed, 15 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/hwmon/ina3221.c b/drivers/hwmon/ina3221.c
> index 86281afd2619..f7a09ab6c440 100644
> --- a/drivers/hwmon/ina3221.c
> +++ b/drivers/hwmon/ina3221.c
> @@ -532,8 +532,15 @@ static ssize_t ina3221_show_shunt(struct device *dev,
> struct ina3221_data *ina = dev_get_drvdata(dev);
> unsigned int channel = sd_attr->index;
> struct ina3221_input *input = &ina->inputs[channel];
> + ssize_t ret;
>
> - return snprintf(buf, PAGE_SIZE, "%d\n", input->shunt_resistor);
> + mutex_lock(&ina->lock);
> +
> + ret = snprintf(buf, PAGE_SIZE, "%d\n", input->shunt_resistor);
> +
> + mutex_unlock(&ina->lock);
> +
> + return ret;
> }
>
> static ssize_t ina3221_set_shunt(struct device *dev,
> @@ -547,14 +554,20 @@ static ssize_t ina3221_set_shunt(struct device *dev,
> int val;
> int ret;
>
> + mutex_lock(&ina->lock);
> +
> ret = kstrtoint(buf, 0, &val);
> - if (ret)
> + if (ret) {
> + mutex_unlock(&ina->lock);
> return ret;
> + }
>
> val = clamp_val(val, 1, INT_MAX);
>
> input->shunt_resistor = val;
>
> + mutex_unlock(&ina->lock);
> +
> return count;
> }
>
> --
> 2.17.1
>
next prev parent reply other threads:[~2018-11-13 4:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-13 4:23 [PATCH] hwmon (ina3221) Add mutex lock to shunt nodes Nicolin Chen
2018-11-13 4:31 ` Guenter Roeck [this message]
2018-11-13 4:41 ` Nicolin Chen
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=20181113043122.GA11205@roeck-us.net \
--to=linux@roeck-us.net \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicoleotsuka@gmail.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