Re: Issue in man page PR_SET_SECUREBITS.2const

[Carlos O'Donell <carlos@redhat.com>]

On 8/24/25 3:21 PM, Alejandro Colomar wrote:
> Hi Helge,
> 
>> Subject: Re: Issue in man page PR_SET_SECUREBITS.2const
> 
> You probably meant PR_SET_THP_DISABLE.2const.  The text you quoted is
> there:
> 
> 	$ grep -rn THP.disable
> 	man/man2const/PR_SET_THP_DISABLE.2const:9:set the state of the "THP disable" flag for the calling thread
> 	man/man2const/PR_SET_THP_DISABLE.2const:21:Set the state of the "THP disable" flag for the calling thread.
> 	man/man2const/PR_SET_THP_DISABLE.2const:32:The setting of the "THP disable" flag is inherited by a child created via
> 	man/man2const/PR_GET_THP_DISABLE.2const:9:get the state of the "THP disable" flag for the calling thread
> 	man/man2const/PR_GET_THP_DISABLE.2const:22:the "THP disable" flag for the calling thread:
> 
> On Sun, Aug 24, 2025 at 02:48:48PM +0000, Helge Kreutzmann wrote:
>> Without further ado, the following was found:
>>
>> Issue:    malloc → B<malloc>(3) ?
> 
> Maybe, but we should probably add a reference to malloc_hook(3) instead?

In a modern system you care about malloc not malloc_hook.

The hooks have been removed and glibc has directly integrated THP usage in malloc instead.

https://sourceware.org/glibc/manual/2.42/html_node/Memory-Allocation-Tunables.html

Tunable: glibc.malloc.hugetlb

-- 
Cheers,
Carlos.