gpio: don't let lockdep complain about inherently dangerous RCU usage
authorBartosz Golaszewski <bartosz.golaszewski@linaro.org>
Wed, 14 Feb 2024 08:44:19 +0000 (09:44 +0100)
committerBartosz Golaszewski <bartosz.golaszewski@linaro.org>
Thu, 15 Feb 2024 07:39:29 +0000 (08:39 +0100)
commit0d7fa0eda4e3ffe1b7ebc73b6ef81298bddda649
tree36856d053c8c32ea85a5dd3689e0f901901dc6c5
parentd82b9e0887e69d9060c854b079a3a5024788f7cb
gpio: don't let lockdep complain about inherently dangerous RCU usage

There are two legacy, deprecated functions - gpiod_to_chip() and
gpio_device_get_chip() - that still have users in tree. They return the
address of the SRCU-protected chip outside of the read-only critical
sections. They are inherently dangerous and the users should convert to
safer alternatives. Let's explicitly silence lockdep warnings by using
rcu_dereference_check(ptr, 1). While at it: reuse
gpio_device_get_chip() in gpiod_to_chip().

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