Re: [PATCH 2/5] mm: don't hide potentially null memmap pointer in sparse_remove_one_section

2019-06-17 Thread David Hildenbrand
On 17.06.19 06:36, Alastair D'Silva wrote: > From: Alastair D'Silva > > By adding offset to memmap before passing it in to clear_hwpoisoned_pages, > is hides a potentially null memmap from the null check inside > clear_hwpoisoned_pages. > > This patch passes the offset to clear_hwpoisoned_pages

Re: [PATCH 2/5] mm: don't hide potentially null memmap pointer in sparse_remove_one_section

2019-06-17 Thread Mike Rapoport
On Mon, Jun 17, 2019 at 02:36:28PM +1000, Alastair D'Silva wrote: > From: Alastair D'Silva > > By adding offset to memmap before passing it in to clear_hwpoisoned_pages, > is hides a potentially null memmap from the null check inside > clear_hwpoisoned_pages. > > This patch passes the offset to

[PATCH 2/5] mm: don't hide potentially null memmap pointer in sparse_remove_one_section

2019-06-16 Thread Alastair D'Silva
From: Alastair D'Silva By adding offset to memmap before passing it in to clear_hwpoisoned_pages, is hides a potentially null memmap from the null check inside clear_hwpoisoned_pages. This patch passes the offset to clear_hwpoisoned_pages instead, allowing memmap to successfully peform it's