Re: [PATCH] nommu: remove __GFP_HIGHMEM in vmalloc/vzalloc

[David Hildenbrand <david@redhat.com>]

On 03.05.21 14:44, Chen Li wrote:
> 
>  From mm/nommu.c:
> void *__vmalloc(unsigned long size, gfp_t gfp_mask)
> {
> 	/*
> 	 *  You can't specify __GFP_HIGHMEM with kmalloc() since kmalloc()
> 	 * returns only a logical address.
> 	 */
> 	return kmalloc(size, (gfp_mask | __GFP_COMP) & ~__GFP_HIGHMEM);
> }
> 
> nommu's __vmalloc just uses kmalloc internally and elimitates __GFP_HIGHMEM,
> so it makes no sense to add __GFP_HIGHMEM for nommu's vmalloc/vzalloc.
> 
> Signed-off-by: Chen Li <chenli@uniontech.com>
> ---
>   mm/nommu.c | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/mm/nommu.c b/mm/nommu.c
> index 5c9ab799c0e6..339a2f2eb1aa 100644
> --- a/mm/nommu.c
> +++ b/mm/nommu.c
> @@ -233,7 +233,7 @@ long vwrite(char *buf, char *addr, unsigned long count)
>    */
>   void *vmalloc(unsigned long size)
>   {
> -       return __vmalloc(size, GFP_KERNEL | __GFP_HIGHMEM);
> +       return __vmalloc(size, GFP_KERNEL);
>   }
>   EXPORT_SYMBOL(vmalloc);
>   
> @@ -251,7 +251,7 @@ EXPORT_SYMBOL(vmalloc);
>    */
>   void *vzalloc(unsigned long size)
>   {
> -	return __vmalloc(size, GFP_KERNEL | __GFP_HIGHMEM | __GFP_ZERO);
> +	return __vmalloc(size, GFP_KERNEL | __GFP_ZERO);
>   }
>   EXPORT_SYMBOL(vzalloc);
>   
> 

Reviewed-by: David Hildenbrand <david@redhat.com>

-- 
Thanks,

David / dhildenb