diff options
| author |   Bartosz Golaszewski <bartosz.golaszewski@linaro.org> | 2024-09-19 15:51:04 +0200 |
|---|---|---|
| committer | Bartosz Golaszewski <bartosz.golaszewski@linaro.org> | 2024-09-30 10:10:45 +0200 |
| commit | ec8b6f55b98146c41dcf15e8189eb43291e35e89 (patch) | |
| tree | ff0c07db8044cb94d2cb3e67ef8cc21d1cc12959 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | Linux 6.12-rc1 (diff) | |
| download | wireguard-linux-ec8b6f55b98146c41dcf15e8189eb43291e35e89.tar.xz wireguard-linux-ec8b6f55b98146c41dcf15e8189eb43291e35e89.zip | |
gpio: free irqs that are still requested when the chip is being removed
If we remove a GPIO chip that is also an interrupt controller with users
not having freed some interrupts, we'll end up leaking resources as
indicated by the following warning:
remove_proc_entry: removing non-empty directory 'irq/30', leaking at least 'gpio'
As there's no way of notifying interrupt users about the irqchip going
away and the interrupt subsystem is not plugged into the driver model and
so not all cases can be handled by devlinks, we need to make sure to free
all interrupts before the complete the removal of the provider.
Reviewed-by: Herve Codina <herve.codina@bootlin.com>
Tested-by: Herve Codina <herve.codina@bootlin.com>
Link: https://lore.kernel.org/r/20240919135104.3583-1-brgl@bgdev.pl
Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions