linux-kernel - Re: [PATCH 2/3] regulator: Only free GPIOs if the core requested them

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]

Message-ID: <CACRpkdaoFVFKAEiXkMX2-E2qaaZmoTLWwXfei-Mf0LdGSReBxw@mail.gmail.com>
Date:   Fri, 30 Nov 2018 23:15:39 +0100
From:   Linus Walleij <linus.walleij@...aro.org>
To:     Mark Brown <broonie@...nel.org>
Cc:     Charles Keepax <ckeepax@...nsource.cirrus.com>,
        Liam Girdwood <lgirdwood@...il.com>,
        Marek Szyprowski <m.szyprowski@...sung.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        patches@...nsource.cirrus.com
Subject: Re: [PATCH 2/3] regulator: Only free GPIOs if the core requested them

On Fri, Nov 23, 2018 at 3:25 PM Mark Brown <broonie@...nel.org> wrote:

> However even with patch 3 I think it'd be better to base this off the
> rest of Linus' series for converting to descriptors (which is currently
> sitting waiting for some more testing) since that will convert
> everything to descriptors and so remove the code that's doing requests
> in the core entirely.

I have made the "real" (or so I think) solution to this problem which
essentially hardens the core so that it very explicitly takes over the
descriptor from the driver.

I'm just having it spin a bit around the 0day build servers (they
don't seem to respond right now). I built all patched drivers
I could easily configure in locally.

I am planning to respin the rest of the cleanups making the core only
handle descriptors on top of it.

Yours,
Linus Walleij