2015-04-23 14:22:20 +00:00
|
|
|
.\" Copyright (c) 2013 Hudson River Trading LLC
|
2013-09-19 18:53:42 +00:00
|
|
|
.\" Written by: John H. Baldwin <jhb@FreeBSD.org>
|
|
|
|
.\" All rights reserved.
|
|
|
|
.\"
|
2014-12-15 12:01:42 +00:00
|
|
|
.\" Copyright (c) 2014 The FreeBSD Foundation
|
|
|
|
.\" Portions of this documentation were written by Konstantin Belousov
|
|
|
|
.\" under sponsorship from the FreeBSD Foundation.
|
|
|
|
.\"
|
2013-09-19 18:53:42 +00:00
|
|
|
.\" Redistribution and use in source and binary forms, with or without
|
|
|
|
.\" modification, are permitted provided that the following conditions
|
|
|
|
.\" are met:
|
|
|
|
.\" 1. Redistributions of source code must retain the above copyright
|
|
|
|
.\" notice, this list of conditions and the following disclaimer.
|
|
|
|
.\" 2. Redistributions in binary form must reproduce the above copyright
|
|
|
|
.\" notice, this list of conditions and the following disclaimer in the
|
|
|
|
.\" documentation and/or other materials provided with the distribution.
|
|
|
|
.\"
|
|
|
|
.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
|
|
|
|
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
|
|
|
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
|
|
|
|
.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
|
|
|
|
.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
|
|
|
|
.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
|
|
|
|
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
|
|
|
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
|
|
|
|
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
|
|
|
|
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
|
|
|
.\" SUCH DAMAGE.
|
|
|
|
.\"
|
|
|
|
.\" $FreeBSD$
|
|
|
|
.\"
|
2021-09-02 00:59:10 +00:00
|
|
|
.Dd September 2, 2021
|
2013-09-19 18:53:42 +00:00
|
|
|
.Dt PROCCTL 2
|
|
|
|
.Os
|
|
|
|
.Sh NAME
|
|
|
|
.Nm procctl
|
|
|
|
.Nd control processes
|
|
|
|
.Sh LIBRARY
|
|
|
|
.Lb libc
|
|
|
|
.Sh SYNOPSIS
|
|
|
|
.In sys/procctl.h
|
|
|
|
.Ft int
|
2020-06-13 18:18:34 +00:00
|
|
|
.Fn procctl "idtype_t idtype" "id_t id" "int cmd" "void *data"
|
2013-09-19 18:53:42 +00:00
|
|
|
.Sh DESCRIPTION
|
|
|
|
The
|
|
|
|
.Fn procctl
|
|
|
|
system call provides for control over processes.
|
|
|
|
The
|
|
|
|
.Fa idtype
|
|
|
|
and
|
|
|
|
.Fa id
|
|
|
|
arguments specify the set of processes to control.
|
|
|
|
If multiple processes match the identifier,
|
|
|
|
.Nm
|
|
|
|
will make a
|
|
|
|
.Dq best effort
|
2014-07-09 01:33:35 +00:00
|
|
|
to control as many of the selected processes as possible.
|
2013-09-19 18:53:42 +00:00
|
|
|
An error is only returned if no selected processes successfully complete
|
|
|
|
the request.
|
|
|
|
The following identifier types are supported:
|
2019-02-26 17:35:06 +00:00
|
|
|
.Bl -tag -width P_PGID
|
2013-09-19 18:53:42 +00:00
|
|
|
.It Dv P_PID
|
|
|
|
Control the process with the process ID
|
|
|
|
.Fa id .
|
2021-10-15 19:01:42 +00:00
|
|
|
.Fa id
|
|
|
|
zero is a shortcut for the calling process ID.
|
2013-09-19 18:53:42 +00:00
|
|
|
.It Dv P_PGID
|
|
|
|
Control processes belonging to the process group with the ID
|
|
|
|
.Fa id .
|
|
|
|
.El
|
|
|
|
.Pp
|
|
|
|
The control request to perform is specified by the
|
|
|
|
.Fa cmd
|
|
|
|
argument.
|
2021-10-15 20:09:39 +00:00
|
|
|
.Pp
|
|
|
|
All status changing requests
|
|
|
|
.Dv *_CTL
|
|
|
|
require the caller to have the right to debug the target.
|
|
|
|
All status query requests
|
|
|
|
.DV *_STATUS
|
|
|
|
require the caller to have the right to observe the target.
|
|
|
|
.Pp
|
2013-09-19 18:53:42 +00:00
|
|
|
The following commands are supported:
|
2019-02-26 17:35:06 +00:00
|
|
|
.Bl -tag -width PROC_TRAPCAP_STATUS
|
2019-02-26 17:41:41 +00:00
|
|
|
.It Dv PROC_ASLR_CTL
|
|
|
|
Controls the Address Space Layout Randomization (ASLR) in the program
|
|
|
|
images created
|
|
|
|
by
|
|
|
|
.Xr execve 2
|
|
|
|
in the specified process or its descendants that did not changed
|
|
|
|
the control nor modified it by other means.
|
|
|
|
The
|
2020-06-13 18:18:34 +00:00
|
|
|
.Fa data
|
2019-02-26 17:41:41 +00:00
|
|
|
parameter must point to the integer variable holding one of the following
|
|
|
|
values:
|
|
|
|
.Bl -tag -width PROC_ASLR_FORCE_DISABLE
|
|
|
|
.It Dv PROC_ASLR_FORCE_ENABLE
|
|
|
|
Request that ASLR is enabled after execution, even if it is disabled
|
|
|
|
system-wide.
|
|
|
|
The image flag and set-uid might prevent ASLR enablement still.
|
|
|
|
.It Dv PROC_ASLR_FORCE_DISABLE
|
|
|
|
Request that ASLR is disabled after execution.
|
|
|
|
Same notes as for
|
2019-06-28 16:42:44 +00:00
|
|
|
.Dv PROC_ASLR_FORCE_ENABLE
|
2019-02-26 17:41:41 +00:00
|
|
|
apply.
|
|
|
|
.It Dv PROC_ASLR_NOFORCE
|
2019-07-02 19:07:17 +00:00
|
|
|
Use the system-wide configured policy for ASLR.
|
2019-02-26 17:41:41 +00:00
|
|
|
.El
|
|
|
|
.It Dv PROC_ASLR_STATUS
|
|
|
|
Returns the current status of ASLR enablement for the target process.
|
|
|
|
The
|
2020-06-13 18:18:34 +00:00
|
|
|
.Fa data
|
2019-02-26 17:41:41 +00:00
|
|
|
parameter must point to the integer variable, where one of the
|
|
|
|
following values is written:
|
|
|
|
.Bl -tag -width PROC_ASLR_FORCE_DISABLE
|
|
|
|
.It Dv PROC_ASLR_FORCE_ENABLE
|
|
|
|
.It Dv PROC_ASLR_FORCE_DISABLE
|
|
|
|
.It Dv PROC_ASLR_NOFORCE
|
|
|
|
.El
|
|
|
|
.Pp
|
|
|
|
If the currently executed image in the process itself has ASLR enabled,
|
|
|
|
the
|
|
|
|
.Dv PROC_ASLR_ACTIVE
|
|
|
|
flag is or-ed with the value listed above.
|
2019-07-02 19:07:17 +00:00
|
|
|
.It Dv PROC_PROTMAX_CTL
|
|
|
|
Controls implicit application of PROT_MAX protection equal to the
|
|
|
|
.Fa prot
|
|
|
|
argument of the
|
|
|
|
.Xr mmap 2
|
|
|
|
syscall, in the target process.
|
|
|
|
The
|
2020-06-13 18:18:34 +00:00
|
|
|
.Fa data
|
2019-07-02 19:07:17 +00:00
|
|
|
parameter must point to the integer variable holding one of the following
|
|
|
|
values:
|
|
|
|
.Bl -tag -width PROC_PROTMAX_FORCE_DISABLE
|
|
|
|
.It Dv PROC_PROTMAX_FORCE_ENABLE
|
|
|
|
Enables implicit PROT_MAX application,
|
|
|
|
even if it is disabled system-wide by the sysctl
|
|
|
|
.Va vm.imply_prot_max .
|
|
|
|
The image flag might still prevent the enablement.
|
2020-05-16 04:52:29 +00:00
|
|
|
.It Dv PROC_PROTMAX_FORCE_DISABLE
|
2019-07-02 19:07:17 +00:00
|
|
|
Request that implicit application of PROT_MAX be disabled.
|
|
|
|
Same notes as for
|
|
|
|
.Dv PROC_PROTMAX_FORCE_ENABLE
|
|
|
|
apply.
|
|
|
|
.It Dv PROC_PROTMAX_NOFORCE
|
|
|
|
Use the system-wide configured policy for PROT_MAX.
|
|
|
|
.El
|
|
|
|
.It Dv PROC_PROTMAX_STATUS
|
|
|
|
Returns the current status of implicit PROT_MAX enablement for the
|
|
|
|
target process.
|
|
|
|
The
|
2020-06-13 18:18:34 +00:00
|
|
|
.Fa data
|
2019-07-02 19:07:17 +00:00
|
|
|
parameter must point to the integer variable, where one of the
|
|
|
|
following values is written:
|
|
|
|
.Bl -tag -width PROC_PROTMAX_FORCE_DISABLE
|
|
|
|
.It Dv PROC_PROTMAX_FORCE_ENABLE
|
|
|
|
.It Dv PROC_PROTMAX_FORCE_DISABLE
|
|
|
|
.It Dv PROC_PROTMAX_NOFORCE
|
|
|
|
.El
|
|
|
|
.Pp
|
|
|
|
If the currently executed image in the process itself has implicit PROT_MAX
|
|
|
|
application enabled, the
|
|
|
|
.Dv PROC_PROTMAX_ACTIVE
|
|
|
|
flag is or-ed with the value listed above.
|
2013-09-19 18:53:42 +00:00
|
|
|
.It Dv PROC_SPROTECT
|
|
|
|
Set process protection state.
|
|
|
|
This is used to mark a process as protected from being killed if the system
|
2015-08-21 02:42:14 +00:00
|
|
|
exhausts the available memory and swap.
|
2013-09-19 18:53:42 +00:00
|
|
|
The
|
2020-06-13 18:18:34 +00:00
|
|
|
.Fa data
|
2013-09-19 18:53:42 +00:00
|
|
|
parameter must point to an integer containing an operation and zero or more
|
|
|
|
optional flags.
|
|
|
|
The following operations are supported:
|
2019-02-26 17:35:06 +00:00
|
|
|
.Bl -tag -width PPROT_CLEAR
|
2013-09-19 18:53:42 +00:00
|
|
|
.It Dv PPROT_SET
|
|
|
|
Mark the selected processes as protected.
|
|
|
|
.It Dv PPROT_CLEAR
|
|
|
|
Clear the protected state of selected processes.
|
|
|
|
.El
|
|
|
|
.Pp
|
|
|
|
The following optional flags are supported:
|
2019-02-26 17:35:06 +00:00
|
|
|
.Bl -tag -width PPROT_DESCEND
|
2013-09-19 18:53:42 +00:00
|
|
|
.It Dv PPROT_DESCEND
|
|
|
|
Apply the requested operation to all child processes of each selected process
|
|
|
|
in addition to each selected process.
|
|
|
|
.It Dv PPROT_INHERIT
|
|
|
|
When used with
|
|
|
|
.Dv PPROT_SET ,
|
|
|
|
mark all future child processes of each selected process as protected.
|
|
|
|
Future child processes will also mark all of their future child processes.
|
|
|
|
.El
|
2014-12-15 12:01:42 +00:00
|
|
|
.It Dv PROC_REAP_ACQUIRE
|
|
|
|
Acquires the reaper status for the current process.
|
2015-08-21 02:42:14 +00:00
|
|
|
Reaper status means that children orphaned by the reaper's descendants
|
|
|
|
that were forked after the acquisition of reaper status are reparented to the
|
|
|
|
reaper process.
|
|
|
|
After system initialization,
|
2014-12-15 12:01:42 +00:00
|
|
|
.Xr init 8
|
|
|
|
is the default reaper.
|
|
|
|
.It Dv PROC_REAP_RELEASE
|
2015-08-21 02:42:14 +00:00
|
|
|
Release the reaper state for the current process.
|
2014-12-15 12:01:42 +00:00
|
|
|
The reaper of the current process becomes the new reaper of the
|
2014-12-17 01:32:27 +00:00
|
|
|
current process's descendants.
|
2014-12-15 12:01:42 +00:00
|
|
|
.It Dv PROC_REAP_STATUS
|
2015-08-21 02:42:14 +00:00
|
|
|
Provides information about the reaper of the specified process,
|
2014-12-17 01:32:27 +00:00
|
|
|
or the process itself when it is a reaper.
|
2014-12-15 12:01:42 +00:00
|
|
|
The
|
|
|
|
.Fa data
|
2014-12-17 01:32:27 +00:00
|
|
|
argument must point to a
|
|
|
|
.Vt procctl_reaper_status
|
|
|
|
structure which is filled in by the syscall on successful return.
|
2014-12-15 12:01:42 +00:00
|
|
|
.Bd -literal
|
|
|
|
struct procctl_reaper_status {
|
|
|
|
u_int rs_flags;
|
|
|
|
u_int rs_children;
|
|
|
|
u_int rs_descendants;
|
|
|
|
pid_t rs_reaper;
|
|
|
|
pid_t rs_pid;
|
|
|
|
};
|
|
|
|
.Ed
|
|
|
|
The
|
|
|
|
.Fa rs_flags
|
|
|
|
may have the following flags returned:
|
2019-02-26 17:35:06 +00:00
|
|
|
.Bl -tag -width REAPER_STATUS_REALINIT
|
2014-12-15 12:01:42 +00:00
|
|
|
.It Dv REAPER_STATUS_OWNED
|
2015-08-21 02:42:14 +00:00
|
|
|
The specified process has acquired reaper status and has not
|
2014-12-15 12:01:42 +00:00
|
|
|
released it.
|
2014-12-17 01:32:27 +00:00
|
|
|
When the flag is returned, the specified process
|
|
|
|
.Fa id ,
|
|
|
|
pid, identifies the reaper, otherwise the
|
2014-12-15 12:01:42 +00:00
|
|
|
.Fa rs_reaper
|
2014-12-17 01:32:27 +00:00
|
|
|
field of the structure is set to the pid of the reaper
|
|
|
|
for the specified process id.
|
2014-12-15 12:01:42 +00:00
|
|
|
.It Dv REAPER_STATUS_REALINIT
|
2015-08-21 02:42:14 +00:00
|
|
|
The specified process is the root of the reaper tree, i.e.,
|
2014-12-17 01:32:27 +00:00
|
|
|
.Xr init 8 .
|
2014-12-15 12:01:42 +00:00
|
|
|
.El
|
2014-12-21 12:36:36 +00:00
|
|
|
.Pp
|
2014-12-15 12:01:42 +00:00
|
|
|
The
|
|
|
|
.Fa rs_children
|
2015-08-21 02:42:14 +00:00
|
|
|
field returns the number of children of the reaper among the descendants.
|
|
|
|
It is possible to have a child whose reaper is not the specified process,
|
|
|
|
since the reaper for any existing children is not reset on the
|
2015-08-20 22:44:26 +00:00
|
|
|
.Dv PROC_REAP_ACQUIRE
|
|
|
|
operation.
|
2014-12-15 12:01:42 +00:00
|
|
|
The
|
|
|
|
.Fa rs_descendants
|
2014-12-17 01:32:27 +00:00
|
|
|
field returns the total number of descendants of the reaper(s),
|
|
|
|
not counting descendants of the reaper in the subtree.
|
2014-12-15 12:01:42 +00:00
|
|
|
The
|
|
|
|
.Fa rs_reaper
|
2014-12-17 01:32:27 +00:00
|
|
|
field returns the reaper pid.
|
2014-12-15 12:01:42 +00:00
|
|
|
The
|
|
|
|
.Fa rs_pid
|
2014-12-17 01:32:27 +00:00
|
|
|
returns the pid of one reaper child if there are any descendants.
|
2014-12-15 12:01:42 +00:00
|
|
|
.It Dv PROC_REAP_GETPIDS
|
|
|
|
Queries the list of descendants of the reaper of the specified process.
|
2014-12-17 01:32:27 +00:00
|
|
|
The request takes a pointer to a
|
|
|
|
.Vt procctl_reaper_pids
|
|
|
|
structure in the
|
|
|
|
.Fa data
|
|
|
|
parameter.
|
2014-12-15 12:01:42 +00:00
|
|
|
.Bd -literal
|
|
|
|
struct procctl_reaper_pids {
|
|
|
|
u_int rp_count;
|
|
|
|
struct procctl_reaper_pidinfo *rp_pids;
|
|
|
|
};
|
|
|
|
.Ed
|
2014-12-17 01:32:27 +00:00
|
|
|
When called, the
|
2014-12-15 12:01:42 +00:00
|
|
|
.Fa rp_pids
|
2014-12-17 01:32:27 +00:00
|
|
|
field must point to an array of
|
2014-12-15 12:01:42 +00:00
|
|
|
.Vt procctl_reaper_pidinfo
|
2014-12-17 01:32:27 +00:00
|
|
|
structures, to be filled in on return,
|
2014-12-15 12:01:42 +00:00
|
|
|
and the
|
|
|
|
.Fa rp_count
|
2014-12-17 01:32:27 +00:00
|
|
|
field must specify the size of the array,
|
|
|
|
into which no more than
|
|
|
|
.Fa rp_count
|
|
|
|
elements will be filled in by the kernel.
|
2014-12-15 12:01:42 +00:00
|
|
|
.Pp
|
|
|
|
The
|
|
|
|
.Vt "struct procctl_reaper_pidinfo"
|
2014-12-17 01:32:27 +00:00
|
|
|
structure provides some information about one of the reaper's descendants.
|
|
|
|
Note that for a descendant that is not a child, it may be incorrectly
|
|
|
|
identified because of a race in which the original child process exited
|
|
|
|
and the exited process's pid was reused for an unrelated process.
|
2014-12-15 12:01:42 +00:00
|
|
|
.Bd -literal
|
|
|
|
struct procctl_reaper_pidinfo {
|
|
|
|
pid_t pi_pid;
|
|
|
|
pid_t pi_subtree;
|
|
|
|
u_int pi_flags;
|
|
|
|
};
|
|
|
|
.Ed
|
|
|
|
The
|
|
|
|
.Fa pi_pid
|
2014-12-17 01:32:27 +00:00
|
|
|
field is the process id of the descendant.
|
2014-12-15 12:01:42 +00:00
|
|
|
The
|
|
|
|
.Fa pi_subtree
|
2014-12-17 01:32:27 +00:00
|
|
|
field provides the pid of the child of the reaper, which is the (grand-)parent
|
2014-12-15 12:01:42 +00:00
|
|
|
of the process.
|
|
|
|
The
|
|
|
|
.Fa pi_flags
|
2014-12-17 01:32:27 +00:00
|
|
|
field returns the following flags, further describing the descendant:
|
2019-02-26 17:35:06 +00:00
|
|
|
.Bl -tag -width REAPER_PIDINFO_REAPER
|
2014-12-15 12:01:42 +00:00
|
|
|
.It Dv REAPER_PIDINFO_VALID
|
2014-12-17 01:32:27 +00:00
|
|
|
Set to indicate that the
|
2014-12-15 12:01:42 +00:00
|
|
|
.Vt procctl_reaper_pidinfo
|
2014-12-17 01:32:27 +00:00
|
|
|
structure was filled in by the kernel.
|
2014-12-15 12:01:42 +00:00
|
|
|
Zero-filling the
|
|
|
|
.Fa rp_pids
|
2014-12-17 01:32:27 +00:00
|
|
|
array and testing the
|
|
|
|
.Dv REAPER_PIDINFO_VALID
|
|
|
|
flag allows the caller to detect the end
|
|
|
|
of the returned array.
|
2014-12-15 12:01:42 +00:00
|
|
|
.It Dv REAPER_PIDINFO_CHILD
|
|
|
|
The
|
|
|
|
.Fa pi_pid
|
2014-12-17 01:32:27 +00:00
|
|
|
field identifies the direct child of the reaper.
|
2017-11-23 11:25:11 +00:00
|
|
|
.It Dv REAPER_PIDINFO_REAPER
|
|
|
|
The reported process is itself a reaper.
|
|
|
|
The descendants of the subordinate reaper are not reported.
|
2014-12-15 12:01:42 +00:00
|
|
|
.El
|
|
|
|
.It Dv PROC_REAP_KILL
|
2014-12-17 01:32:27 +00:00
|
|
|
Request to deliver a signal to some subset of the descendants of the reaper.
|
2014-12-15 12:01:42 +00:00
|
|
|
The
|
|
|
|
.Fa data
|
2014-12-17 01:32:27 +00:00
|
|
|
parameter must point to a
|
2014-12-15 12:01:42 +00:00
|
|
|
.Vt procctl_reaper_kill
|
|
|
|
structure, which is used both for parameters and status return.
|
|
|
|
.Bd -literal
|
|
|
|
struct procctl_reaper_kill {
|
|
|
|
int rk_sig;
|
|
|
|
u_int rk_flags;
|
|
|
|
pid_t rk_subtree;
|
|
|
|
u_int rk_killed;
|
|
|
|
pid_t rk_fpid;
|
|
|
|
};
|
|
|
|
.Ed
|
|
|
|
The
|
|
|
|
.Fa rk_sig
|
2014-12-17 01:32:27 +00:00
|
|
|
field specifies the signal to be delivered.
|
2015-08-21 02:42:14 +00:00
|
|
|
Zero is not a valid signal number, unlike for
|
2014-12-15 12:01:42 +00:00
|
|
|
.Xr kill 2 .
|
|
|
|
The
|
|
|
|
.Fa rk_flags
|
2014-12-17 01:32:27 +00:00
|
|
|
field further directs the operation.
|
2014-12-15 12:01:42 +00:00
|
|
|
It is or-ed from the following flags:
|
2019-02-26 17:35:06 +00:00
|
|
|
.Bl -tag -width REAPER_KILL_CHILDREN
|
2014-12-15 12:01:42 +00:00
|
|
|
.It Dv REAPER_KILL_CHILDREN
|
|
|
|
Deliver the specified signal only to direct children of the reaper.
|
|
|
|
.It Dv REAPER_KILL_SUBTREE
|
2014-12-17 01:32:27 +00:00
|
|
|
Deliver the specified signal only to descendants that were forked by
|
|
|
|
the direct child with pid specified in the
|
|
|
|
.Fa rk_subtree
|
|
|
|
field.
|
2014-12-15 12:01:42 +00:00
|
|
|
.El
|
2014-12-17 01:32:27 +00:00
|
|
|
If neither the
|
2014-12-15 12:01:42 +00:00
|
|
|
.Dv REAPER_KILL_CHILDREN
|
2014-12-17 01:32:27 +00:00
|
|
|
nor the
|
2014-12-15 12:01:42 +00:00
|
|
|
.Dv REAPER_KILL_SUBTREE
|
|
|
|
flags are specified, all current descendants of the reaper are signalled.
|
|
|
|
.Pp
|
2014-12-17 01:32:27 +00:00
|
|
|
If a signal was delivered to any process, the return value from the request
|
2014-12-15 12:01:42 +00:00
|
|
|
is zero.
|
2014-12-17 01:32:27 +00:00
|
|
|
In this case, the
|
2014-12-15 12:01:42 +00:00
|
|
|
.Fa rk_killed
|
2014-12-17 01:32:27 +00:00
|
|
|
field identifies the number of processes signalled.
|
2014-12-15 12:01:42 +00:00
|
|
|
The
|
|
|
|
.Fa rk_fpid
|
|
|
|
field is set to the pid of the first process for which signal
|
2015-08-21 02:42:14 +00:00
|
|
|
delivery failed, e.g., due to permission problems.
|
|
|
|
If no such process exists, the
|
2014-12-15 12:01:42 +00:00
|
|
|
.Fa rk_fpid
|
2014-12-17 01:32:27 +00:00
|
|
|
field is set to -1.
|
2015-01-18 15:13:11 +00:00
|
|
|
.It Dv PROC_TRACE_CTL
|
|
|
|
Enable or disable tracing of the specified process(es), according to the
|
|
|
|
value of the integer argument.
|
2015-08-21 02:42:14 +00:00
|
|
|
Tracing includes attachment to the process using the
|
2015-01-18 15:13:11 +00:00
|
|
|
.Xr ptrace 2
|
|
|
|
and
|
|
|
|
.Xr ktrace 2 ,
|
|
|
|
debugging sysctls,
|
|
|
|
.Xr hwpmc 4 ,
|
2015-08-21 02:42:14 +00:00
|
|
|
.Xr dtrace 1 ,
|
2015-01-18 15:13:11 +00:00
|
|
|
and core dumping.
|
|
|
|
Possible values for the
|
|
|
|
.Fa data
|
|
|
|
argument are:
|
2019-02-26 17:35:06 +00:00
|
|
|
.Bl -tag -width PROC_TRACE_CTL_DISABLE_EXEC
|
2015-01-18 15:13:11 +00:00
|
|
|
.It Dv PROC_TRACE_CTL_ENABLE
|
|
|
|
Enable tracing, after it was disabled by
|
|
|
|
.Dv PROC_TRACE_CTL_DISABLE .
|
|
|
|
Only allowed for self.
|
|
|
|
.It Dv PROC_TRACE_CTL_DISABLE
|
|
|
|
Disable tracing for the specified process.
|
|
|
|
Tracing is re-enabled when the process changes the executing
|
2015-08-21 02:42:14 +00:00
|
|
|
program with the
|
2015-01-18 15:13:11 +00:00
|
|
|
.Xr execve 2
|
|
|
|
syscall.
|
|
|
|
A child inherits the trace settings from the parent on
|
|
|
|
.Xr fork 2 .
|
|
|
|
.It Dv PROC_TRACE_CTL_DISABLE_EXEC
|
|
|
|
Same as
|
|
|
|
.Dv PROC_TRACE_CTL_DISABLE ,
|
2015-08-21 02:42:14 +00:00
|
|
|
but the setting persists for the process even after
|
2015-01-18 15:13:11 +00:00
|
|
|
.Xr execve 2 .
|
|
|
|
.El
|
|
|
|
.It Dv PROC_TRACE_STATUS
|
|
|
|
Returns the current tracing status for the specified process in
|
|
|
|
the integer variable pointed to by
|
|
|
|
.Fa data .
|
|
|
|
If tracing is disabled,
|
|
|
|
.Fa data
|
|
|
|
is set to -1.
|
2015-08-21 02:42:14 +00:00
|
|
|
If tracing is enabled, but no debugger is attached by the
|
2015-01-18 15:13:11 +00:00
|
|
|
.Xr ptrace 2
|
|
|
|
syscall,
|
|
|
|
.Fa data
|
|
|
|
is set to 0.
|
|
|
|
If a debugger is attached,
|
|
|
|
.Fa data
|
|
|
|
is set to the pid of the debugger process.
|
2016-09-23 09:26:40 +00:00
|
|
|
.It Dv PROC_TRAPCAP_CTL
|
2016-09-27 11:31:53 +00:00
|
|
|
Controls the capability mode sandbox actions for the specified
|
|
|
|
sandboxed processes,
|
|
|
|
on a return from any syscall which gives either a
|
2016-09-23 09:26:40 +00:00
|
|
|
.Er ENOTCAPABLE
|
|
|
|
or
|
|
|
|
.Er ECAPMODE
|
|
|
|
error.
|
2016-09-27 11:31:53 +00:00
|
|
|
If the control is enabled, such errors from the syscalls cause
|
|
|
|
delivery of the synchronous
|
|
|
|
.Dv SIGTRAP
|
|
|
|
signal to the thread immediately before returning from the syscalls.
|
2016-09-23 09:26:40 +00:00
|
|
|
.Pp
|
|
|
|
Possible values for the
|
|
|
|
.Fa data
|
|
|
|
argument are:
|
2019-02-26 17:35:06 +00:00
|
|
|
.Bl -tag -width PROC_TRAPCAP_CTL_DISABLE
|
2016-09-23 09:26:40 +00:00
|
|
|
.It Dv PROC_TRAPCAP_CTL_ENABLE
|
|
|
|
Enable the
|
|
|
|
.Dv SIGTRAP
|
|
|
|
signal delivery on capability mode access violations.
|
|
|
|
The enabled mode is inherited by the children of the process,
|
|
|
|
and is kept after
|
|
|
|
.Xr fexecve 2
|
|
|
|
calls.
|
|
|
|
.It Dv PROC_TRAPCAP_CTL_DISABLE
|
|
|
|
Disable the signal delivery on capability mode access violations.
|
|
|
|
Note that the global sysctl
|
2017-03-16 13:19:38 +00:00
|
|
|
.Dv kern.trap_enotcap
|
2016-09-27 11:31:53 +00:00
|
|
|
might still cause the signal to be delivered.
|
|
|
|
See
|
2016-09-23 09:26:40 +00:00
|
|
|
.Xr capsicum 4 .
|
|
|
|
.El
|
|
|
|
.Pp
|
|
|
|
On signal delivery, the
|
|
|
|
.Va si_errno
|
|
|
|
member of the
|
|
|
|
.Fa siginfo
|
|
|
|
signal handler parameter is set to the syscall error value,
|
|
|
|
and the
|
|
|
|
.Va si_code
|
|
|
|
member is set to
|
|
|
|
.Dv TRAP_CAP .
|
2021-07-10 16:19:52 +00:00
|
|
|
The system call number is stored in the
|
|
|
|
.Va si_syscall
|
|
|
|
field of the
|
|
|
|
.Fa siginfo
|
|
|
|
signal handler parameter.
|
|
|
|
The other system call parameters can be read from the
|
|
|
|
.Fa ucontext_t
|
|
|
|
but the system call number is typically stored in the register
|
|
|
|
that also contains the return value and so is unavailable in the
|
|
|
|
signal handler.
|
2016-09-23 09:26:40 +00:00
|
|
|
.Pp
|
|
|
|
See
|
|
|
|
.Xr capsicum 4
|
|
|
|
for more information about the capability mode.
|
|
|
|
.It Dv PROC_TRAPCAP_STATUS
|
2016-09-27 11:31:53 +00:00
|
|
|
Return the current status of signalling capability mode access
|
2016-09-23 09:26:40 +00:00
|
|
|
violations for the specified process.
|
|
|
|
The integer value pointed to by the
|
|
|
|
.Fa data
|
|
|
|
argument is set to the
|
|
|
|
.Dv PROC_TRAPCAP_CTL_ENABLE
|
|
|
|
value if the process control enables signal delivery, and to
|
|
|
|
.Dv PROC_TRAPCAP_CTL_DISABLE
|
|
|
|
otherwise.
|
|
|
|
.Pp
|
|
|
|
See the note about sysctl
|
2017-03-16 13:19:38 +00:00
|
|
|
.Dv kern.trap_enotcap
|
2016-09-23 09:26:40 +00:00
|
|
|
above, which gives independent global control of signal delivery.
|
2018-04-20 15:19:27 +00:00
|
|
|
.It Dv PROC_PDEATHSIG_CTL
|
2018-04-18 21:31:13 +00:00
|
|
|
Request the delivery of a signal when the parent of the calling
|
|
|
|
process exits.
|
|
|
|
.Fa idtype
|
|
|
|
must be
|
|
|
|
.Dv P_PID
|
|
|
|
and
|
|
|
|
.Fa id
|
|
|
|
must be the either caller's pid or zero, with no difference in effect.
|
|
|
|
The value is cleared for child processes
|
|
|
|
and when executing set-user-ID or set-group-ID binaries.
|
2020-07-11 18:04:09 +00:00
|
|
|
.Fa data
|
2018-04-18 21:31:13 +00:00
|
|
|
must point to a value of type
|
|
|
|
.Vt int
|
|
|
|
indicating the signal
|
|
|
|
that should be delivered to the caller.
|
|
|
|
Use zero to cancel a previously requested signal delivery.
|
2018-04-20 15:19:27 +00:00
|
|
|
.It Dv PROC_PDEATHSIG_STATUS
|
2018-04-18 21:31:13 +00:00
|
|
|
Query the current signal number that will be delivered when the parent
|
|
|
|
of the calling process exits.
|
|
|
|
.Fa idtype
|
|
|
|
must be
|
|
|
|
.Dv P_PID
|
|
|
|
and
|
|
|
|
.Fa id
|
|
|
|
must be the either caller's pid or zero, with no difference in effect.
|
2020-07-11 18:04:09 +00:00
|
|
|
.Fa data
|
2018-04-18 21:31:13 +00:00
|
|
|
must point to a memory location that can hold a value of type
|
|
|
|
.Vt int .
|
|
|
|
If signal delivery has not been requested, it will contain zero
|
|
|
|
on return.
|
2019-09-03 18:56:25 +00:00
|
|
|
.It Dv PROC_STACKGAP_CTL
|
|
|
|
Controls the stack gaps in the specified process.
|
|
|
|
A stack gap is the part of the growth area for a
|
|
|
|
.Dv MAP_STACK
|
|
|
|
mapped region that is reserved and never filled by memory.
|
|
|
|
Instead, the process is guaranteed to receive a
|
|
|
|
.Dv SIGSEGV
|
|
|
|
signal on accessing pages in the gap.
|
|
|
|
Gaps protect against stack overflow corrupting memory adjacent
|
|
|
|
to the stack.
|
|
|
|
.Pp
|
|
|
|
The
|
|
|
|
.Fa data
|
|
|
|
argument must point to an integer variable containing flags.
|
|
|
|
The following flags are allowed:
|
|
|
|
.Bl -tag -width PROC_STACKGAP_DISABLE_EXEC
|
|
|
|
.It Dv PROC_STACKGAP_ENABLE
|
|
|
|
This flag is only accepted for consistency with
|
|
|
|
.Dv PROC_STACKGAP_STATUS .
|
|
|
|
If stack gaps are enabled, the flag is ignored.
|
|
|
|
If disabled, the flag causes an
|
|
|
|
.Ev EINVAL
|
|
|
|
error to be returned.
|
|
|
|
After gaps are disabled in a process, they can only be re-enabled when an
|
|
|
|
.Xr execve 2
|
|
|
|
is performed.
|
|
|
|
.It Dv PROC_STACKGAP_DISABLE
|
|
|
|
Disable stack gaps for the process.
|
|
|
|
For existing stacks, the gap is no longer a reserved part of the growth
|
|
|
|
area and can be filled by memory on access.
|
|
|
|
.It Dv PROC_STACKGAP_ENABLE_EXEC
|
|
|
|
Enable stack gaps for programs started after an
|
|
|
|
.Xr execve 2
|
|
|
|
by the specified process.
|
|
|
|
.It Dv PROC_STACKGAP_DISABLE_EXEC
|
|
|
|
Inherit disabled stack gaps state after
|
|
|
|
.Xr execve 2 .
|
|
|
|
In other words, if the currently executing program has stack gaps disabled,
|
|
|
|
they are kept disabled on exec.
|
|
|
|
If gaps were enabled, they are kept enabled after exec.
|
|
|
|
.El
|
|
|
|
.Pp
|
|
|
|
The stack gap state is inherited from the parent on
|
|
|
|
.Xr fork 2 .
|
|
|
|
.It Dv PROC_STACKGAP_STATUS
|
|
|
|
Returns the current stack gap state for the specified process.
|
|
|
|
.Fa data
|
|
|
|
must point to an integer variable, which is used to return a bitmask
|
|
|
|
consisting of the following flags:
|
|
|
|
.Bl -tag -width PROC_STACKGAP_DISABLE_EXEC
|
|
|
|
.It Dv PROC_STACKGAP_ENABLE
|
|
|
|
Stack gaps are enabled.
|
|
|
|
.It Dv PROC_STACKGAP_DISABLE
|
|
|
|
Stack gaps are disabled.
|
|
|
|
.It Dv PROC_STACKGAP_ENABLE_EXEC
|
|
|
|
Stack gaps are enabled in the process after
|
|
|
|
.Xr execve 2 .
|
|
|
|
.It Dv PROC_STACKGAP_DISABLE_EXEC
|
|
|
|
Stack gaps are disabled in the process after
|
|
|
|
.Xr execve 2 .
|
|
|
|
.El
|
procctl(2): add PROC_NO_NEW_PRIVS_CTL, PROC_NO_NEW_PRIVS_STATUS
This introduces a new, per-process flag, "NO_NEW_PRIVS", which
is inherited, preserved on exec, and cannot be cleared. The flag,
when set, makes subsequent execs ignore any SUID and SGID bits,
instead executing those binaries as if they not set.
The main purpose of the flag is implementation of Linux
PROC_SET_NO_NEW_PRIVS prctl(2), and possibly also unpriviledged
chroot.
Reviewed By: kib
Sponsored By: EPSRC
Differential Revision: https://reviews.freebsd.org/D30939
2021-07-01 08:11:11 +00:00
|
|
|
.It Dv PROC_NO_NEW_PRIVS_CTL
|
|
|
|
Allows one to ignore the SUID and SGID bits on the program
|
|
|
|
images activated by
|
|
|
|
.Xr execve 2
|
|
|
|
in the specified process and its future descendants.
|
|
|
|
The
|
|
|
|
.Fa data
|
|
|
|
parameter must point to the integer variable holding the following
|
|
|
|
value:
|
|
|
|
.Bl -tag -width PROC_NO_NEW_PRIVS_ENABLE
|
|
|
|
.It Dv PROC_NO_NEW_PRIVS_ENABLE
|
|
|
|
Request SUID and SGID bits to be ignored.
|
|
|
|
.El
|
|
|
|
.Pp
|
|
|
|
It is not possible to disable it once it has been enabled.
|
|
|
|
.It Dv PROC_NO_NEW_PRIVS_STATUS
|
|
|
|
Returns the current status of SUID/SGID enablement for the target process.
|
|
|
|
The
|
|
|
|
.Fa data
|
|
|
|
parameter must point to the integer variable, where one of the
|
|
|
|
following values is written:
|
|
|
|
.Bl -tag -width PROC_NO_NEW_PRIVS_DISABLE
|
|
|
|
.It Dv PROC_NO_NEW_PRIVS_ENABLE
|
|
|
|
.It Dv PROC_NO_NEW_PRIVS_DISABLE
|
|
|
|
.El
|
2021-09-02 00:59:10 +00:00
|
|
|
.It Dv PROC_WXMAP_CTL
|
|
|
|
Controls the 'write exclusive against execution' permissions for the
|
|
|
|
mappings in the process address space.
|
|
|
|
It overrides the global settings established by the
|
|
|
|
.Dv kern.elf{32/64}.allow_wx
|
|
|
|
sysctl,
|
|
|
|
and the corresponding bit in the ELF control note, see
|
|
|
|
.Xr elfctl 1 .
|
|
|
|
.Pp
|
|
|
|
The
|
|
|
|
.Fa data
|
|
|
|
parameter must point to the integer variable holding one of the
|
|
|
|
following values:
|
|
|
|
.Bl -tag -width PROC_WX_MAPPINGS_DISALLOW_EXEC
|
|
|
|
.It Dv PROC_WX_MAPPINGS_PERMIT
|
|
|
|
Enable creation of mappings that have both write and execute
|
|
|
|
protection attributes, in the specified process' address space.
|
|
|
|
.It Dv PROC_WX_MAPPINGS_DISALLOW_EXEC
|
|
|
|
In the new address space created by
|
|
|
|
.Xr execve 2 ,
|
|
|
|
disallow creation of mappings that have both write and execute
|
|
|
|
permissions.
|
|
|
|
.El
|
|
|
|
.Pp
|
|
|
|
Once creation of writeable and executable mappings is allowed,
|
|
|
|
it is impossible (and pointless) to disallow it.
|
|
|
|
The only way to ensure the absence of such mappings after they
|
|
|
|
were enabled in a given process, is to set the
|
|
|
|
.Dv PROC_WX_MAPPINGS_DISALLOW_EXEC
|
|
|
|
flag and
|
|
|
|
.Xr execve 2
|
|
|
|
an image.
|
|
|
|
.It Dv PROC_WXMAP_STATUS
|
|
|
|
Returns the current status of the 'write exclusive against execution'
|
|
|
|
enforcement for the specified process.
|
|
|
|
The
|
|
|
|
.Dv data
|
|
|
|
parameter must point to the integer variable, where one of the
|
|
|
|
following values is written:
|
|
|
|
.Bl -tag -width PROC_WX_MAPPINGS_DISALLOW_EXEC
|
|
|
|
.It Dv PROC_WX_MAPPINGS_PERMIT
|
|
|
|
Creation of simultaneously writable and executable mapping is permitted,
|
|
|
|
otherwise the process cannot create such mappings.
|
|
|
|
.It Dv PROC_WX_MAPPINGS_DISALLOW_EXEC
|
|
|
|
After
|
|
|
|
.Xr execve 2 ,
|
|
|
|
the new address space should disallow creation of simultaneously
|
|
|
|
writable and executable mappings.
|
|
|
|
.El
|
|
|
|
.Pp
|
|
|
|
Additionally, if the address space of the process disallows
|
|
|
|
creation of simultaneously writable and executable mappings and
|
|
|
|
it is guaranteed that no such mapping was created since address space
|
|
|
|
creation, the
|
|
|
|
.Dv PROC_WXORX_ENFORCE
|
|
|
|
flag is set in the returned value.
|
2013-09-19 18:53:42 +00:00
|
|
|
.El
|
2020-06-13 18:19:42 +00:00
|
|
|
.Sh x86 MACHINE-SPECIFIC REQUESTS
|
|
|
|
.Bl -tag -width PROC_KPTI_STATUS
|
|
|
|
.It Dv PROC_KPTI_CTL
|
|
|
|
AMD64 only.
|
|
|
|
Controls the Kernel Page Table Isolation (KPTI) option for the children
|
|
|
|
of the specified process.
|
|
|
|
For the command to work, the
|
|
|
|
.Va vm.pmap.kpti
|
|
|
|
tunable must be enabled on boot.
|
|
|
|
It is not possible to change the KPTI setting for a running process,
|
|
|
|
except at the
|
|
|
|
.Xr execve 2 ,
|
|
|
|
where the address space is reinitialized.
|
|
|
|
.Pp
|
|
|
|
The
|
|
|
|
.Fa data
|
|
|
|
parameter must point to an integer variable containing one of the
|
|
|
|
following commands:
|
|
|
|
.Bl -tag -width PROC_KPTI_CTL_DISABLE_ON_EXEC
|
|
|
|
.It Dv PROC_KPTI_CTL_ENABLE_ON_EXEC
|
|
|
|
Enable KPTI after
|
|
|
|
.Xr execve 2 .
|
|
|
|
.It Dv PROC_KPTI_CTL_DISABLE_ON_EXEC
|
|
|
|
Disable KPTI after
|
|
|
|
.Xr execve 2 .
|
|
|
|
Only root or a process having the
|
|
|
|
.Va PRIV_IO
|
|
|
|
privilege might use this option.
|
|
|
|
.El
|
|
|
|
.It Dv PROC_KPTI_STATUS
|
|
|
|
Returns the current KPTI status for the specified process.
|
2020-07-11 18:04:09 +00:00
|
|
|
.Fa data
|
|
|
|
must point to the integer variable, which returns the
|
2020-06-13 18:19:42 +00:00
|
|
|
following statuses:
|
|
|
|
.Bl -tag -width PROC_KPTI_CTL_DISABLE_ON_EXEC
|
|
|
|
.It Dv PROC_KPTI_CTL_ENABLE_ON_EXEC
|
|
|
|
.It Dv PROC_KPTI_CTL_DISABLE_ON_EXEC
|
|
|
|
.El
|
|
|
|
.Pp
|
|
|
|
The status is or-ed with the
|
|
|
|
.Va PROC_KPTI_STATUS_ACTIVE
|
|
|
|
in case KPTI is active for the current address space of the process.
|
2015-01-18 15:13:11 +00:00
|
|
|
.Sh NOTES
|
|
|
|
Disabling tracing on a process should not be considered a security
|
|
|
|
feature, as it is bypassable both by the kernel and privileged processes,
|
|
|
|
and via other system mechanisms.
|
2015-08-21 02:42:14 +00:00
|
|
|
As such, it should not be utilized to reliably protect cryptographic
|
2015-01-18 15:13:11 +00:00
|
|
|
keying material or other confidential data.
|
2021-09-02 00:59:10 +00:00
|
|
|
.Pp
|
|
|
|
Note that processes can trivially bypass the 'no simultaneously
|
|
|
|
writable and executable mappings' policy by first marking some mapping
|
|
|
|
as writeable and write code to it, then removing write and adding
|
|
|
|
execute permission.
|
|
|
|
This may be legitimately required by some programs, such as JIT compilers.
|
2013-09-19 18:53:42 +00:00
|
|
|
.Sh RETURN VALUES
|
|
|
|
If an error occurs, a value of -1 is returned and
|
|
|
|
.Va errno
|
|
|
|
is set to indicate the error.
|
|
|
|
.Sh ERRORS
|
|
|
|
The
|
|
|
|
.Fn procctl
|
|
|
|
system call
|
|
|
|
will fail if:
|
|
|
|
.Bl -tag -width Er
|
|
|
|
.It Bq Er EFAULT
|
|
|
|
The
|
2020-07-11 18:04:09 +00:00
|
|
|
.Fa data
|
2014-12-17 01:32:27 +00:00
|
|
|
parameter points outside the process's allocated address space.
|
2013-09-19 18:53:42 +00:00
|
|
|
.It Bq Er EINVAL
|
|
|
|
The
|
|
|
|
.Fa cmd
|
|
|
|
argument specifies an unsupported command.
|
|
|
|
.Pp
|
|
|
|
The
|
|
|
|
.Fa idtype
|
|
|
|
argument specifies an unsupported identifier type.
|
|
|
|
.It Bq Er EPERM
|
|
|
|
The calling process does not have permission to perform the requested
|
|
|
|
operation on any of the selected processes.
|
|
|
|
.It Bq Er ESRCH
|
|
|
|
No processes matched the requested
|
|
|
|
.Fa idtype
|
|
|
|
and
|
|
|
|
.Fa id .
|
|
|
|
.It Bq Er EINVAL
|
|
|
|
An invalid operation or flag was passed in
|
2020-07-11 18:04:09 +00:00
|
|
|
.Fa data
|
2013-09-19 18:53:42 +00:00
|
|
|
for a
|
|
|
|
.Dv PROC_SPROTECT
|
|
|
|
command.
|
2014-12-15 12:01:42 +00:00
|
|
|
.It Bq Er EPERM
|
|
|
|
The
|
|
|
|
.Fa idtype
|
|
|
|
argument is not equal to
|
|
|
|
.Dv P_PID ,
|
|
|
|
or
|
|
|
|
.Fa id
|
|
|
|
is not equal to the pid of the calling process, for
|
|
|
|
.Dv PROC_REAP_ACQUIRE
|
|
|
|
or
|
|
|
|
.Dv PROC_REAP_RELEASE
|
|
|
|
requests.
|
|
|
|
.It Bq Er EINVAL
|
2014-12-17 01:32:27 +00:00
|
|
|
Invalid or undefined flags were passed to a
|
2014-12-15 12:01:42 +00:00
|
|
|
.Dv PROC_REAP_KILL
|
|
|
|
request.
|
|
|
|
.It Bq Er EINVAL
|
2014-12-17 01:32:27 +00:00
|
|
|
An invalid or zero signal number was requested for a
|
2014-12-15 12:01:42 +00:00
|
|
|
.Dv PROC_REAP_KILL
|
|
|
|
request.
|
|
|
|
.It Bq Er EINVAL
|
|
|
|
The
|
|
|
|
.Dv PROC_REAP_RELEASE
|
|
|
|
request was issued by the
|
|
|
|
.Xr init 8
|
|
|
|
process.
|
|
|
|
.It Bq Er EBUSY
|
|
|
|
The
|
|
|
|
.Dv PROC_REAP_ACQUIRE
|
2014-12-17 01:32:27 +00:00
|
|
|
request was issued by a process that had already acquired reaper status
|
|
|
|
and has not yet released it.
|
2015-01-18 15:13:11 +00:00
|
|
|
.It Bq Er EBUSY
|
|
|
|
The
|
|
|
|
.Dv PROC_TRACE_CTL
|
|
|
|
request was issued for a process already being traced.
|
|
|
|
.It Bq Er EPERM
|
|
|
|
The
|
|
|
|
.Dv PROC_TRACE_CTL
|
2015-08-21 02:42:14 +00:00
|
|
|
request to re-enable tracing of the process
|
|
|
|
.Po Dv PROC_TRACE_CTL_ENABLE Pc ,
|
|
|
|
or to disable persistence of
|
2015-01-18 15:13:11 +00:00
|
|
|
.Dv PROC_TRACE_CTL_DISABLE
|
|
|
|
on
|
|
|
|
.Xr execve 2
|
|
|
|
was issued for a non-current process.
|
|
|
|
.It Bq Er EINVAL
|
|
|
|
The value of the integer
|
|
|
|
.Fa data
|
|
|
|
parameter for the
|
|
|
|
.Dv PROC_TRACE_CTL
|
2016-09-23 09:26:40 +00:00
|
|
|
or
|
|
|
|
.Dv PROC_TRAPCAP_CTL
|
2015-01-18 15:13:11 +00:00
|
|
|
request is invalid.
|
2018-04-18 21:31:13 +00:00
|
|
|
.It Bq Er EINVAL
|
|
|
|
The
|
2018-04-20 15:19:27 +00:00
|
|
|
.Dv PROC_PDEATHSIG_CTL
|
2018-04-18 21:31:13 +00:00
|
|
|
or
|
2018-04-20 15:19:27 +00:00
|
|
|
.Dv PROC_PDEATHSIG_STATUS
|
2018-04-18 21:31:13 +00:00
|
|
|
request referenced an unsupported
|
|
|
|
.Fa id ,
|
|
|
|
.Fa idtype
|
|
|
|
or invalid signal number.
|
2013-09-19 18:53:42 +00:00
|
|
|
.El
|
|
|
|
.Sh SEE ALSO
|
2015-01-18 15:13:11 +00:00
|
|
|
.Xr dtrace 1 ,
|
2019-04-09 10:09:59 +00:00
|
|
|
.Xr proccontrol 1 ,
|
|
|
|
.Xr protect 1 ,
|
2020-04-24 22:04:14 +00:00
|
|
|
.Xr cap_enter 2 ,
|
2014-12-15 12:01:42 +00:00
|
|
|
.Xr kill 2 ,
|
2015-01-18 15:13:11 +00:00
|
|
|
.Xr ktrace 2 ,
|
2019-07-02 19:07:17 +00:00
|
|
|
.Xr mmap 2 ,
|
|
|
|
.Xr mprotect 2 ,
|
2014-12-15 12:01:42 +00:00
|
|
|
.Xr ptrace 2 ,
|
|
|
|
.Xr wait 2 ,
|
2016-09-23 09:26:40 +00:00
|
|
|
.Xr capsicum 4 ,
|
2015-01-18 15:13:11 +00:00
|
|
|
.Xr hwpmc 4 ,
|
2014-12-15 12:01:42 +00:00
|
|
|
.Xr init 8
|
2013-09-19 18:53:42 +00:00
|
|
|
.Sh HISTORY
|
|
|
|
The
|
|
|
|
.Fn procctl
|
|
|
|
function appeared in
|
2014-01-28 21:40:10 +00:00
|
|
|
.Fx 10.0 .
|
2019-02-26 17:41:41 +00:00
|
|
|
.Pp
|
2014-12-17 01:32:27 +00:00
|
|
|
The reaper facility is based on a similar feature of Linux and
|
2014-12-15 12:01:42 +00:00
|
|
|
DragonflyBSD, and first appeared in
|
|
|
|
.Fx 10.2 .
|
2019-02-26 17:41:41 +00:00
|
|
|
.Pp
|
2018-04-18 21:31:13 +00:00
|
|
|
The
|
2018-04-20 15:19:27 +00:00
|
|
|
.Dv PROC_PDEATHSIG_CTL
|
2018-04-18 21:31:13 +00:00
|
|
|
facility is based on the prctl(PR_SET_PDEATHSIG, ...) feature of Linux,
|
|
|
|
and first appeared in
|
2018-05-12 10:11:33 +00:00
|
|
|
.Fx 11.2 .
|
2019-02-26 17:41:41 +00:00
|
|
|
.Pp
|
|
|
|
The ASLR support was added to system for the checklists compliance in
|
|
|
|
.Fx 13.0 .
|