linux-kernel - question about disable_irq() and free

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>] [day] [month] [year] [list]

Message-ID: <a943a7ed-7a17-4c22-a617-b327f7f302e9@broadcom.com>
Date: Wed, 13 Aug 2025 21:31:41 +0200
From: Arend van Spriel <arend.vanspriel@...adcom.com>
To: Thomas Gleixner <tglx@...utronix.de>,
 "Russell King (Oracle)" <rmk+kernel@...linux.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: question about disable_irq() and free_irq()

I have gone through the "Linux generic IRQ handling" page [1] but I 
could not find a definitive answer to my question. So hopefully you can 
clarify it for me.

I was wondering whether a disable_irq() must be followed by 
enable_irq(), leaving the nested disable out of this, or could one call 
free_irq() for a disabled irq.

Regards,
Arend

[1] https://docs.kernel.org/core-api/genericirq.html