linux-kernel - Re: [PATCH] mips: Remove __GFP

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <aS1i1HrCrLhj_Gxx@alpha.franken.de>
Date: Mon, 1 Dec 2025 10:41:40 +0100
From: Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To: "Vishal Moola (Oracle)" <vishal.moola@...il.com>
Cc: linux-mips@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mips: Remove __GFP_HIGHMEM masking

On Fri, Nov 07, 2025 at 03:27:58PM -0800, Vishal Moola (Oracle) wrote:
> Remove unnecessary __GFP_HIGHMEM masking, which was introduced with
> commit 3e14fb19ad7c ("mips: convert various functions to use ptdescs").
> GFP_KERNEL doesn't contain __GFP_HIGHMEM.
> 
> Signed-off-by: Vishal Moola (Oracle) <vishal.moola@...il.com>
> ---
>  arch/mips/include/asm/pgalloc.h | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/arch/mips/include/asm/pgalloc.h b/arch/mips/include/asm/pgalloc.h
> index 942af87f1cdd..7a04381efa0b 100644
> --- a/arch/mips/include/asm/pgalloc.h
> +++ b/arch/mips/include/asm/pgalloc.h
> @@ -81,8 +81,7 @@ static inline pmd_t *pmd_alloc_one(struct mm_struct *mm, unsigned long address)
>  static inline pud_t *pud_alloc_one(struct mm_struct *mm, unsigned long address)
>  {
>  	pud_t *pud;
> -	struct ptdesc *ptdesc = pagetable_alloc(GFP_KERNEL & ~__GFP_HIGHMEM,
> -			PUD_TABLE_ORDER);
> +	struct ptdesc *ptdesc = pagetable_alloc(GFP_KERNEL, PUD_TABLE_ORDER);
>  
>  	if (!ptdesc)
>  		return NULL;
> -- 
> 2.51.1

applied to mips-next.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]