linux-kernel - Re: [PATCH 2/2] genirq: proc: fix a procfs entry leak

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: <875y54ci86.ffs@tglx>
Date:   Thu, 24 Aug 2023 22:12:41 +0200
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Bartosz Golaszewski <brgl@...ev.pl>,
        Marc Zyngier <marc.zyngier@....com>
Cc:     linux-kernel@...r.kernel.org,
        Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
Subject: Re: [PATCH 2/2] genirq: proc: fix a procfs entry leak

On Mon, Aug 14 2023 at 11:36, Bartosz Golaszewski wrote:

Please read and follow the guidelines of the tip tree:

  https://www.kernel.org/doc/html/latest/process/maintainer-tip.html

> From: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
>
> When removing the proc entry for a desc that still has active users, we
> will leak the irqaction entries. Let's remove them in
> unregister_irq_proc().

How exactly is an interrupt descriptor freed which has still active
users?

If that happens then the procfs entry leak is the least of your worries.

Thanks,

        tglx