linux-kernel - Re: [PATCH] mips: 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] [day] [month] [year] [list]

Message-Id: <20180809123441.GA3264@rapoport-lnx>
Date:   Thu, 9 Aug 2018 15:34:42 +0300
From:   Mike Rapoport <rppt@...ux.vnet.ibm.com>
To:     Paul Burton <paul.burton@...s.com>
Cc:     "Fancer's opinion" <fancer.lancer@...il.com>,
        Linux-MIPS <linux-mips@...ux-mips.org>,
        Ralf Baechle <ralf@...ux-mips.org>,
        James Hogan <jhogan@...nel.org>,
        Huacai Chen <chenhc@...ote.com>,
        Michal Hocko <mhocko@...nel.org>, linux-mm@...ck.org,
        linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] mips: switch to NO_BOOTMEM

On Wed, Aug 08, 2018 at 02:42:15PM -0700, Paul Burton wrote:
> Hi Sergey & Mike,
> 
> On Thu, Aug 09, 2018 at 12:30:03AM +0300, Fancer's opinion wrote:
> > Hello Mike,
> > I haven't read your patch text yet. I am waiting for the subsystem
> > maintainers response at least
> > about the necessity to have this type of changes being merged into the
> > sources (I mean
> > memblock/no-bootmem alteration). If they find it pointless (although I
> > would strongly disagree), then
> > nothing to discuss. Otherwise we can come up with a solution.
> > 
> > -Sergey
> 
> I'm all for dropping bootmem.
> 
> It's too late for something this invasive in 4.19, but I'd love to get
> it into 4.20.

I can resend my patch once merge window is closed. We can then apply
additional changes Sergey has done in his set on top.

> Thanks,
>     Paul
> 

-- 
Sincerely yours,
Mike.