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: <CAHk-=wjxvNGEUUN5fj203KJL8qXK3jv359Ketc-HJMJU9wN6KA@mail.gmail.com>
Date:   Mon, 28 Mar 2022 14:41:33 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Jonathan Neuschäfer <j.neuschaefer@....net>
Cc:     Linus Walleij <linus.walleij@...aro.org>,
        Kees Cook <keescook@...omium.org>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        "open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>
Subject: Re: [GIT PULL] pin control bulk changes for v5.18

On Mon, Mar 28, 2022 at 2:38 PM Jonathan Neuschäfer
<j.neuschaefer@....net> wrote:
>
> It was — but when it was noticed, the fix went through the IRQ tree, on
> top of a refactoring that happened there (the switch to generic_handle_domain_irq):
>
> https://lore.kernel.org/lkml/164751044707.389.16417510835118111853.tip-bot2@tip-bot2/

Ok, that ends up at least being identical to what I did, so thats' good.

> When I added the pinctrl-wpcm450 driver, I changed the pinctrl/nuvoton/
> directory to obj-y and exposed the pinctrl-npcm7xx to CI bot testing.
> The bug existed, untouched, since the driver was added a few years ago.

Ahh. Good. So not a heisenbug, just happened to be hidden before.

Thanks for clarifying,

                 Linus

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ