Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
References: <20210208145818.395353822@linuxfoundation.org>
 <20210208145820.464727041@linuxfoundation.org>
User-agent: mu4e 1.4.10; emacs 27.1
From:   Thiago Jung Bauermann <bauerman@linux.ibm.com>
To:     Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc:     linux-kernel@vger.kernel.org, stable@vger.kernel.org,
        Roman Gushchin <guro@fb.com>,
        Mike Rapoport <rppt@linux.ibm.com>,
        Joonsoo Kim <iamjoonsoo.kim@lge.com>,
        Michal Hocko <mhocko@kernel.org>,
        Rik van Riel <riel@surriel.com>,
        Wonhyuk Yang <vvghjk1234@gmail.com>,
        Andrew Morton <akpm@linux-foundation.org>,
        Linus Torvalds <torvalds@linux-foundation.org>,
        Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.10 051/120] memblock: do not start bottom-up
 allocations with kernel_end
In-reply-to: <20210208145820.464727041@linuxfoundation.org>
Date:   Tue, 09 Feb 2021 12:07:57 -0300
Message-ID: <875z31th2q.fsf@manicouagan.localdomain>
MIME-Version: 1.0
Content-Type: text/plain
Precedence: bulk


Greg Kroah-Hartman <gregkh@linuxfoundation.org> writes:

> From: Roman Gushchin <guro@fb.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/

-- 
Thiago Jung Bauermann
IBM Linux Technology Center