man2/prctl.2

   1 .\" Copyright (C) 1998 Andries Brouwer (aeb@cwi.nl)
   2 .\" and Copyright (C) 2002, 2006, 2008, 2012, 2013 Michael Kerrisk <mtk.manpages@gmail.com>
   3 .\" and Copyright Guillem Jover <guillem@hadrons.org>
   4 .\" and Copyright (C) 2014 Dave Hansen / Intel
   5 .\"
   6 .\" %%%LICENSE_START(VERBATIM)
   7 .\" Permission is granted to make and distribute verbatim copies of this
   8 .\" manual provided the copyright notice and this permission notice are
   9 .\" preserved on all copies.
  10 .\"
  11 .\" Permission is granted to copy and distribute modified versions of this
  12 .\" manual under the conditions for verbatim copying, provided that the
  13 .\" entire resulting derived work is distributed under the terms of a
  14 .\" permission notice identical to this one.
  15 .\"
  16 .\" Since the Linux kernel and libraries are constantly changing, this
  17 .\" manual page may be incorrect or out-of-date.  The author(s) assume no
  18 .\" responsibility for errors or omissions, or for damages resulting from
  19 .\" the use of the information contained herein.  The author(s) may not
  20 .\" have taken the same level of care in the production of this manual,
  21 .\" which is licensed free of charge, as they might when working
  22 .\" professionally.
  23 .\"
  24 .\" Formatted or processed versions of this manual, if unaccompanied by
  25 .\" the source, must acknowledge the copyright and authors of this work.
  26 .\" %%%LICENSE_END
  27 .\"
  28 .\" Modified Thu Nov 11 04:19:42 MET 1999, aeb: added PR_GET_PDEATHSIG
  29 .\" Modified 27 Jun 02, Michael Kerrisk
  30 .\"     Added PR_SET_DUMPABLE, PR_GET_DUMPABLE,
  31 .\"     PR_SET_KEEPCAPS, PR_GET_KEEPCAPS
  32 .\" Modified 2006-08-30 Guillem Jover <guillem@hadrons.org>
  33 .\"     Updated Linux versions where the options where introduced.
  34 .\"     Added PR_SET_TIMING, PR_GET_TIMING, PR_SET_NAME, PR_GET_NAME,
  35 .\"     PR_SET_UNALIGN, PR_GET_UNALIGN, PR_SET_FPEMU, PR_GET_FPEMU,
  36 .\"     PR_SET_FPEXC, PR_GET_FPEXC
  37 .\" 2008-04-29 Serge Hallyn, Document PR_CAPBSET_READ and PR_CAPBSET_DROP
  38 .\" 2008-06-13 Erik Bosman, <ejbosman@cs.vu.nl>
  39 .\"     Document PR_GET_TSC and PR_SET_TSC.
  40 .\" 2008-06-15 mtk, Document PR_SET_SECCOMP, PR_GET_SECCOMP
  41 .\" 2009-10-03 Andi Kleen, document PR_MCE_KILL
  42 .\" 2012-04 Cyrill Gorcunov, Document PR_SET_MM
  43 .\" 2012-04-25 Michael Kerrisk, Document PR_TASK_PERF_EVENTS_DISABLE and
  44 .\"                             PR_TASK_PERF_EVENTS_ENABLE
  45 .\" 2012-09-20 Kees Cook, update PR_SET_SECCOMP for mode 2
  46 .\" 2012-09-20 Kees Cook, document PR_SET_NO_NEW_PRIVS, PR_GET_NO_NEW_PRIVS
  47 .\" 2012-10-25 Michael Kerrisk, Document PR_SET_TIMERSLACK and
  48 .\"                             PR_GET_TIMERSLACK
  49 .\" 2013-01-10 Kees Cook, document PR_SET_PTRACER
  50 .\" 2012-02-04 Michael Kerrisk, document PR_{SET,GET}_CHILD_SUBREAPER
  51 .\" 2014-11-10 Dave Hansen, document PR_MPX_{EN,DIS}ABLE_MANAGEMENT
  52 .\"
  53 .\"
  54 .TH PRCTL 2 2018-02-02 "Linux" "Linux Programmer's Manual"
  55 .SH NAME
  56 prctl \- operations on a process
  57 .SH SYNOPSIS
  58 .nf
  59 .B #include <sys/prctl.h>
  60 .PP
  61 .BI "int prctl(int " option ", unsigned long " arg2 ", unsigned long " arg3 ,
  62 .BI "          unsigned long " arg4 ", unsigned long " arg5 );
  63 .fi
  64 .SH DESCRIPTION
  65 .BR prctl ()
  66 is called with a first argument describing what to do
  67 (with values defined in \fI<linux/prctl.h>\fP), and further
  68 arguments with a significance depending on the first one.
  69 The first argument can be:
  70 .\"
  71 .TP
  72 .BR PR_CAP_AMBIENT " (since Linux 4.3)"
  73 .\" commit 58319057b7847667f0c9585b9de0e8932b0fdb08
  74 Reads or changes the ambient capability set of the calling thread,
  75 according to the value of
  76 .IR arg2 ,
  77 which must be one of the following:
  78 .RS
  79 .\"
  80 .TP
  81 .B PR_CAP_AMBIENT_RAISE
  82 The capability specified in
  83 .I arg3
  84 is added to the ambient set.
  85 The specified capability must already be present in
  86 both the permitted and the inheritable sets of the process.
  87 This operation is not permitted if the
  88 .B SECBIT_NO_CAP_AMBIENT_RAISE
  89 securebit is set.
  90 .TP
  91 .B PR_CAP_AMBIENT_LOWER
  92 The capability specified in
  93 .I arg3
  94 is removed from the ambient set.
  95 .TP
  96 .B PR_CAP_AMBIENT_IS_SET
  97 The
  98 .BR prctl ()
  99 call returns 1 if the capability in
 100 .I arg3
 101 is in the ambient set and 0 if it is not.
 102 .TP
 103 .BR PR_CAP_AMBIENT_CLEAR_ALL
 104 All capabilities will be removed from the ambient set.
 105 This operation requires setting
 106 .I arg3
 107 to zero.
 108 .RE
 109 .IP
 110 In all of the above operations,
 111 .I arg4
 112 and
 113 .I arg5
 114 must be specified as 0.
 115 .IP
 116 Higher-level interfaces layered on top of the above operations are
 117 provided in the
 118 .BR libcap (3)
 119 library in the form of
 120 .BR cap_get_ambient (3),
 121 .BR cap_set_ambient (3),
 122 and
 123 .BR cap_reset_ambient (3).
 124 .TP
 125 .BR PR_CAPBSET_READ " (since Linux 2.6.25)"
 126 Return (as the function result) 1 if the capability specified in
 127 .I arg2
 128 is in the calling thread's capability bounding set,
 129 or 0 if it is not.
 130 (The capability constants are defined in
 131 .IR <linux/capability.h> .)
 132 The capability bounding set dictates
 133 whether the process can receive the capability through a
 134 file's permitted capability set on a subsequent call to
 135 .BR execve (2).
 136 .IP
 137 If the capability specified in
 138 .I arg2
 139 is not valid, then the call fails with the error
 140 .BR EINVAL .
 141 .IP
 142 A higher-level interface layered on top of this operation is provided in the
 143 .BR libcap (3)
 144 library in the form of
 145 .BR cap_get_bound (3).
 146 .TP
 147 .BR PR_CAPBSET_DROP " (since Linux 2.6.25)"
 148 If the calling thread has the
 149 .B CAP_SETPCAP
 150 capability within its user namespace, then drop the capability specified by
 151 .I arg2
 152 from the calling thread's capability bounding set.
 153 Any children of the calling thread will inherit the newly
 154 reduced bounding set.
 155 .IP
 156 The call fails with the error:
 157 .B EPERM
 158 if the calling thread does not have the
 159 .BR CAP_SETPCAP ;
 160 .BR EINVAL
 161 if
 162 .I arg2
 163 does not represent a valid capability; or
 164 .BR EINVAL
 165 if file capabilities are not enabled in the kernel,
 166 in which case bounding sets are not supported.
 167 .IP
 168 A higher-level interface layered on top of this operation is provided in the
 169 .BR libcap (3)
 170 library in the form of
 171 .BR cap_drop_bound (3).
 172 .TP
 173 .BR PR_SET_CHILD_SUBREAPER " (since Linux 3.4)"
 174 .\" commit ebec18a6d3aa1e7d84aab16225e87fd25170ec2b
 175 If
 176 .I arg2
 177 is nonzero,
 178 set the "child subreaper" attribute of the calling process;
 179 if
 180 .I arg2
 181 is zero, unset the attribute.
 182 .IP
 183 A subreaper fulfills the role of
 184 .BR init (1)
 185 for its descendant processes.
 186 When a process becomes orphaned
 187 (i.e., its immediate parent terminates)
 188 then that process will be reparented to
 189 the nearest still living ancestor subreaper.
 190 Subsequently, calls to
 191 .BR getppid ()
 192 in the orphaned process will now return the PID of the subreaper process,
 193 and when the orphan terminates, it is the subreaper process that
 194 will receive a
 195 .BR SIGCHLD
 196 signal and will be able to
 197 .BR wait (2)
 198 on the process to discover its termination status.
 199 .IP
 200 The setting of "child subreaper" attribute
 201 is not inherited by children created by
 202 .BR fork (2)
 203 and
 204 .BR clone (2).
 205 The setting is preserved across
 206 .BR execve (2).
 207 .IP
 208 Establishing a subreaper process is useful in session management frameworks
 209 where a hierarchical group of processes is managed by a subreaper process
 210 that needs to be informed when one of the processes\(emfor example,
 211 a double-forked daemon\(emterminates
 212 (perhaps so that it can restart that process).
 213 Some
 214 .BR init (1)
 215 frameworks (e.g.,
 216 .BR systemd (1))
 217 employ a subreaper process for similar reasons.
 218 .TP
 219 .BR PR_GET_CHILD_SUBREAPER " (since Linux 3.4)"
 220 Return the "child subreaper" setting of the caller,
 221 in the location pointed to by
 222 .IR "(int\ *) arg2" .
 223 .TP
 224 .BR PR_SET_DUMPABLE " (since Linux 2.3.20)"
 225 Set the state of the "dumpable" flag,
 226 which determines whether core dumps are produced for the calling process
 227 upon delivery of a signal whose default behavior is to produce a core dump.
 228 .IP
 229 In kernels up to and including 2.6.12,
 230 .I arg2
 231 must be either 0
 232 .RB ( SUID_DUMP_DISABLE ,
 233 process is not dumpable) or 1
 234 .RB ( SUID_DUMP_USER ,
 235 process is dumpable).
 236 Between kernels 2.6.13 and 2.6.17,
 237 .\" commit abf75a5033d4da7b8a7e92321d74021d1fcfb502
 238 the value 2 was also permitted,
 239 which caused any binary which normally would not be dumped
 240 to be dumped readable by root only;
 241 for security reasons, this feature has been removed.
 242 .\" See http://marc.theaimsgroup.com/?l=linux-kernel&m=115270289030630&w=2
 243 .\" Subject:    Fix prctl privilege escalation (CVE-2006-2451)
 244 .\" From:       Marcel Holtmann <marcel () holtmann ! org>
 245 .\" Date:       2006-07-12 11:12:00
 246 (See also the description of
 247 .I /proc/sys/fs/\:suid_dumpable
 248 in
 249 .BR proc (5).)
 250 .IP
 251 Normally, this flag is set to 1.
 252 However, it is reset to the current value contained in the file
 253 .IR /proc/sys/fs/\:suid_dumpable
 254 (which by default has the value 0),
 255 in the following circumstances:
 256 .\" See kernel/cred.c::commit_creds() (Linux 3.18 sources)
 257 .RS
 258 .IP * 3
 259 The process's effective user or group ID is changed.
 260 .IP *
 261 The process's filesystem user or group ID is changed (see
 262 .BR credentials (7)).
 263 .IP *
 264 The process executes
 265 .RB ( execve (2))
 266 a set-user-ID or set-group-ID program, resulting in a change
 267 of either the effective user ID or the effective group ID.
 268 .IP *
 269 The process executes
 270 .RB ( execve (2))
 271 a program that has file capabilities (see
 272 .BR capabilities (7)),
 273 .\" See kernel/cred.c::commit_creds()
 274 but only if the permitted capabilities
 275 gained exceed those already permitted for the process.
 276 .\" Also certain namespace operations;
 277 .RE
 278 .IP
 279 Processes that are not dumpable can not be attached via
 280 .BR ptrace (2)
 281 .BR PTRACE_ATTACH ;
 282 see
 283 .BR ptrace (2)
 284 for further details.
 285 .IP
 286 If a process is not dumpable,
 287 the ownership of files in the process's
 288 .IR /proc/[pid]
 289 directory is affected as described in
 290 .BR proc (5).
 291 .TP
 292 .BR PR_GET_DUMPABLE " (since Linux 2.3.20)"
 293 Return (as the function result) the current state of the calling
 294 process's dumpable flag.
 295 .\" Since Linux 2.6.13, the dumpable flag can have the value 2,
 296 .\" but in 2.6.13 PR_GET_DUMPABLE simply returns 1 if the dumpable
 297 .\" flags has a nonzero value.  This was fixed in 2.6.14.
 298 .TP
 299 .BR PR_SET_ENDIAN " (since Linux 2.6.18, PowerPC only)"
 300 Set the endian-ness of the calling process to the value given
 301 in \fIarg2\fP, which should be one of the following:
 302 .\" Respectively 0, 1, 2
 303 .BR PR_ENDIAN_BIG ,
 304 .BR PR_ENDIAN_LITTLE ,
 305 or
 306 .B PR_ENDIAN_PPC_LITTLE
 307 (PowerPC pseudo little endian).
 308 .TP
 309 .BR PR_GET_ENDIAN " (since Linux 2.6.18, PowerPC only)"
 310 Return the endian-ness of the calling process,
 311 in the location pointed to by
 312 .IR "(int\ *) arg2" .
 313 .TP
 314 .BR PR_SET_FP_MODE " (since Linux 4.0, only on MIPS)"
 315 .\" commit 9791554b45a2acc28247f66a5fd5bbc212a6b8c8
 316 On the MIPS architecture,
 317 user-space code can be built using an ABI which permits linking
 318 with code that has more restrictive floating-point (FP) requirements.
 319 For example, user-space code may be built to target the O32 FPXX ABI
 320 and linked with code built for either one of the more restrictive
 321 FP32 or FP64 ABIs.
 322 When more restrictive code is linked in,
 323 the overall requirement for the process is to use the more
 324 restrictive floating-point mode.
 325 .IP
 326 Because the kernel has no means of knowing in advance
 327 which mode the process should be executed in,
 328 and because these restrictions can
 329 change over the lifetime of the process, the
 330 .B PR_SET_FP_MODE
 331 operation is provided to allow control of the floating-point mode
 332 from user space.
 333 .IP
 334 .\" https://dmz-portal.mips.com/wiki/MIPS_O32_ABI_-_FR0_and_FR1_Interlinking
 335 The
 336 .I (unsigned int) arg2
 337 argument is a bit mask describing the floating-point mode used:
 338 .RS
 339 .TP
 340 .BR PR_FP_MODE_FR
 341 When this bit is
 342 .I unset
 343 (so called
 344 .BR FR=0 " or " FR0
 345 mode), the 32 floating-point registers are 32 bits wide,
 346 and 64-bit registers are represented as a pair of registers
 347 (even- and odd- numbered,
 348 with the even-numbered register containing the lower 32 bits,
 349 and the odd-numbered register containing the higher 32 bits).
 350 .IP
 351 When this bit is
 352 .I set
 353 (on supported hardware),
 354 the 32 floating-point registers are 64 bits wide (so called
 355 .BR FR=1 " or " FR1
 356 mode).
 357 Note that modern MIPS implementations (MIPS R6 and newer) support
 358 .B FR=1
 359 mode only.
 360 .IP
 361 .IP
 362 Applications that use the O32 FP32 ABI can operate only when this bit is
 363 .I unset
 364 .RB ( FR=0 ;
 365 or they can be used with FRE enabled, see below).
 366 Applications that use the O32 FP64 ABI
 367 (and the O32 FP64A ABI, which exists to
 368 provide the ability to operate with existing FP32 code; see below)
 369 can operate only when this bit is
 370 .I set
 371 .RB ( FR=1 ).
 372 Applications that use the O32 FPXX ABI can operate with either
 373 .BR FR=0
 374 or
 375 .BR FR=1 .
 376 .TP
 377 .BR PR_FP_MODE_FRE
 378 Enable emulation of 32-bit floating-point mode.
 379 When this mode is enabled,
 380 it emulates 32-bit floating-point operations
 381 by raising a reserved-instruction exception
 382 on every instruction that uses 32-bit formats and
 383 the kernel then handles the instruction in software.
 384 (The problem lies in the discrepancy of handling odd-numbered registers
 385 which are the high 32 bits of 64-bit registers with even numbers in
 386 .B FR=0
 387 mode and the lower 32-bit parts of odd-numbered 64-bit registers in
 388 .B FR=1
 389 mode.)
 390 Enabling this bit is necessary when code with the O32 FP32 ABI should operate
 391 with code with compatible the O32 FPXX or O32 FP64A ABIs (which require
 392 .B FR=1
 393 FPU mode) or when it is executed on newer hardware (MIPS R6 onwards)
 394 which lacks
 395 .B FR=0
 396 mode support when a binary with the FP32 ABI is used.
 397 .IP
 398 Note that this mode makes sense only when the FPU is in 64-bit mode
 399 .RB ( FR=1 ).
 400 .IP
 401 Note that the use of emulation inherently has a significant performance hit
 402 and should be avoided if possible.
 403 .RE
 404 .IP
 405 In the N32/N64 ABI, 64-bit floating-point mode is always used,
 406 so FPU emulation is not required and the FPU always operates in
 407 .B FR=1
 408 mode.
 409 .IP
 410 This option is mainly intended for use by the dynamic linker
 411 .RB ( ld.so (8)).
 412 .IP
 413 The arguments
 414 .IR arg3 ,
 415 .IR arg4 ,
 416 and
 417 .IR arg5
 418 are ignored.
 419 .TP
 420 .BR PR_GET_FP_MODE " (since Linux 4.0, only on MIPS)"
 421 Get the current floating-point mode (see the description of
 422 .B PR_SET_FP_MODE
 423 for details).
 424 .IP
 425 On success,
 426 the call returns a bit mask which represents the current floating-point mode.
 427 .IP
 428 The arguments
 429 .IR arg2 ,
 430 .IR arg3 ,
 431 .IR arg4 ,
 432 and
 433 .IR arg5
 434 are ignored.
 435 .TP
 436 .BR PR_SET_FPEMU " (since Linux 2.4.18, 2.5.9, only on ia64)"
 437 Set floating-point emulation control bits to \fIarg2\fP.
 438 Pass
 439 .B PR_FPEMU_NOPRINT
 440 to silently emulate floating-point operation accesses, or
 441 .B PR_FPEMU_SIGFPE
 442 to not emulate floating-point operations and send
 443 .B SIGFPE
 444 instead.
 445 .TP
 446 .BR PR_GET_FPEMU " (since Linux 2.4.18, 2.5.9, only on ia64)"
 447 Return floating-point emulation control bits,
 448 in the location pointed to by
 449 .IR "(int\ *) arg2" .
 450 .TP
 451 .BR PR_SET_FPEXC " (since Linux 2.4.21, 2.5.32, only on PowerPC)"
 452 Set floating-point exception mode to \fIarg2\fP.
 453 Pass \fBPR_FP_EXC_SW_ENABLE\fP to use FPEXC for FP exception enables,
 454 \fBPR_FP_EXC_DIV\fP for floating-point divide by zero,
 455 \fBPR_FP_EXC_OVF\fP for floating-point overflow,
 456 \fBPR_FP_EXC_UND\fP for floating-point underflow,
 457 \fBPR_FP_EXC_RES\fP for floating-point inexact result,
 458 \fBPR_FP_EXC_INV\fP for floating-point invalid operation,
 459 \fBPR_FP_EXC_DISABLED\fP for FP exceptions disabled,
 460 \fBPR_FP_EXC_NONRECOV\fP for async nonrecoverable exception mode,
 461 \fBPR_FP_EXC_ASYNC\fP for async recoverable exception mode,
 462 \fBPR_FP_EXC_PRECISE\fP for precise exception mode.
 463 .TP
 464 .BR PR_GET_FPEXC " (since Linux 2.4.21, 2.5.32, only on PowerPC)"
 465 Return floating-point exception mode,
 466 in the location pointed to by
 467 .IR "(int\ *) arg2" .
 468 .TP
 469 .BR PR_SET_KEEPCAPS " (since Linux 2.2.18)"
 470 Set the state of the calling thread's "keep capabilities" flag.
 471 The effect if this flag is described in
 472 .BR capabilities (7).
 473 .I arg2
 474 must be either 0 (clear the flag)
 475 or 1 (set the flag).
 476 The "keep capabilities" value will be reset to 0 on subsequent calls to
 477 .BR execve (2).
 478 .TP
 479 .BR PR_GET_KEEPCAPS " (since Linux 2.2.18)"
 480 Return (as the function result) the current state of the calling thread's
 481 "keep capabilities" flag.
 482 See
 483 .BR capabilities (7)
 484 for a description of this flag.
 485 .TP
 486 .BR PR_MCE_KILL " (since Linux 2.6.32)"
 487 Set the machine check memory corruption kill policy for the calling thread.
 488 If
 489 .I arg2
 490 is
 491 .BR PR_MCE_KILL_CLEAR ,
 492 clear the thread memory corruption kill policy and use the system-wide default.
 493 (The system-wide default is defined by
 494 .IR /proc/sys/vm/memory_failure_early_kill ;
 495 see
 496 .BR proc (5).)
 497 If
 498 .I arg2
 499 is
 500 .BR PR_MCE_KILL_SET ,
 501 use a thread-specific memory corruption kill policy.
 502 In this case,
 503 .I arg3
 504 defines whether the policy is
 505 .I early kill
 506 .RB ( PR_MCE_KILL_EARLY ),
 507 .I late kill
 508 .RB ( PR_MCE_KILL_LATE ),
 509 or the system-wide default
 510 .RB ( PR_MCE_KILL_DEFAULT ).
 511 Early kill means that the thread receives a
 512 .B SIGBUS
 513 signal as soon as hardware memory corruption is detected inside
 514 its address space.
 515 In late kill mode, the process is killed only when it accesses a corrupted page.
 516 See
 517 .BR sigaction (2)
 518 for more information on the
 519 .BR SIGBUS
 520 signal.
 521 The policy is inherited by children.
 522 The remaining unused
 523 .BR prctl ()
 524 arguments must be zero for future compatibility.
 525 .TP
 526 .BR PR_MCE_KILL_GET " (since Linux 2.6.32)"
 527 Return the current per-process machine check kill policy.
 528 All unused
 529 .BR prctl ()
 530 arguments must be zero.
 531 .TP
 532 .BR PR_SET_MM " (since Linux 3.3)"
 533 .\" commit 028ee4be34a09a6d48bdf30ab991ae933a7bc036
 534 Modify certain kernel memory map descriptor fields
 535 of the calling process.
 536 Usually these fields are set by the kernel and dynamic loader (see
 537 .BR ld.so (8)
 538 for more information) and a regular application should not use this feature.
 539 However, there are cases, such as self-modifying programs,
 540 where a program might find it useful to change its own memory map.
 541 .IP
 542 The calling process must have the
 543 .BR CAP_SYS_RESOURCE
 544 capability.
 545 The value in
 546 .I arg2
 547 is one of the options below, while
 548 .I arg3
 549 provides a new value for the option.
 550 The
 551 .I arg4
 552 and
 553 .I arg5
 554 arguments must be zero if unused.
 555 .IP
 556 Before Linux 3.10,
 557 .\" commit 52b3694157e3aa6df871e283115652ec6f2d31e0
 558 this feature is available only if the kernel is built with the
 559 .BR CONFIG_CHECKPOINT_RESTORE
 560 option enabled.
 561 .RS
 562 .TP
 563 .BR PR_SET_MM_START_CODE
 564 Set the address above which the program text can run.
 565 The corresponding memory area must be readable and executable,
 566 but not writable or shareable (see
 567 .BR mprotect (2)
 568 and
 569 .BR mmap (2)
 570 for more information).
 571 .TP
 572 .BR PR_SET_MM_END_CODE
 573 Set the address below which the program text can run.
 574 The corresponding memory area must be readable and executable,
 575 but not writable or shareable.
 576 .TP
 577 .BR PR_SET_MM_START_DATA
 578 Set the address above which initialized and
 579 uninitialized (bss) data are placed.
 580 The corresponding memory area must be readable and writable,
 581 but not executable or shareable.
 582 .TP
 583 .B PR_SET_MM_END_DATA
 584 Set the address below which initialized and
 585 uninitialized (bss) data are placed.
 586 The corresponding memory area must be readable and writable,
 587 but not executable or shareable.
 588 .TP
 589 .BR PR_SET_MM_START_STACK
 590 Set the start address of the stack.
 591 The corresponding memory area must be readable and writable.
 592 .TP
 593 .BR PR_SET_MM_START_BRK
 594 Set the address above which the program heap can be expanded with
 595 .BR brk (2)
 596 call.
 597 The address must be greater than the ending address of
 598 the current program data segment.
 599 In addition, the combined size of the resulting heap and
 600 the size of the data segment can't exceed the
 601 .BR RLIMIT_DATA
 602 resource limit (see
 603 .BR setrlimit (2)).
 604 .TP
 605 .BR PR_SET_MM_BRK
 606 Set the current
 607 .BR brk (2)
 608 value.
 609 The requirements for the address are the same as for the
 610 .BR PR_SET_MM_START_BRK
 611 option.
 612 .PP
 613 The following options are available since Linux 3.5.
 614 .\" commit fe8c7f5cbf91124987106faa3bdf0c8b955c4cf7
 615 .TP
 616 .BR PR_SET_MM_ARG_START
 617 Set the address above which the program command line is placed.
 618 .TP
 619 .BR PR_SET_MM_ARG_END
 620 Set the address below which the program command line is placed.
 621 .TP
 622 .BR PR_SET_MM_ENV_START
 623 Set the address above which the program environment is placed.
 624 .TP
 625 .BR PR_SET_MM_ENV_END
 626 Set the address below which the program environment is placed.
 627 .IP
 628 The address passed with
 629 .BR PR_SET_MM_ARG_START ,
 630 .BR PR_SET_MM_ARG_END ,
 631 .BR PR_SET_MM_ENV_START ,
 632 and
 633 .BR PR_SET_MM_ENV_END
 634 should belong to a process stack area.
 635 Thus, the corresponding memory area must be readable, writable, and
 636 (depending on the kernel configuration) have the
 637 .BR MAP_GROWSDOWN
 638 attribute set (see
 639 .BR mmap (2)).
 640 .TP
 641 .BR PR_SET_MM_AUXV
 642 Set a new auxiliary vector.
 643 The
 644 .I arg3
 645 argument should provide the address of the vector.
 646 The
 647 .I arg4
 648 is the size of the vector.
 649 .TP
 650 .BR PR_SET_MM_EXE_FILE
 651 .\" commit b32dfe377102ce668775f8b6b1461f7ad428f8b6
 652 Supersede the
 653 .IR /proc/pid/exe
 654 symbolic link with a new one pointing to a new executable file
 655 identified by the file descriptor provided in
 656 .I arg3
 657 argument.
 658 The file descriptor should be obtained with a regular
 659 .BR open (2)
 660 call.
 661 .IP
 662 To change the symbolic link, one needs to unmap all existing
 663 executable memory areas, including those created by the kernel itself
 664 (for example the kernel usually creates at least one executable
 665 memory area for the ELF
 666 .IR \.text
 667 section).
 668 .IP
 669 In Linux 4.9 and earlier, the
 670 .\" commit 3fb4afd9a504c2386b8435028d43283216bf588e
 671 .BR PR_SET_MM_EXE_FILE
 672 operation can be performed only once in a process's lifetime;
 673 attempting to perform the operation a second time results in the error
 674 .BR EPERM .
 675 This restriction was enforced for security reasons that were subsequently
 676 deemed specious,
 677 and the restriction was removed in Linux 4.10 because some
 678 user-space applications needed to perform this operation more than once.
 679 .PP
 680 The following options are available since Linux 3.18.
 681 .\" commit f606b77f1a9e362451aca8f81d8f36a3a112139e
 682 .TP
 683 .BR PR_SET_MM_MAP
 684 Provides one-shot access to all the addresses by passing in a
 685 .I struct prctl_mm_map
 686 (as defined in \fI<linux/prctl.h>\fP).
 687 The
 688 .I arg4
 689 argument should provide the size of the struct.
 690 .IP
 691 This feature is available only if the kernel is built with the
 692 .BR CONFIG_CHECKPOINT_RESTORE
 693 option enabled.
 694 .TP
 695 .BR PR_SET_MM_MAP_SIZE
 696 Returns the size of the
 697 .I struct prctl_mm_map
 698 the kernel expects.
 699 This allows user space to find a compatible struct.
 700 The
 701 .I arg4
 702 argument should be a pointer to an unsigned int.
 703 .IP
 704 This feature is available only if the kernel is built with the
 705 .BR CONFIG_CHECKPOINT_RESTORE
 706 option enabled.
 707 .RE
 708 .TP
 709 .BR PR_MPX_ENABLE_MANAGEMENT ", " PR_MPX_DISABLE_MANAGEMENT " (since Linux 3.19) "
 710 .\" commit fe3d197f84319d3bce379a9c0dc17b1f48ad358c
 711 .\" See also http://lwn.net/Articles/582712/
 712 .\" See also https://gcc.gnu.org/wiki/Intel%20MPX%20support%20in%20the%20GCC%20compiler
 713 Enable or disable kernel management of Memory Protection eXtensions (MPX)
 714 bounds tables.
 715 The
 716 .IR arg2 ,
 717 .IR arg3 ,
 718 .IR arg4 ,
 719 and
 720 .IR arg5
 721 .\" commit e9d1b4f3c60997fe197bf0243cb4a41a44387a88
 722 arguments must be zero.
 723 .IP
 724 MPX is a hardware-assisted mechanism for performing bounds checking on
 725 pointers.
 726 It consists of a set of registers storing bounds information
 727 and a set of special instruction prefixes that tell the CPU on which
 728 instructions it should do bounds enforcement.
 729 There is a limited number of these registers and
 730 when there are more pointers than registers,
 731 their contents must be "spilled" into a set of tables.
 732 These tables are called "bounds tables" and the MPX
 733 .BR prctl ()
 734 operations control
 735 whether the kernel manages their allocation and freeing.
 736 .IP
 737 When management is enabled, the kernel will take over allocation
 738 and freeing of the bounds tables.
 739 It does this by trapping the #BR exceptions that result
 740 at first use of missing bounds tables and
 741 instead of delivering the exception to user space,
 742 it allocates the table and populates the bounds directory
 743 with the location of the new table.
 744 For freeing, the kernel checks to see if bounds tables are
 745 present for memory which is not allocated, and frees them if so.
 746 .IP
 747 Before enabling MPX management using
 748 .BR PR_MPX_ENABLE_MANAGEMENT ,
 749 the application must first have allocated a user-space buffer for
 750 the bounds directory and placed the location of that directory in the
 751 .I bndcfgu
 752 register.
 753 .IP
 754 These calls fail if the CPU or kernel does not support MPX.
 755 Kernel support for MPX is enabled via the
 756 .BR CONFIG_X86_INTEL_MPX
 757 configuration option.
 758 You can check whether the CPU supports MPX by looking for the 'mpx'
 759 CPUID bit, like with the following command:
 760 .IP
 761 .in +4n
 762 .EX
 763 cat /proc/cpuinfo | grep ' mpx '
 764 .EE
 765 .in
 766 .IP
 767 A thread may not switch in or out of long (64-bit) mode while MPX is
 768 enabled.
 769 .IP
 770 All threads in a process are affected by these calls.
 771 .IP
 772 The child of a
 773 .BR fork (2)
 774 inherits the state of MPX management.
 775 During
 776 .BR execve (2),
 777 MPX management is reset to a state as if
 778 .BR PR_MPX_DISABLE_MANAGEMENT
 779 had been called.
 780 .IP
 781 For further information on Intel MPX, see the kernel source file
 782 .IR Documentation/x86/intel_mpx.txt .
 783 .TP
 784 .BR PR_SET_NAME " (since Linux 2.6.9)"
 785 Set the name of the calling thread,
 786 using the value in the location pointed to by
 787 .IR "(char\ *) arg2" .
 788 The name can be up to 16 bytes long,
 789 .\" TASK_COMM_LEN in include/linux/sched.h
 790 including the terminating null byte.
 791 (If the length of the string, including the terminating null byte,
 792 exceeds 16 bytes, the string is silently truncated.)
 793 This is the same attribute that can be set via
 794 .BR pthread_setname_np (3)
 795 and retrieved using
 796 .BR pthread_getname_np (3).
 797 The attribute is likewise accessible via
 798 .IR /proc/self/task/[tid]/comm ,
 799 where
 800 .I tid
 801 is the name of the calling thread.
 802 .TP
 803 .BR PR_GET_NAME " (since Linux 2.6.11)"
 804 Return the name of the calling thread,
 805 in the buffer pointed to by
 806 .IR "(char\ *) arg2" .
 807 The buffer should allow space for up to 16 bytes;
 808 the returned string will be null-terminated.
 809 .TP
 810 .BR PR_SET_NO_NEW_PRIVS " (since Linux 3.5)"
 811 Set the calling thread's
 812 .I no_new_privs
 813 attribute to the value in
 814 .IR arg2 .
 815 With
 816 .I no_new_privs
 817 set to 1,
 818 .BR execve (2)
 819 promises not to grant privileges to do anything
 820 that could not have been done without the
 821 .BR execve (2)
 822 call (for example,
 823 rendering the set-user-ID and set-group-ID mode bits,
 824 and file capabilities non-functional).
 825 Once set, this the
 826 .I no_new_privs
 827 attribute cannot be unset.
 828 The setting of this attribute is inherited by children created by
 829 .BR fork (2)
 830 and
 831 .BR clone (2),
 832 and preserved across
 833 .BR execve (2).
 834 .IP
 835 Since Linux 4.10,
 836 the value of a thread's
 837 .I no_new_privs
 838 attribute can be viewed via the
 839 .I NoNewPrivs
 840 field in the
 841 .IR /proc/[pid]/status
 842 file.
 843 .IP
 844 For more information, see the kernel source file
 845 .IR Documentation/userspace\-api/no_new_privs.rst
 846 .\" commit 40fde647ccb0ae8c11d256d271e24d385eed595b
 847 (or
 848 .IR Documentation/prctl/no_new_privs.txt
 849 before Linux 4.13).
 850 See also
 851 .BR seccomp (2).
 852 .TP
 853 .BR PR_GET_NO_NEW_PRIVS " (since Linux 3.5)"
 854 Return (as the function result) the value of the
 855 .I no_new_privs
 856 attribute for the calling thread.
 857 A value of 0 indicates the regular
 858 .BR execve (2)
 859 behavior.
 860 A value of 1 indicates
 861 .BR execve (2)
 862 will operate in the privilege-restricting mode described above.
 863 .TP
 864 .BR PR_SET_PDEATHSIG " (since Linux 2.1.57)"
 865 Set the parent death signal
 866 of the calling process to \fIarg2\fP (either a signal value
 867 in the range 1..maxsig, or 0 to clear).
 868 This is the signal that the calling process will get when its
 869 parent dies.
 870 .IP
 871 .IR Warning :
 872 .\" https://bugzilla.kernel.org/show_bug.cgi?id=43300
 873 the "parent" in this case is considered to be the
 874 .I thread
 875 that created this process.
 876 In other words, the signal will be sent when that thread terminates
 877 (via, for example,
 878 .BR pthread_exit (3)),
 879 rather than after all of the threads in the parent process terminate.
 880 .IP
 881 The parent-death signal is process-directed (see
 882 .BR signal (7))
 883 and, if the child installs a handler using the
 884 .BR sigaction (2)
 885 .B SA_SIGINFO
 886 flag, the
 887 .I si_pid
 888 field of the
 889 .I siginfo_t
 890 argument of the handler contains the PID of the terminating parent process.
 891 .IP
 892 The parent death signal setting is cleared for the child of a
 893 .BR fork (2).
 894 It is also
 895 (since Linux 2.4.36 / 2.6.23)
 896 .\" commit d2d56c5f51028cb9f3d800882eb6f4cbd3f9099f
 897 cleared when executing a set-user-ID or set-group-ID binary,
 898 or a binary that has associated capabilities (see
 899 .BR capabilities (7));
 900 otherwise, this value is preserved across
 901 .BR execve (2).
 902 .TP
 903 .BR PR_GET_PDEATHSIG " (since Linux 2.3.15)"
 904 Return the current value of the parent process death signal,
 905 in the location pointed to by
 906 .IR "(int\ *) arg2" .
 907 .TP
 908 .BR PR_SET_PTRACER " (since Linux 3.4)"
 909 .\" commit 2d514487faf188938a4ee4fb3464eeecfbdcf8eb
 910 .\" commit bf06189e4d14641c0148bea16e9dd24943862215
 911 This is meaningful only when the Yama LSM is enabled and in mode 1
 912 ("restricted ptrace", visible via
 913 .IR /proc/sys/kernel/yama/ptrace_scope ).
 914 When a "ptracer process ID" is passed in \fIarg2\fP,
 915 the caller is declaring that the ptracer process can
 916 .BR ptrace (2)
 917 the calling process as if it were a direct process ancestor.
 918 Each
 919 .B PR_SET_PTRACER
 920 operation replaces the previous "ptracer process ID".
 921 Employing
 922 .B PR_SET_PTRACER
 923 with
 924 .I arg2
 925 set to 0 clears the caller's "ptracer process ID".
 926 If
 927 .I arg2
 928 is
 929 .BR PR_SET_PTRACER_ANY ,
 930 the ptrace restrictions introduced by Yama are effectively disabled for the
 931 calling process.
 932 .IP
 933 For further information, see the kernel source file
 934 .IR Documentation/admin\-guide/LSM/Yama.rst
 935 .\" commit 90bb766440f2147486a2acc3e793d7b8348b0c22
 936 (or
 937 .IR Documentation/security/Yama.txt
 938 before Linux 4.13).
 939 .TP
 940 .BR PR_SET_SECCOMP " (since Linux 2.6.23)"
 941 .\" See http://thread.gmane.org/gmane.linux.kernel/542632
 942 .\" [PATCH 0 of 2] seccomp updates
 943 .\" andrea@cpushare.com
 944 Set the secure computing (seccomp) mode for the calling thread, to limit
 945 the available system calls.
 946 The more recent
 947 .BR seccomp (2)
 948 system call provides a superset of the functionality of
 949 .BR PR_SET_SECCOMP .
 950 .IP
 951 The seccomp mode is selected via
 952 .IR arg2 .
 953 (The seccomp constants are defined in
 954 .IR <linux/seccomp.h> .)
 955 .IP
 956 With
 957 .IR arg2
 958 set to
 959 .BR SECCOMP_MODE_STRICT ,
 960 the only system calls that the thread is permitted to make are
 961 .BR read (2),
 962 .BR write (2),
 963 .BR _exit (2)
 964 (but not
 965 .BR exit_group (2)),
 966 and
 967 .BR sigreturn (2).
 968 Other system calls result in the delivery of a
 969 .BR SIGKILL
 970 signal.
 971 Strict secure computing mode is useful for number-crunching applications
 972 that may need to execute untrusted byte code,
 973 perhaps obtained by reading from a pipe or socket.
 974 This operation is available only
 975 if the kernel is configured with
 976 .B CONFIG_SECCOMP
 977 enabled.
 978 .IP
 979 With
 980 .IR arg2
 981 set to
 982 .BR SECCOMP_MODE_FILTER " (since Linux 3.5),"
 983 the system calls allowed are defined by a pointer
 984 to a Berkeley Packet Filter passed in
 985 .IR arg3 .
 986 This argument is a pointer to
 987 .IR "struct sock_fprog" ;
 988 it can be designed to filter
 989 arbitrary system calls and system call arguments.
 990 This mode is available only if the kernel is configured with
 991 .B CONFIG_SECCOMP_FILTER
 992 enabled.
 993 .IP
 994 If
 995 .BR SECCOMP_MODE_FILTER
 996 filters permit
 997 .BR fork (2),
 998 then the seccomp mode is inherited by children created by
 999 .BR fork (2);
1000 if
1001 .BR execve (2)
1002 is permitted, then the seccomp mode is preserved across
1003 .BR execve (2).
1004 If the filters permit
1005 .BR prctl ()
1006 calls, then additional filters can be added;
1007 they are run in order until the first non-allow result is seen.
1008 .IP
1009 For further information, see the kernel source file
1010 .IR Documentation/userspace\-api/seccomp_filter.rst
1011 .\" commit c061f33f35be0ccc80f4b8e0aea5dfd2ed7e01a3
1012 (or
1013 .IR Documentation/prctl/seccomp_filter.txt
1014 before Linux 4.13).
1015 .TP
1016 .BR PR_GET_SECCOMP " (since Linux 2.6.23)"
1017 Return (as the function result)
1018 the secure computing mode of the calling thread.
1019 If the caller is not in secure computing mode, this operation returns 0;
1020 if the caller is in strict secure computing mode, then the
1021 .BR prctl ()
1022 call will cause a
1023 .B SIGKILL
1024 signal to be sent to the process.
1025 If the caller is in filter mode, and this system call is allowed by the
1026 seccomp filters, it returns 2; otherwise, the process is killed with a
1027 .BR SIGKILL
1028 signal.
1029 This operation is available only
1030 if the kernel is configured with
1031 .B CONFIG_SECCOMP
1032 enabled.
1033 .IP
1034 Since Linux 3.8, the
1035 .IR Seccomp
1036 field of the
1037 .IR /proc/[pid]/status
1038 file provides a method of obtaining the same information,
1039 without the risk that the process is killed; see
1040 .BR proc (5).
1041 .TP
1042 .BR PR_SET_SECUREBITS " (since Linux 2.6.26)"
1043 Set the "securebits" flags of the calling thread to the value supplied in
1044 .IR arg2 .
1045 See
1046 .BR capabilities (7).
1047 .TP
1048 .BR PR_GET_SECUREBITS " (since Linux 2.6.26)"
1049 Return (as the function result)
1050 the "securebits" flags of the calling thread.
1051 See
1052 .BR capabilities (7).
1053 .TP
1054 .BR PR_GET_SPECULATION_CTRL " (since Linux 4.17)"
1055 Returns the state of the speculation misfeature specified in
1056 .IR arg2 .
1057 Currently, the only permitted value for this argument is
1058 .BR PR_SPEC_STORE_BYPASS
1059 (otherwise the call fails with the error
1060 .BR ENODEV ).
1061 .IP
1062 The return value uses bits 0-3 with the following meaning:
1063 .RS
1064 .TP
1065 .BR PR_SPEC_PRCTL
1066 Mitigation can be controlled per thread by
1067 .B PR_SET_SPECULATION_CTRL
1068 .TP
1069 .BR PR_SPEC_ENABLE
1070 The speculation feature is enabled, mitigation is disabled.
1071 .TP
1072 .BR PR_SPEC_DISABLE
1073 The speculation feature is disabled, mitigation is enabled
1074 .TP
1075 .BR PR_SPEC_FORCE_DISABLE
1076 Same as
1077 .B PR_SPEC_DISABLE
1078 but cannot be undone.
1079 .RE
1080 .IP
1081 If all bits are 0,
1082 then the CPU is not affected by the speculation misfeature.
1083 .IP
1084 If
1085 .B PR_SPEC_PRCTL
1086 is set, then per-thread control of the mitigation is available.
1087 If not set,
1088 .BR prctl ()
1089 for the speculation misfeature will fail.
1090 .IP
1091 The
1092 .IR arg3 ,
1093 .IR arg4 ,
1094 and
1095 .I arg5
1096 arguments must be specified as 0; otherwise the call fails with the error
1097 .BR EINVAL .
1098 .TP
1099 .BR PR_SET_SPECULATION_CTRL " (since Linux 4.17)"
1100 .\" commit b617cfc858161140d69cc0b5cc211996b557a1c7
1101 .\" commit 356e4bfff2c5489e016fdb925adbf12a1e3950ee
1102 Sets the state of the speculation misfeature specified in
1103 .IR arg2 .
1104 Currently, the only permitted value for this argument is
1105 .B PR_SPEC_STORE_BYPASS
1106 (otherwise the call fails with the error
1107 .BR ENODEV ).
1108 This setting is a per-thread attribute.
1109 The
1110 .IR arg3
1111 argument is used to hand in the control value,
1112 which is one of the following:
1113 .RS
1114 .TP
1115 .BR PR_SPEC_ENABLE
1116 The speculation feature is enabled, mitigation is disabled.
1117 .TP
1118 .BR PR_SPEC_DISABLE
1119 The speculation feature is disabled, mitigation is enabled
1120 .TP
1121 .BR PR_SPEC_FORCE_DISABLE
1122 Same as
1123 .B PR_SPEC_DISABLE
1124 but cannot be undone.
1125 A subsequent
1126 .B
1127 prctl(..., PR_SPEC_ENABLE)
1128 will fail with the error
1129 .BR EPERM .
1130 .RE
1131 .IP
1132 Any other value in
1133 .IR arg3
1134 will result in the call failing with the error
1135 .BR ERANGE .
1136 .IP
1137 The
1138 .I arg4
1139 and
1140 .I arg5
1141 arguments must be specified as 0; otherwise the call fails with the error
1142 .BR EINVAL .
1143 .IP
1144 The speculation feature can also be controlled by the
1145 .B spec_store_bypass_disable
1146 boot parameter.
1147 This parameter may enforce a read-only policy which will result in the
1148 .BR prctl (2)
1149 call failing with the error
1150 .BR ENXIO .
1151 For further details, see the kernel source file
1152 .IR Documentation/admin-guide/kernel-parameters.txt .
1153 .TP
1154 .BR PR_SET_THP_DISABLE " (since Linux 3.15)"
1155 .\" commit a0715cc22601e8830ace98366c0c2bd8da52af52
1156 Set the state of the "THP disable" flag for the calling thread.
1157 If
1158 .I arg2
1159 has a nonzero value, the flag is set, otherwise it is cleared.
1160 Setting this flag provides a method
1161 for disabling transparent huge pages
1162 for jobs where the code cannot be modified, and using a malloc hook with
1163 .BR madvise (2)
1164 is not an option (i.e., statically allocated data).
1165 The setting of the "THP disable" flag is inherited by a child created via
1166 .BR fork (2)
1167 and is preserved across
1168 .BR execve (2).
1169 .\"
1170 .TP
1171 .BR PR_TASK_PERF_EVENTS_DISABLE " (since Linux 2.6.31)"
1172 Disable all performance counters attached to the calling process,
1173 regardless of whether the counters were created by
1174 this process or another process.
1175 Performance counters created by the calling process for other
1176 processes are unaffected.
1177 For more information on performance counters, see the Linux kernel source file
1178 .IR tools/perf/design.txt .
1179 .IP
1180 Originally called
1181 .BR PR_TASK_PERF_COUNTERS_DISABLE ;
1182 .\" commit 1d1c7ddbfab358445a542715551301b7fc363e28
1183 renamed (retaining the same numerical value)
1184 in Linux 2.6.32.
1185 .\"
1186 .TP
1187 .BR PR_TASK_PERF_EVENTS_ENABLE " (since Linux 2.6.31)"
1188 The converse of
1189 .BR PR_TASK_PERF_EVENTS_DISABLE ;
1190 enable performance counters attached to the calling process.
1191 .IP
1192 Originally called
1193 .BR PR_TASK_PERF_COUNTERS_ENABLE ;
1194 .\" commit 1d1c7ddbfab358445a542715551301b7fc363e28
1195 renamed
1196 .\" commit cdd6c482c9ff9c55475ee7392ec8f672eddb7be6
1197 in Linux 2.6.32.
1198 .\"
1199 .TP
1200 .BR PR_GET_THP_DISABLE " (since Linux 3.15)"
1201 Return (via the function result) the current setting of the "THP disable"
1202 flag for the calling thread:
1203 either 1, if the flag is set, or 0, if it is not.
1204 .TP
1205 .BR PR_GET_TID_ADDRESS " (since Linux 3.5)"
1206 .\" commit 300f786b2683f8bb1ec0afb6e1851183a479c86d
1207 Retrieve the
1208 .I clear_child_tid
1209 address set by
1210 .BR set_tid_address (2)
1211 and the
1212 .BR clone (2)
1213 .B CLONE_CHILD_CLEARTID
1214 flag, in the location pointed to by
1215 .IR "(int\ **)\ arg2" .
1216 This feature is available only if the kernel is built with the
1217 .BR CONFIG_CHECKPOINT_RESTORE
1218 option enabled.
1219 Note that since the
1220 .BR prctl ()
1221 system call does not have a compat implementation for
1222 the AMD64 x32 and MIPS n32 ABIs,
1223 and the kernel writes out a pointer using the kernel's pointer size,
1224 this operation expects a user-space buffer of 8 (not 4) bytes on these ABIs.
1225 .TP
1226 .BR PR_SET_TIMERSLACK " (since Linux 2.6.28)"
1227 .\" See https://lwn.net/Articles/369549/
1228 .\" commit 6976675d94042fbd446231d1bd8b7de71a980ada
1229 Each thread has two associated timer slack values:
1230 a "default" value, and a "current" value.
1231 This operation sets the "current" timer slack value for the calling thread.
1232 If the nanosecond value supplied in
1233 .IR arg2
1234 is greater than zero, then the "current" value is set to this value.
1235 If
1236 .I arg2
1237 is less than or equal to zero,
1238 .\" It seems that it's not possible to set the timer slack to zero;
1239 .\" The minimum value is 1? Seems a little strange.
1240 the "current" timer slack is reset to the
1241 thread's "default" timer slack value.
1242 .IP
1243 The "current" timer slack is used by the kernel to group timer expirations
1244 for the calling thread that are close to one another;
1245 as a consequence, timer expirations for the thread may be
1246 up to the specified number of nanoseconds late (but will never expire early).
1247 Grouping timer expirations can help reduce system power consumption
1248 by minimizing CPU wake-ups.
1249 .IP
1250 The timer expirations affected by timer slack are those set by
1251 .BR select (2),
1252 .BR pselect (2),
1253 .BR poll (2),
1254 .BR ppoll (2),
1255 .BR epoll_wait (2),
1256 .BR epoll_pwait (2),
1257 .BR clock_nanosleep (2),
1258 .BR nanosleep (2),
1259 and
1260 .BR futex (2)
1261 (and thus the library functions implemented via futexes, including
1262 .\" List obtained by grepping for futex usage in glibc source
1263 .BR pthread_cond_timedwait (3),
1264 .BR pthread_mutex_timedlock (3),
1265 .BR pthread_rwlock_timedrdlock (3),
1266 .BR pthread_rwlock_timedwrlock (3),
1267 and
1268 .BR sem_timedwait (3)).
1269 .IP
1270 Timer slack is not applied to threads that are scheduled under
1271 a real-time scheduling policy (see
1272 .BR sched_setscheduler (2)).
1273 .IP
1274 When a new thread is created,
1275 the two timer slack values are made the same as the "current" value
1276 of the creating thread.
1277 Thereafter, a thread can adjust its "current" timer slack value via
1278 .BR PR_SET_TIMERSLACK .
1279 The "default" value can't be changed.
1280 The timer slack values of
1281 .IR init
1282 (PID 1), the ancestor of all processes,
1283 are 50,000 nanoseconds (50 microseconds).
1284 The timer slack values are preserved across
1285 .BR execve (2).
1286 .IP
1287 Since Linux 4.6, the "current" timer slack value of any process
1288 can be examined and changed via the file
1289 .IR /proc/[pid]/timerslack_ns .
1290 See
1291 .BR proc (5).
1292 .TP
1293 .BR PR_GET_TIMERSLACK " (since Linux 2.6.28)"
1294 Return (as the function result)
1295 the "current" timer slack value of the calling thread.
1296 .TP
1297 .BR PR_SET_TIMING " (since Linux 2.6.0)"
1298 .\" Precisely: Linux 2.6.0-test4
1299 Set whether to use (normal, traditional) statistical process timing or
1300 accurate timestamp-based process timing, by passing
1301 .B PR_TIMING_STATISTICAL
1302 .\" 0
1303 or
1304 .B PR_TIMING_TIMESTAMP
1305 .\" 1
1306 to \fIarg2\fP.
1307 .B PR_TIMING_TIMESTAMP
1308 is not currently implemented
1309 (attempting to set this mode will yield the error
1310 .BR EINVAL ).
1311 .\" PR_TIMING_TIMESTAMP doesn't do anything in 2.6.26-rc8,
1312 .\" and looking at the patch history, it appears
1313 .\" that it never did anything.
1314 .TP
1315 .BR PR_GET_TIMING " (since Linux 2.6.0)"
1316 .\" Precisely: Linux 2.6.0-test4
1317 Return (as the function result) which process timing method is currently
1318 in use.
1319 .TP
1320 .BR PR_SET_TSC " (since Linux 2.6.26, x86 only)"
1321 Set the state of the flag determining whether the timestamp counter
1322 can be read by the process.
1323 Pass
1324 .B PR_TSC_ENABLE
1325 to
1326 .I arg2
1327 to allow it to be read, or
1328 .B PR_TSC_SIGSEGV
1329 to generate a
1330 .B SIGSEGV
1331 when the process tries to read the timestamp counter.
1332 .TP
1333 .BR PR_GET_TSC " (since Linux 2.6.26, x86 only)"
1334 Return the state of the flag determining whether the timestamp counter
1335 can be read,
1336 in the location pointed to by
1337 .IR "(int\ *) arg2" .
1338 .TP
1339 .B PR_SET_UNALIGN
1340 (Only on: ia64, since Linux 2.3.48; parisc, since Linux 2.6.15;
1341 PowerPC, since Linux 2.6.18; Alpha, since Linux 2.6.22;
1342 .\" sh: 94ea5e449ae834af058ef005d16a8ad44fcf13d6
1343 .\" tile: 2f9ac29eec71a696cb0dcc5fb82c0f8d4dac28c9
1344 sh, since Linux 2.6.34; tile, since Linux 3.12)
1345 Set unaligned access control bits to \fIarg2\fP.
1346 Pass
1347 \fBPR_UNALIGN_NOPRINT\fP to silently fix up unaligned user accesses,
1348 or \fBPR_UNALIGN_SIGBUS\fP to generate
1349 .B SIGBUS
1350 on unaligned user access.
1351 Alpha also supports an additional flag with the value
1352 of 4 and no corresponding named constant,
1353 which instructs kernel to not fix up
1354 unaligned accesses (it is analogous to providing the
1355 .BR UAC_NOFIX
1356 flag in
1357 .BR SSI_NVPAIRS
1358 operation of the
1359 .BR setsysinfo ()
1360 system call on Tru64).
1361 .TP
1362 .B PR_GET_UNALIGN
1363 (see
1364 .B PR_SET_UNALIGN
1365 for information on versions and architectures)
1366 Return unaligned access control bits, in the location pointed to by
1367 .IR "(unsigned int\ *) arg2" .
1368 .SH RETURN VALUE
1369 On success,
1370 .BR PR_GET_DUMPABLE ,
1371 .BR PR_GET_KEEPCAPS ,
1372 .BR PR_GET_NO_NEW_PRIVS ,
1373 .BR PR_GET_THP_DISABLE ,
1374 .BR PR_CAPBSET_READ ,
1375 .BR PR_GET_TIMING ,
1376 .BR PR_GET_TIMERSLACK ,
1377 .BR PR_GET_SECUREBITS ,
1378 .BR PR_MCE_KILL_GET ,
1379 .BR PR_CAP_AMBIENT + PR_CAP_AMBIENT_IS_SET ,
1380 and (if it returns)
1381 .BR PR_GET_SECCOMP
1382 return the nonnegative values described above.
1383 All other
1384 .I option
1385 values return 0 on success.
1386 On error, \-1 is returned, and
1387 .I errno
1388 is set appropriately.
1389 .SH ERRORS
1390 .TP
1391 .B EACCES
1392 .I option
1393 is
1394 .BR PR_SET_SECCOMP
1395 and
1396 .I arg2
1397 is
1398 .BR SECCOMP_MODE_FILTER ,
1399 but the process does not have the
1400 .BR CAP_SYS_ADMIN
1401 capability or has not set the
1402 .IR no_new_privs
1403 attribute (see the discussion of
1404 .BR PR_SET_NO_NEW_PRIVS
1405 above).
1406 .TP
1407 .B EACCES
1408 .I option
1409 is
1410 .BR PR_SET_MM ,
1411 and
1412 .I arg3
1413 is
1414 .BR PR_SET_MM_EXE_FILE ,
1415 the file is not executable.
1416 .TP
1417 .B EBADF
1418 .I option
1419 is
1420 .BR PR_SET_MM ,
1421 .I arg3
1422 is
1423 .BR PR_SET_MM_EXE_FILE ,
1424 and the file descriptor passed in
1425 .I arg4
1426 is not valid.
1427 .TP
1428 .B EBUSY
1429 .I option
1430 is
1431 .BR PR_SET_MM ,
1432 .I arg3
1433 is
1434 .BR PR_SET_MM_EXE_FILE ,
1435 and this the second attempt to change the
1436 .I /proc/pid/exe
1437 symbolic link, which is prohibited.
1438 .TP
1439 .B EFAULT
1440 .I arg2
1441 is an invalid address.
1442 .TP
1443 .B EFAULT
1444 .I option
1445 is
1446 .BR PR_SET_SECCOMP ,
1447 .I arg2
1448 is
1449 .BR SECCOMP_MODE_FILTER ,
1450 the system was built with
1451 .BR CONFIG_SECCOMP_FILTER ,
1452 and
1453 .I arg3
1454 is an invalid address.
1455 .TP
1456 .B EINVAL
1457 The value of
1458 .I option
1459 is not recognized.
1460 .TP
1461 .B EINVAL
1462 .I option
1463 is
1464 .BR PR_MCE_KILL
1465 or
1466 .BR PR_MCE_KILL_GET
1467 or
1468 .BR PR_SET_MM ,
1469 and unused
1470 .BR prctl ()
1471 arguments were not specified as zero.
1472 .TP
1473 .B EINVAL
1474 .I arg2
1475 is not valid value for this
1476 .IR option .
1477 .TP
1478 .B EINVAL
1479 .I option
1480 is
1481 .BR PR_SET_SECCOMP
1482 or
1483 .BR PR_GET_SECCOMP ,
1484 and the kernel was not configured with
1485 .BR CONFIG_SECCOMP .
1486 .TP
1487 .B EINVAL
1488 .I option
1489 is
1490 .BR PR_SET_SECCOMP ,
1491 .I arg2
1492 is
1493 .BR SECCOMP_MODE_FILTER ,
1494 and the kernel was not configured with
1495 .BR CONFIG_SECCOMP_FILTER .
1496 .TP
1497 .B EINVAL
1498 .I option
1499 is
1500 .BR PR_SET_MM ,
1501 and one of the following is true
1502 .RS
1503 .IP * 3
1504 .I arg4
1505 or
1506 .I arg5
1507 is nonzero;
1508 .IP *
1509 .I arg3
1510 is greater than
1511 .B TASK_SIZE
1512 (the limit on the size of the user address space for this architecture);
1513 .IP *
1514 .I arg2
1515 is
1516 .BR PR_SET_MM_START_CODE ,
1517 .BR PR_SET_MM_END_CODE ,
1518 .BR PR_SET_MM_START_DATA ,
1519 .BR PR_SET_MM_END_DATA ,
1520 or
1521 .BR PR_SET_MM_START_STACK ,
1522 and the permissions of the corresponding memory area are not as required;
1523 .IP *
1524 .I arg2
1525 is
1526 .BR PR_SET_MM_START_BRK
1527 or
1528 .BR PR_SET_MM_BRK ,
1529 and
1530 .I arg3
1531 is less than or equal to the end of the data segment
1532 or specifies a value that would cause the
1533 .B RLIMIT_DATA
1534 resource limit to be exceeded.
1535 .RE
1536 .TP
1537 .B EINVAL
1538 .I option
1539 is
1540 .BR PR_SET_PTRACER
1541 and
1542 .I arg2
1543 is not 0,
1544 .BR PR_SET_PTRACER_ANY ,
1545 or the PID of an existing process.
1546 .TP
1547 .B EINVAL
1548 .I option
1549 is
1550 .B PR_SET_PDEATHSIG
1551 and
1552 .I arg2
1553 is not a valid signal number.
1554 .TP
1555 .B EINVAL
1556 .I option
1557 is
1558 .BR PR_SET_DUMPABLE
1559 and
1560 .I arg2
1561 is neither
1562 .B SUID_DUMP_DISABLE
1563 nor
1564 .BR SUID_DUMP_USER .
1565 .TP
1566 .B EINVAL
1567 .I option
1568 is
1569 .BR PR_SET_TIMING
1570 and
1571 .I arg2
1572 is not
1573 .BR PR_TIMING_STATISTICAL .
1574 .TP
1575 .B EINVAL
1576 .I option
1577 is
1578 .BR PR_SET_NO_NEW_PRIVS
1579 and
1580 .I arg2
1581 is not equal to 1
1582 or
1583 .IR arg3 ,
1584 .IR arg4 ,
1585 or
1586 .IR arg5
1587 is nonzero.
1588 .TP
1589 .B EINVAL
1590 .I option
1591 is
1592 .BR PR_GET_NO_NEW_PRIVS
1593 and
1594 .IR arg2 ,
1595 .IR arg3 ,
1596 .IR arg4 ,
1597 or
1598 .IR arg5
1599 is nonzero.
1600 .TP
1601 .B EINVAL
1602 .I option
1603 is
1604 .BR PR_SET_THP_DISABLE
1605 and
1606 .IR arg3 ,
1607 .IR arg4 ,
1608 or
1609 .IR arg5
1610 is nonzero.
1611 .TP
1612 .B EINVAL
1613 .I option
1614 is
1615 .BR PR_GET_THP_DISABLE
1616 and
1617 .IR arg2 ,
1618 .IR arg3 ,
1619 .IR arg4 ,
1620 or
1621 .IR arg5
1622 is nonzero.
1623 .TP
1624 .B EINVAL
1625 .I option
1626 is
1627 .B PR_CAP_AMBIENT
1628 and an unused argument
1629 .RI ( arg4 ,
1630 .IR arg5 ,
1631 or,
1632 in the case of
1633 .BR PR_CAP_AMBIENT_CLEAR_ALL ,
1634 .IR arg3 )
1635 is nonzero; or
1636 .IR arg2
1637 has an invalid value;
1638 or
1639 .IR arg2
1640 is
1641 .BR PR_CAP_AMBIENT_LOWER ,
1642 .BR PR_CAP_AMBIENT_RAISE ,
1643 or
1644 .BR PR_CAP_AMBIENT_IS_SET
1645 and
1646 .IR arg3
1647 does not specify a valid capability.
1648 .TP
1649 .B ENODEV
1650 .I option
1651 was
1652 .BR PR_SET_SPECULATION_CTRL
1653 the kernel or CPU does not support the requested speculation misfeature.
1654 .TP
1655 .B ENXIO
1656 .I option
1657 was
1658 .BR PR_MPX_ENABLE_MANAGEMENT
1659 or
1660 .BR PR_MPX_DISABLE_MANAGEMENT
1661 and the kernel or the CPU does not support MPX management.
1662 Check that the kernel and processor have MPX support.
1663 .TP
1664 .B ENXIO
1665 .I option
1666 was
1667 .BR PR_SET_SPECULATION_CTRL
1668 implies that the control of the selected speculation misfeature is not possible.
1669 See
1670 .BR PR_GET_SPECULATION_CTRL
1671 for the bit fields to determine which option is available.
1672 .TP
1673 .B EOPNOTSUPP
1674 .I option
1675 is
1676 .B PR_SET_FP_MODE
1677 and
1678 .I arg2
1679 has an invalid or unsupported value.
1680 .TP
1681 .B EPERM
1682 .I option
1683 is
1684 .BR PR_SET_SECUREBITS ,
1685 and the caller does not have the
1686 .B CAP_SETPCAP
1687 capability,
1688 or tried to unset a "locked" flag,
1689 or tried to set a flag whose corresponding locked flag was set
1690 (see
1691 .BR capabilities (7)).
1692 .TP
1693 .B EPERM
1694 .I option
1695 is
1696 .BR PR_SET_SPECULATION_CTRL
1697 wherein the speculation was disabled with
1698 .B PR_SPEC_FORCE_DISABLE
1699 and caller tried to enable it again.
1700 .TP
1701 .B EPERM
1702 .I option
1703 is
1704 .BR PR_SET_KEEPCAPS ,
1705 and the caller's
1706 .B SECBIT_KEEP_CAPS_LOCKED
1707 flag is set
1708 (see
1709 .BR capabilities (7)).
1710 .TP
1711 .B EPERM
1712 .I option
1713 is
1714 .BR PR_CAPBSET_DROP ,
1715 and the caller does not have the
1716 .B CAP_SETPCAP
1717 capability.
1718 .TP
1719 .B EPERM
1720 .I option
1721 is
1722 .BR PR_SET_MM ,
1723 and the caller does not have the
1724 .B CAP_SYS_RESOURCE
1725 capability.
1726 .TP
1727 .B EPERM
1728 .IR option
1729 is
1730 .BR PR_CAP_AMBIENT
1731 and
1732 .IR arg2
1733 is
1734 .BR PR_CAP_AMBIENT_RAISE ,
1735 but either the capability specified in
1736 .IR arg3
1737 is not present in the process's permitted and inheritable capability sets,
1738 or the
1739 .B PR_CAP_AMBIENT_LOWER
1740 securebit has been set.
1741 .TP
1742 .B ERANGE
1743 .I option
1744 was
1745 .BR PR_SET_SPECULATION_CTRL
1746 and
1747 .IR arg3
1748 is neither
1749 .BR PR_SPEC_ENABLE ,
1750 .BR PR_SPEC_DISABLE ,
1751 nor
1752 .BR PR_SPEC_FORCE_DISABLE .
1753 .TP
1754 .B EINVAL
1755 .I option
1756 was
1757 .BR PR_GET_SPECULATION_CTRL
1758 or
1759 .BR PR_SET_SPECULATION_CTRL
1760 and unused arguments to
1761 .BR prctl ()
1762 are not 0.
1763 .SH VERSIONS
1764 The
1765 .BR prctl ()
1766 system call was introduced in Linux 2.1.57.
1767 .\" The library interface was added in glibc 2.0.6
1768 .SH CONFORMING TO
1769 This call is Linux-specific.
1770 IRIX has a
1771 .BR prctl ()
1772 system call (also introduced in Linux 2.1.44
1773 as irix_prctl on the MIPS architecture),
1774 with prototype
1775 .PP
1776 .in +4n
1777 .EX
1778 .BI "ptrdiff_t prctl(int " option ", int " arg2 ", int " arg3 );
1779 .EE
1780 .in
1781 .PP
1782 and options to get the maximum number of processes per user,
1783 get the maximum number of processors the calling process can use,
1784 find out whether a specified process is currently blocked,
1785 get or set the maximum stack size, and so on.
1786 .SH SEE ALSO
1787 .BR signal (2),
1788 .BR core (5)