linux-kernel - Re: [PATCH] pinctrl: stm32: check for IRQ MUX validity during alloc()

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

Date:   Sat, 26 Jun 2021 01:53:48 +0200
From:   Linus Walleij <linus.walleij@...aro.org>
To:     Fabien Dessenne <fabien.dessenne@...s.st.com>
Cc:     Maxime Coquelin <mcoquelin.stm32@...il.com>,
        Alexandre Torgue <alexandre.torgue@...s.st.com>,
        "open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
        linux-stm32@...md-mailman.stormreply.com,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>,
        linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] pinctrl: stm32: check for IRQ MUX validity during alloc()

On Thu, Jun 17, 2021 at 4:46 PM Fabien Dessenne
<fabien.dessenne@...s.st.com> wrote:

> Considering the following irq_domain_ops call chain:
> - .alloc() is called when a clients calls platform_get_irq() or
>   gpiod_to_irq()
> - .activate() is called next, when the clients calls
>   request_threaded_irq()
> Check for the IRQ MUX conflict during the first stage (alloc instead of
> activate). This avoids to provide the client with an IRQ that can't be
> used.
>
> Signed-off-by: Fabien Dessenne <fabien.dessenne@...s.st.com>

Patch applied!

Yours,
Linus Walleij