Re: [PATCH] lib/genalloc.c: Avoid de-referencing NULL pool

2019-06-10 Thread Florian Fainelli
On 6/10/19 3:03 PM, Florian Fainelli wrote: > On 6/10/19 2:51 PM, Andrew Morton wrote: >> On Fri, 7 Jun 2019 16:43:31 -0700 Florian Fainelli >> wrote: >> >>> With architectures allowing the kernel to be placed almost arbitrarily >>> in memory (e.g.: ARM64), it is possible to have the kernel

Re: [PATCH] lib/genalloc.c: Avoid de-referencing NULL pool

2019-06-10 Thread Florian Fainelli
On 6/10/19 2:51 PM, Andrew Morton wrote: > On Fri, 7 Jun 2019 16:43:31 -0700 Florian Fainelli > wrote: > >> With architectures allowing the kernel to be placed almost arbitrarily >> in memory (e.g.: ARM64), it is possible to have the kernel resides at >> physical addresses above 4GB, resulting

Re: [PATCH] lib/genalloc.c: Avoid de-referencing NULL pool

2019-06-10 Thread Andrew Morton
On Fri, 7 Jun 2019 16:43:31 -0700 Florian Fainelli wrote: > With architectures allowing the kernel to be placed almost arbitrarily > in memory (e.g.: ARM64), it is possible to have the kernel resides at > physical addresses above 4GB, resulting in neither the default CMA area, > nor the atomic

[PATCH] lib/genalloc.c: Avoid de-referencing NULL pool

2019-06-07 Thread Florian Fainelli
With architectures allowing the kernel to be placed almost arbitrarily in memory (e.g.: ARM64), it is possible to have the kernel resides at physical addresses above 4GB, resulting in neither the default CMA area, nor the atomic pool from successfully allocating. This does not prevent specific