Re: [PATCH] mm: memblock: do not enforce current limit for memblock_phys* family

[Mike Rapoport]

On October 15, 2019 12:44:23 AM GMT+02:00, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote:
>On Sun, 13 Oct 2019 00:31:01 +0300 Mike Rapoport <rppt@xxxxxxxxxx>
>wrote:
>
>> Until commit 92d12f9544b7 ("memblock: refactor internal allocation
>> functions") the maximal address for memblock allocations was forced
>to
>> memblock.current_limit only for the allocation functions returning
>virtual
>> address. The changes introduced by that commit moved the limit
>enforcement
>> into the allocation core and as a result the allocation functions
>returning
>> physical address also started to limit allocations to
>> memblock.current_limit.
>> 
>> This caused breakage of etnaviv GPU driver:
>> 
>> ...
>>
>
>So I'll add a cc:stable, yes?

Yeah, right. Somehow I've missed that...

-- 
Sincerely yours,
Mike