From: Marek Szyprowski <m.szyprowski@samsung.com>
To: Tzung-Bi Shih <tzungbi@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>,
Linus Walleij <linusw@kernel.org>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gpio: Fix lockdep warnings in gpiolib_{cdev,sysfs}_register()
Date: Mon, 2 Mar 2026 10:08:05 +0100 [thread overview]
Message-ID: <caadf265-062e-47ff-a40e-ca4243f41157@samsung.com> (raw)
In-Reply-To: <20260228131430.102388-1-tzungbi@kernel.org>
On 28.02.2026 14:14, Tzung-Bi Shih wrote:
> A lockdep warning is reported in gpiolib-cdev driver:
>
> WARNING: drivers/gpio/gpiolib-cdev.c:2735 at
> gpiolib_cdev_register+0x114/0x140, CPU#1: swapper/0/1
> Modules linked in:
> CPU: 1 UID: 0 PID: 1 Comm: swapper/0 Not tainted
> 7.0.0-rc1-next-20260227-00065-g6af4b9cfeded #12259 PREEMPT
> Hardware name: Samsung Exynos (Flattened Device Tree)
> Call trace:
> unwind_backtrace from show_stack+0x10/0x14
> show_stack from dump_stack_lvl+0x68/0x88
> dump_stack_lvl from __warn+0x94/0x210
> __warn from warn_slowpath_fmt+0x1b0/0x1bc
> warn_slowpath_fmt from gpiolib_cdev_register+0x114/0x140
> gpiolib_cdev_register from gpiochip_setup_dev+0x4c/0xd0
> gpiochip_setup_dev from gpiochip_add_data_with_key+0x960/0xad4
> gpiochip_add_data_with_key from devm_gpiochip_add_data_with_key+0x20/0x5c
>
> This is because the SRCU wasn't held in gpiolib_cdev_register() when the
> caller is from gpiochip_add_data_with_key() instead of
> gpiochip_setup_devs(). gpiochip_sysfs_register() shares the similar
> concern.
>
> Given that both gpiolib_cdev_register() and gpiochip_sysfs_register()
> are only called from gpiolib but no external users. Remove the lockdep
> checks to fix the warnings.
>
> Reported-by: Marek Szyprowski <m.szyprowski@samsung.com>
> Closes: https://lore.kernel.org/all/506ce9b3-d492-4fce-9d02-330e411911e2@samsung.com/
> Fixes: cf674f1a0c98 ("gpio: Ensure struct gpio_chip for gpiochip_setup_dev()")
> Signed-off-by: Tzung-Bi Shih <tzungbi@kernel.org>
Tested-by: Marek Szyprowski <m.szyprowski@samsung.com>
> ---
> drivers/gpio/gpiolib-cdev.c | 2 --
> drivers/gpio/gpiolib-sysfs.c | 2 --
> 2 files changed, 4 deletions(-)
>
> diff --git a/drivers/gpio/gpiolib-cdev.c b/drivers/gpio/gpiolib-cdev.c
> index 7ebdb4993a74..f36b7c06996d 100644
> --- a/drivers/gpio/gpiolib-cdev.c
> +++ b/drivers/gpio/gpiolib-cdev.c
> @@ -2732,8 +2732,6 @@ int gpiolib_cdev_register(struct gpio_chip *gc, dev_t devt)
> struct gpio_device *gdev = gc->gpiodev;
> int ret;
>
> - lockdep_assert_held(&gdev->srcu);
> -
> cdev_init(&gdev->chrdev, &gpio_fileops);
> gdev->chrdev.owner = THIS_MODULE;
> gdev->dev.devt = MKDEV(MAJOR(devt), gdev->id);
> diff --git a/drivers/gpio/gpiolib-sysfs.c b/drivers/gpio/gpiolib-sysfs.c
> index 748a3eb1bf35..fc06b0c2881b 100644
> --- a/drivers/gpio/gpiolib-sysfs.c
> +++ b/drivers/gpio/gpiolib-sysfs.c
> @@ -990,8 +990,6 @@ int gpiochip_sysfs_register(struct gpio_chip *gc)
> struct device *parent;
> int err;
>
> - lockdep_assert_held(&gdev->srcu);
> -
> /*
> * Many systems add gpio chips for SOC support very early,
> * before driver model support is available. In those cases we
Best regards
--
Marek Szyprowski, PhD
Samsung R&D Institute Poland
next prev parent reply other threads:[~2026-03-02 9:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20260228131459eucas1p1b5deb465c52d0990a6920b0d8981975f@eucas1p1.samsung.com>
2026-02-28 13:14 ` Tzung-Bi Shih
2026-03-02 8:42 ` Bartosz Golaszewski
2026-03-02 9:08 ` Marek Szyprowski [this message]
2026-03-02 9:11 ` 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=caadf265-062e-47ff-a40e-ca4243f41157@samsung.com \
--to=m.szyprowski@samsung.com \
--cc=brgl@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tzungbi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®