linux-kernel - Re: Design of interrupt controller driver

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 for Android: free password hash cracker in your pocket

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

Date:   Tue, 6 Jun 2017 12:29:57 +0200 (CEST)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Mason <slash.tmp@...e.fr>
cc:     Marc Zyngier <marc.zyngier@....com>,
        Jason Cooper <jason@...edaemon.net>,
        Mark Rutland <mark.rutland@....com>,
        Arnd Bergmann <arnd@...db.de>,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: Design of interrupt controller driver

On Tue, 6 Jun 2017, Mason wrote:
> On 06/06/2017 09:39, Thomas Gleixner wrote:
> What about disable_irq(virq);
> That function /is/ exported API, and eventually calls mask_irq.
> 
> disable_irq -> __disable_irq_nosync -> __disable_irq -> irq_disable -> mask_irq

What you can call from an ISR is disable_irq_nosync(). disable_irq() will
deadlock.

Thanks,

	tglx