linux-kernel - Re: [PATCH][v2] mm/hugetlb: early exit from hugetlb_pages_alloc_boot() when max_huge

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 for Android: free password hash cracker in your pocket

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

Message-Id: <20250819155913.93e549fc5bd728c2f9ddacf4@linux-foundation.org>
Date: Tue, 19 Aug 2025 15:59:13 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: David Hildenbrand <david@...hat.com>
Cc: jane.chu@...cle.com, lirongqing <lirongqing@...du.com>,
 muchun.song@...ux.dev, osalvador@...e.de, linux-mm@...ck.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH][v2] mm/hugetlb: early exit from
 hugetlb_pages_alloc_boot() when max_huge_pages=0

On Mon, 18 Aug 2025 09:46:59 +0200 David Hildenbrand <david@...hat.com> wrote:

> >>>    	if (hugetlb_hstate_alloc_pages_specific_nodes(h))
> >>>    		return;
> >>
> >> Looks good.  Could you add stable: ?
> 
> Can you elaborate why you think this is stable material?
> 

To prevent the

> [    3.702280] HugeTLB: allocation took 0ms with hugepage_allocation_threads=32

message when hugetlb pages are disabled.

Yeah, I guess it isn't very important.  I'll destabilize the patch.