On Thu, Sep 19, 2024 at 1:13 PM Bartosz Golaszewski <brgl@xxxxxxxx> wrote: > > From: Bartosz Golaszewski <bartosz.golaszewski@xxxxxxxxxx> > > 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. > > Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@xxxxxxxxxx> > --- > Herve: if I say I'll do something, then I'll do it, no need to remind me every > six months. :) Anyway, this is a proposition of fixing the resource leak you > reported with gpiomon in a more generic way so we also address the same issue > for in-kernel users. > I noticed a problem here so I sent an improved version[1]. Bart [1] https://lore.kernel.org/linux-gpio/20240919135104.3583-1-brgl@xxxxxxxx/