[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240210110043.853-1-hdanton@sina.com>
Date: Sat, 10 Feb 2024 19:00:41 +0800
From: Hillf Danton <hdanton@...a.com>
To: Bartosz Golaszewski <brgl@...ev.pl>
Cc: Linus Walleij <linus.walleij@...aro.org>,
"Paul E . McKenney" <paulmck@...nel.org>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Wolfram Sang <wsa@...-dreams.de>,
linux-gpio@...r.kernel.org,
linux-kernel@...r.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
Subject: Re: [PATCH v3 01/24] gpio: protect the list of GPIO devices with SRCU
On Thu, 8 Feb 2024 10:58:57 +0100 Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
> @@ -382,11 +389,13 @@ static int gpiodev_add_to_list_unlocked(struct gpio_device *gdev)
> /* add between prev and next */
> if (prev->base + prev->ngpio <= gdev->base
> && gdev->base + gdev->ngpio <= next->base) {
> - list_add(&gdev->list, &prev->list);
> + list_add_rcu(&gdev->list, &prev->list);
> return 0;
> }
> }
>
> + synchronize_srcu(&gpio_devices_srcu);
> +
If not typo, could you shed light on why this sync is needed?
> return -EBUSY;
> }
Powered by blists - more mailing lists