From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Linus Walleij <linus.walleij@linaro.org>,
Kent Gibson <warthog618@gmail.com>, Alex Elder <elder@linaro.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
"Paul E . McKenney" <paulmck@kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Wolfram Sang <wsa@the-dreams.de>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
kernel test robot <oliver.sang@intel.com>
Subject: [PATCH 3/3] gpio: use rcu_dereference_protected() to make lockdep happy
Date: Tue, 13 Feb 2024 10:31:08 +0100 [thread overview]
Message-ID: <20240213093108.13922-4-brgl@bgdev.pl> (raw)
In-Reply-To: <20240213093108.13922-1-brgl@bgdev.pl>
From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Lockdep with CONFIG_PROVE_RCU enabled reports false positives about
suspicious rcu_dereference() usage. Let's silence it by using
rcu_dereference_protected().
Fixes: d83cee3d2bb1 ("gpio: protect the pointer to gpio_chip in gpio_device with SRCU")
Reported-by: kernel test robot <oliver.sang@intel.com>
Closes: https://lore.kernel.org/oe-lkp/202402122234.d85cca9b-lkp@intel.com
Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
---
drivers/gpio/gpiolib.c | 12 ++++++++----
drivers/gpio/gpiolib.h | 4 +++-
2 files changed, 11 insertions(+), 5 deletions(-)
diff --git a/drivers/gpio/gpiolib.c b/drivers/gpio/gpiolib.c
index c1391a9a0af6..d7503376b918 100644
--- a/drivers/gpio/gpiolib.c
+++ b/drivers/gpio/gpiolib.c
@@ -109,7 +109,8 @@ const char *gpiod_get_label(struct gpio_desc *desc)
return "interrupt";
return test_bit(FLAG_REQUESTED, &flags) ?
- rcu_dereference(desc->label) : NULL;
+ rcu_dereference_protected(desc->label,
+ lockdep_is_held(&desc->srcu)) : NULL;
}
static int desc_set_label(struct gpio_desc *desc, const char *label)
@@ -2978,7 +2979,8 @@ static int gpiod_get_raw_value_commit(const struct gpio_desc *desc)
guard(srcu)(&gdev->srcu);
- gc = rcu_dereference(gdev->chip);
+ gc = rcu_dereference_protected(gdev->chip,
+ lockdep_is_held(&gdev->srcu));
if (!gc)
return -ENODEV;
@@ -3012,7 +3014,8 @@ static bool gpio_device_chip_cmp(struct gpio_device *gdev, struct gpio_chip *gc)
{
guard(srcu)(&gdev->srcu);
- return gc == rcu_dereference(gdev->chip);
+ return gc == rcu_dereference_protected(gdev->chip,
+ lockdep_is_held(&gdev->srcu));
}
int gpiod_get_array_value_complex(bool raw, bool can_sleep,
@@ -3593,7 +3596,8 @@ int gpiod_to_irq(const struct gpio_desc *desc)
gdev = desc->gdev;
/* FIXME Cannot use gpio_chip_guard due to const desc. */
guard(srcu)(&gdev->srcu);
- gc = rcu_dereference(gdev->chip);
+ gc = rcu_dereference_protected(gdev->chip,
+ lockdep_is_held(&gdev->srcu));
if (!gc)
return -ENODEV;
diff --git a/drivers/gpio/gpiolib.h b/drivers/gpio/gpiolib.h
index 07443d26cbca..a857848b8955 100644
--- a/drivers/gpio/gpiolib.h
+++ b/drivers/gpio/gpiolib.h
@@ -14,6 +14,7 @@
#include <linux/err.h>
#include <linux/gpio/consumer.h> /* for enum gpiod_flags */
#include <linux/gpio/driver.h>
+#include <linux/lockdep.h>
#include <linux/module.h>
#include <linux/notifier.h>
#include <linux/srcu.h>
@@ -202,7 +203,8 @@ DEFINE_CLASS(gpio_chip_guard,
_guard.gdev = desc->gdev;
_guard.idx = srcu_read_lock(&_guard.gdev->srcu);
- _guard.gc = rcu_dereference(_guard.gdev->chip);
+ _guard.gc = rcu_dereference_protected(_guard.gdev->chip,
+ lockdep_is_held(&_guard.gdev->srcu));
_guard;
}),
--
2.40.1
next prev parent reply other threads:[~2024-02-13 9:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 9:31 [PATCH 0/3] gpio: fix SRCU bugs Bartosz Golaszewski
2024-02-13 9:31 ` [PATCH 1/3] gpio: take the SRCU read lock in gpiod_hog() Bartosz Golaszewski
2024-02-13 21:29 ` Linus Walleij
2024-02-13 9:31 ` [PATCH 2/3] gpio: cdev: use correct pointer accessors with SRCU Bartosz Golaszewski
2024-02-13 21:33 ` Linus Walleij
2024-02-13 9:31 ` Bartosz Golaszewski [this message]
2024-02-13 12:03 ` [PATCH 3/3] gpio: use rcu_dereference_protected() to make lockdep happy Paul E. McKenney
2024-02-13 12:06 ` 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=20240213093108.13922-4-brgl@bgdev.pl \
--to=brgl@bgdev.pl \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=elder@linaro.org \
--cc=geert+renesas@glider.be \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver.sang@intel.com \
--cc=paulmck@kernel.org \
--cc=warthog618@gmail.com \
--cc=wsa@the-dreams.de \
/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;
as well as URLs for NNTP newsgroup(s).