linux-kernel - Re: Crashing 'kzm' target in next-20160913 due to 'gpio: mxc: shift gpio_mxc_init() to subsys

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]

Date:   Thu, 15 Sep 2016 14:19:29 +0200
From:   Linus Walleij <linus.walleij@...aro.org>
To:     Guenter Roeck <linux@...ck-us.net>
Cc:     Vladimir Zapolskiy <vladimir_zapolskiy@...tor.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Shawn Guo <shawnguo@...nel.org>
Subject: Re: Crashing 'kzm' target in next-20160913 due to 'gpio: mxc: shift
 gpio_mxc_init() to subsys_initcall level'

On Wed, Sep 14, 2016 at 4:33 PM, Guenter Roeck <linux@...ck-us.net> wrote:
> On 09/14/2016 12:19 AM, Linus Walleij wrote:
>>
>> On Wed, Sep 14, 2016 at 5:20 AM, Guenter Roeck <linux@...ck-us.net> wrote:
>>
>>> So, in other words, lots of bugs here. Nevertheless, I would suggest to
>>> keep
>>> using postcore_initcall(), at least until it is sure that all gpio
>>> clients handle
>>> -EPROBE_DEFER
>>> correctly.
>>
>>
>> So can I just revert this patch in isolation? None of the other patches
>> depend on it?
>>
> Good question, if this was part of a series.

No response from author, so betting on it and reverting this in isolation
with your Reported-by.

Yours,
Linus Walleij