linux-kernel - Re: [PATCH 3.18 093/185] microblaze: switch to NO

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:   Tue, 29 May 2018 09:34:33 -0500
From:   Rob Herring <robh@...nel.org>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        stable <stable@...r.kernel.org>,
        Alvaro Gamez Machado <alvaro.gamez@...ent.com>,
        Michal Simek <michal.simek@...inx.com>,
        Sasha Levin <alexander.levin@...rosoft.com>
Subject: Re: [PATCH 3.18 093/185] microblaze: switch to NO_BOOTMEM

On Mon, May 28, 2018 at 5:02 AM, Greg Kroah-Hartman
<gregkh@...uxfoundation.org> wrote:
> 3.18-stable review patch.  If anyone has any objections, please let me know.
>
> ------------------
>
> From: Rob Herring <robh@...nel.org>
>
> [ Upstream commit 101646a24a2f9cdb61d7732459fbf068a7bbb542 ]
>
> Microblaze doesn't set CONFIG_NO_BOOTMEM and so memblock_virt_alloc()
> doesn't work for CONFIG_HAVE_MEMBLOCK && !CONFIG_NO_BOOTMEM.

Unless Michal feels differently, I don't think this should go in
stable. The DT change that broke microblaze is only in 4.16 .

Rob