From: Kent Gibson <warthog618@gmail.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [PATCH v2 1/5] gpio: sysfs: use cleanup guards for gpiod_data::mutex
Date: Fri, 25 Oct 2024 21:24:20 +0800 [thread overview]
Message-ID: <20241025132420.GA155087@rigel> (raw)
In-Reply-To: <20241025-gpio-notify-sysfs-v2-1-5bd1b1b0b3e6@linaro.org>
On Fri, Oct 25, 2024 at 02:18:51PM +0200, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
>
> Shrink the code and drop some goto labels by using lock guards around
> gpiod_data::mutex.
>
> Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
> ---
> drivers/gpio/gpiolib-sysfs.c | 81 ++++++++++++++++----------------------------
> 1 file changed, 29 insertions(+), 52 deletions(-)
>
> @@ -139,19 +132,17 @@ static ssize_t value_store(struct device *dev,
> long value;
>
> status = kstrtol(buf, 0, &value);
> + if (status)
> + return status;
>
> - mutex_lock(&data->mutex);
> + guard(mutex)(&data->mutex);
>
> - if (!test_bit(FLAG_IS_OUT, &desc->flags)) {
> - status = -EPERM;
> - } else if (status == 0) {
> - gpiod_set_value_cansleep(desc, value);
> - status = size;
> - }
> + if (!test_bit(FLAG_IS_OUT, &desc->flags))
> + return -EPERM;
>
> - mutex_unlock(&data->mutex);
> + gpiod_set_value_cansleep(desc, value);
>
> - return status;
> + return size;
> }
This is a behavioural change as you've moved the decode check before the
permission check. Not sure if that is significant or not, so in my
suggestion I retained the old order.
Cheers,
Kent.
next prev parent reply other threads:[~2024-10-25 13:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 12:18 [PATCH v2 0/5] gpio: sysfs: send character device notifications for sysfs class events Bartosz Golaszewski
2024-10-25 12:18 ` [PATCH v2 1/5] gpio: sysfs: use cleanup guards for gpiod_data::mutex Bartosz Golaszewski
2024-10-25 13:24 ` Kent Gibson [this message]
2024-10-25 14:08 ` Bartosz Golaszewski
2024-10-25 15:34 ` Kent Gibson
2024-10-25 16:12 ` Bartosz Golaszewski
2024-10-25 12:18 ` [PATCH v2 2/5] gpio: sysfs: use cleanup guards for the sysfs_lock mutex Bartosz Golaszewski
2024-10-25 12:18 ` [PATCH v2 3/5] gpio: sysfs: emit chardev line-state events on GPIO export Bartosz Golaszewski
2024-10-25 12:18 ` [PATCH v2 4/5] gpio: sysfs: emit chardev line-state events on active-low changes Bartosz Golaszewski
2024-10-25 12:18 ` [PATCH v2 5/5] gpio: sysfs: emit chardev line-state events on edge store Bartosz Golaszewski
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=20241025132420.GA155087@rigel \
--to=warthog618@gmail.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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.