public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Helge Kreutzmann <debian@helgefjell.de>
To: Alejandro Colomar <alx@kernel.org>
Cc: mario.blaettermann@gmail.com, linux-man@vger.kernel.org
Subject: Re: Issue in man page PR_SET_SECUREBITS.2const
Date: Mon, 25 Aug 2025 16:11:01 +0000	[thread overview]
Message-ID: <aKyLFcafAbwaaQCH@meinfjell.helgefjelltest.de> (raw)
In-Reply-To: <lnh4f63q5onlj54wt7qg76unbcvu5apinualih4byiatrfvjpv@5r53xpupbjws>

[-- Attachment #1: Type: text/plain, Size: 2084 bytes --]

Hello Alejandro,
Am Sun, Aug 24, 2025 at 09:21:39PM +0200 schrieb Alejandro Colomar:
> 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:

Yes, sorry.

> 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?

This I cannot judge on, I just see the reference to "malloc" in the
text and hence the question, if this should be turned into a
reference. If malloc_hook(3) is better, than of coures it should be
used.

> Cheers,
> Alex
> 
> > 
> > "Setting this flag provides a method for disabling transparent huge pages for "
> > "jobs where the code cannot be modified, and using a malloc hook with "
> > "B<madvise>(2)  is not an option (i.e., statically allocated data).  The "
> > "setting of the \"THP disable\" flag is inherited by a child created via "
> > "B<fork>(2)  and is preserved across B<execve>(2)."
> 
> -- 
> <https://www.alejandro-colomar.es/>

Greetings

          Helge

-- 
      Dr. Helge Kreutzmann                     debian@helgefjell.de
           Dipl.-Phys.                   http://www.helgefjell.de/debian.php
        64bit GNU powered                     gpg signed mail preferred
           Help keep free software "libre": http://www.ffii.de/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2025-08-25 16:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-24 14:48 Issue in man page PR_SET_SECUREBITS.2const Helge Kreutzmann
2025-08-24 19:21 ` Alejandro Colomar
2025-08-25 16:11   ` Helge Kreutzmann [this message]
2025-08-25 17:52   ` Carlos O'Donell
2025-08-25 19:41     ` Alejandro Colomar
2025-08-25 20:00       ` Carlos O'Donell
2025-08-31  9:19         ` Alejandro Colomar
  -- strict thread matches above, loose matches on Subject: below --
2025-08-24 14:48 Helge Kreutzmann
2025-08-24 19:25 ` Alejandro Colomar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aKyLFcafAbwaaQCH@meinfjell.helgefjelltest.de \
    --to=debian@helgefjell.de \
    --cc=alx@kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=mario.blaettermann@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox