linux-kernel - Re: [PATCH 5.10 051/120] memblock: do not start bottom-up allocations with kernel

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, 9 Feb 2021 20:10:00 +0100
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Thiago Jung Bauermann <bauerman@...ux.ibm.com>
Cc:     linux-kernel@...r.kernel.org, stable@...r.kernel.org,
        Roman Gushchin <guro@...com>,
        Mike Rapoport <rppt@...ux.ibm.com>,
        Joonsoo Kim <iamjoonsoo.kim@....com>,
        Michal Hocko <mhocko@...nel.org>,
        Rik van Riel <riel@...riel.com>,
        Wonhyuk Yang <vvghjk1234@...il.com>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Sasha Levin <sashal@...nel.org>
Subject: Re: [PATCH 5.10 051/120] memblock: do not start bottom-up
 allocations with kernel_end

On Tue, Feb 09, 2021 at 12:07:57PM -0300, Thiago Jung Bauermann wrote:
> 
> Greg Kroah-Hartman <gregkh@...uxfoundation.org> writes:
> 
> > From: Roman Gushchin <guro@...com>
> >
> > [ Upstream commit 2dcb3964544177c51853a210b6ad400de78ef17d ]
> >
> > With kaslr the kernel image is placed at a random place, so starting the
> > bottom-up allocation with the kernel_end can result in an allocation
> > failure and a warning like this one:
> 
> Not sure if this is ready for stable yet (including stable branches 4.19
> and 5.4), since it seems to uncover latent bugs in x86 early memory
> reservation. I asked about this issue here:
> 
> https://lore.kernel.org/lkml/87ft26yuwg.fsf@manicouagan.localdomain/

If there are fixes for this that get merged, please make sure they get
tagged properly to go to the stable trees as well.

thanks,

greg k-h