On 29.08.19 05:51, Alastair D'Silva wrote:
> There is no possibility for memmap to be NULL in the current
> codebase.
> 
> This check was added in commit 95a4774d055c ("memory-hotplug:
> update mce_bad_pages when removing the memory")
> where memmap was originally inited to NULL, and only conditionally
> given a value.
> 
> The code that could have passed a NULL has been removed, so there
> is no longer a possibility that memmap can be NULL.
> 
> Signed-off-by: Alastair D'Silva <[email protected]>
> ---
>  mm/sparse.c | 3 ---
>  1 file changed, 3 deletions(-)
> 
> diff --git a/mm/sparse.c b/mm/sparse.c
> index 78979c142b7d..9f7e3682cdcb 100644
> --- a/mm/sparse.c
> +++ b/mm/sparse.c
> @@ -754,9 +754,6 @@ static void clear_hwpoisoned_pages(struct page *memmap, 
> int nr_pages)
>  {
>       int i;
>  
> -     if (!memmap)
> -             return;
> -
>       /*
>        * A further optimization is to have per section refcounted
>        * num_poisoned_pages.  But that would need more space per memmap, so
> 

Reviewed-by: David Hildenbrand <[email protected]>

-- 

Thanks,

David / dhildenb

Reply via email to