Re: [PATCH] powerpc: Perform a bounds check in arch_add_memory

2019-09-05 Thread David Hildenbrand
On 04.09.19 07:25, Alastair D'Silva wrote: > On Mon, 2019-09-02 at 09:28 +0200, David Hildenbrand wrote: >> On 02.09.19 01:54, Alastair D'Silva wrote: >>> On Tue, 2019-08-27 at 09:13 +0200, David Hildenbrand wrote: On 27.08.19 08:39, Alastair D'Silva wrote: > On Tue, 2019-08-27 at 08:28

Re: [PATCH] powerpc: Perform a bounds check in arch_add_memory

2019-09-03 Thread Alastair D'Silva
On Mon, 2019-09-02 at 09:28 +0200, David Hildenbrand wrote: > On 02.09.19 01:54, Alastair D'Silva wrote: > > On Tue, 2019-08-27 at 09:13 +0200, David Hildenbrand wrote: > > > On 27.08.19 08:39, Alastair D'Silva wrote: > > > > On Tue, 2019-08-27 at 08:28 +0200, Michal Hocko wrote: > > > > > On Tue

Re: [PATCH] powerpc: Perform a bounds check in arch_add_memory

2019-09-02 Thread David Hildenbrand
On 02.09.19 01:54, Alastair D'Silva wrote: > On Tue, 2019-08-27 at 09:13 +0200, David Hildenbrand wrote: >> On 27.08.19 08:39, Alastair D'Silva wrote: >>> On Tue, 2019-08-27 at 08:28 +0200, Michal Hocko wrote: On Tue 27-08-19 15:20:46, Alastair D'Silva wrote: > From: Alastair D'Silva

RE: [PATCH] powerpc: Perform a bounds check in arch_add_memory

2019-09-01 Thread Alastair D'Silva
On Tue, 2019-08-27 at 09:13 +0200, David Hildenbrand wrote: > On 27.08.19 08:39, Alastair D'Silva wrote: > > On Tue, 2019-08-27 at 08:28 +0200, Michal Hocko wrote: > > > On Tue 27-08-19 15:20:46, Alastair D'Silva wrote: > > > > From: Alastair D'Silva > > > > > > > > It is possible for firmware

Re: [PATCH] powerpc: Perform a bounds check in arch_add_memory

2019-08-27 Thread Michal Hocko
On Tue 27-08-19 16:39:56, Alastair D'Silva wrote: > On Tue, 2019-08-27 at 08:28 +0200, Michal Hocko wrote: > > On Tue 27-08-19 15:20:46, Alastair D'Silva wrote: > > > From: Alastair D'Silva > > > > > > It is possible for firmware to allocate memory ranges outside > > > the range of physical

Re: [PATCH] powerpc: Perform a bounds check in arch_add_memory

2019-08-27 Thread David Hildenbrand
On 27.08.19 08:39, Alastair D'Silva wrote: > On Tue, 2019-08-27 at 08:28 +0200, Michal Hocko wrote: >> On Tue 27-08-19 15:20:46, Alastair D'Silva wrote: >>> From: Alastair D'Silva >>> >>> It is possible for firmware to allocate memory ranges outside >>> the range of physical memory that we

Re: [PATCH] powerpc: Perform a bounds check in arch_add_memory

2019-08-27 Thread Alastair D'Silva
On Tue, 2019-08-27 at 08:28 +0200, Michal Hocko wrote: > On Tue 27-08-19 15:20:46, Alastair D'Silva wrote: > > From: Alastair D'Silva > > > > It is possible for firmware to allocate memory ranges outside > > the range of physical memory that we support (MAX_PHYSMEM_BITS). > > Doesn't that count

Re: [PATCH] powerpc: Perform a bounds check in arch_add_memory

2019-08-27 Thread Michal Hocko
On Tue 27-08-19 15:20:46, Alastair D'Silva wrote: > From: Alastair D'Silva > > It is possible for firmware to allocate memory ranges outside > the range of physical memory that we support (MAX_PHYSMEM_BITS). Doesn't that count as a FW bug? Do you have any evidence of that in the field? Just

[PATCH] powerpc: Perform a bounds check in arch_add_memory

2019-08-26 Thread Alastair D'Silva
From: Alastair D'Silva It is possible for firmware to allocate memory ranges outside the range of physical memory that we support (MAX_PHYSMEM_BITS). This patch adds a bounds check to ensure that any hotplugged memory is addressable. Signed-off-by: Alastair D'Silva --- arch/powerpc/mm/mem.c