From: Aaron Rainbolt <arraybolt3@gmail.com>
To: alx+linux-man@kernel.org
Cc: linux-man@vger.kernel.org
Subject: PR_SET_NO_NEW_PRIVS still in need of three trailing 0L arguments?
Date: Tue, 27 Oct 2026 00:32:29 -0400 [thread overview]
Message-ID: <20261027003229.158e4f7b@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 930 bytes --]
At one point, prctl always required five arguments. At some point
thereafter, it became a variadic function. Some of the PR_*(2const) man
pages recognize it as a variadic function, such as
PR_SET_DUMPABLE(2const), which states that you can use something like
`prctl(PR_SET_DUMPABLE, 1L);` without problems. On the other hand,
PR_SET_NO_NEW_PRIVS(2const) documents the only allowable method of use
as `prctl(PR_SET_NO_NEW_PRIVS, 1L, 0L, 0L, 0L);`, which looks like the
non-variadic form is still being assumed.
Is there some historical reason that three trailing 0L arguments must
or at least should be passed? Or is the manpage simply out of date? I'd
be happy to send patches for this and other prctl functions that are
mistakenly non-variadic if there is a need to. If there is a historical
reason to pass three trailing 0L arguments, maybe that reason could be
documented.
Thanks for your time,
--
Aaron
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next reply other threads:[~2026-10-27 4:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 4:32 Aaron Rainbolt [this message]
2026-10-27 10:59 ` PR_SET_NO_NEW_PRIVS still in need of three trailing 0L arguments? 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=20261027003229.158e4f7b@gmail.com \
--to=arraybolt3@gmail.com \
--cc=alx+linux-man@kernel.org \
--cc=linux-man@vger.kernel.org \
/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