linux-kernel - Re: [PATCH v2] gpio: free irqs that are still requested when the chip is being removed

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <172768450502.13259.2790852008542028745.b4-ty@linaro.org>
Date: Mon, 30 Sep 2024 10:22:30 +0200
From: Bartosz Golaszewski <brgl@...ev.pl>
To: Herve Codina <herve.codina@...tlin.com>,
	Linus Walleij <linus.walleij@...aro.org>,
	Bartosz Golaszewski <brgl@...ev.pl>
Cc: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>,
	linux-gpio@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] gpio: free irqs that are still requested when the chip is being removed

From: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>


On Thu, 19 Sep 2024 15:51:04 +0200, Bartosz Golaszewski wrote:
> 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.
> 
> [...]

Applied, thanks!

[1/1] gpio: free irqs that are still requested when the chip is being removed
      commit: ec8b6f55b98146c41dcf15e8189eb43291e35e89

Best regards,
-- 
Bartosz Golaszewski <bartosz.golaszewski@...aro.org>