| /linux/Documentation/admin-guide/ |
| H A D | perf-security.rst | 11 monitored processes. The data leakage is possible both in scenarios of
52 To perform security checks, the Linux implementation splits processes
53 into two categories [6]_ : a) privileged processes (whose effective user
55 processes (whose effective UID is nonzero). Privileged processes bypass
57 monitoring is fully available to privileged processes without access,
60 Unprivileged processes are subject to a full security permission check
66 independently enabled and disabled on per-thread basis for processes and
69 Unprivileged processes with enabled CAP_PERFMON capability are treated
70 as privileged processes with respect to perf_events performance
79 processes but CAP_SYS_ADMIN usage for secure monitoring and observability
[all …]
|
| H A D | cgroup-v2.rst | 116 cgroup is a mechanism to organize processes hierarchically and
122 processes. A cgroup controller is usually responsible for
129 same cgroup. On creation, all processes are put in the cgroup that
132 existing descendant processes.
137 processes which belong to the cgroups consisting the inclusive
263 Initially, only the root cgroup exists to which all processes belong.
270 "cgroup.procs". When read, it lists the PIDs of all processes which
288 A cgroup which doesn't have any children or live processes can be
290 have any children and is associated only with zombie processes is
317 the threads of a group of processes. By default, all threads of a
[all …]
|
| /linux/tools/testing/selftests/powerpc/benchmarks/ |
| H A D | context_switch.c | 279 static int processes; variable
285 if (!processes) in mutex_lock()
306 if (!processes) in mutex_unlock()
323 if (!processes) { in futex_setup()
390 { "process", no_argument, &processes, 1 },
463 if (processes) in main()
475 printf("Using %s with ", processes ? "processes" : "threads"); in main()
|
| /linux/Documentation/admin-guide/cgroup-v1/ |
| H A D | pids.rst | 21 number of processes currently in the cgroup is given by pids.current.
25 be smaller than pids.current, or attaching enough processes to the cgroup such
50 Then we create a hierarchy, set limits and attach processes to it::
64 # ( /bin/echo "Here's some processes for you." | cat )
79 # ( /bin/echo "Here's some processes for you." | cat )
84 processes from being forked at all (note that the shell itself counts towards
|
| H A D | rdma.rst | 20 set of processes can use. These processes are grouped using RDMA controller.
22 RDMA controller defines two resources which can be limited for processes of a
34 of processes can be limited. Through this controller different rdma
52 of the child processes which shares the address space, rdma resources are
57 deleted after processes migrated. This allow progress migration as well with
|
| /linux/tools/power/cpupower/ |
| H A D | TODO | 15 - Fork as many processes as there are CPUs in case the
18 -> Execute start measures via the forked processes on
21 -> Execute stop measures via the forked processes on
|
| /linux/Documentation/admin-guide/LSM/ |
| H A D | Yama.rst | 16 running state of any of their processes. For example, if one application
18 attach to other running processes (e.g. Firefox, SSH sessions, GPG agent,
43 Firefox's crash handlers, and by Wine for allowing only Wine processes
68 only processes with ``CAP_SYS_PTRACE`` may use ptrace, either with
72 no processes may use ptrace with ``PTRACE_ATTACH`` nor via
|
| /linux/Documentation/power/ |
| H A D | freezing-of-tasks.rst | 10 The freezing of tasks is a mechanism by which user space processes and some
30 try_to_freeze_tasks() that sends a fake signal to all user space processes, and
44 For user space processes try_to_freeze() is called automatically from the
129 processes, but if any of the kernel threads may cause something like this
141 3. The third reason is to prevent user space processes and some kernel threads
171 4. Another reason for freezing tasks is to prevent user space processes from
173 space processes should not notice that such a system-wide operation has
194 space processes:
196 1. Putting processes into an uninterruptible sleep distorts the load average.
198 userspace, it gets even more complicated because some userspace processes are
[all …]
|
| H A D | basic-pm-debugging.rst | 53 - test the freezing of processes
56 - test the freezing of processes and suspending of devices
59 - test the freezing of processes, suspending of devices and platform
63 - test the freezing of processes, suspending of devices, platform
67 - test the freezing of processes, suspending of devices, platform global
77 /sys/power/pm_test (eg. "devices" to test the freezing of processes and
86 Then, the kernel will try to freeze processes, suspend devices, wait a few
88 parameter), resume devices and thaw processes. If "platform" is written to
|
| /linux/Documentation/security/ |
| H A D | landlock.rst | 16 kernel and other processes point of view. Landlock's interface must therefore
19 Landlock is designed to be usable by unprivileged processes while following the
24 Any user can enforce Landlock rulesets on their processes. They are merged and
41 processes.
43 only impact the processes requesting them.
86 processes (e.g. through a Unix domain socket). Such access rights will then be
|
| /linux/tools/power/pm-graph/config/ |
| H A D | suspend-x2-proc.cfg | 2 # Proc S3 (Suspend to Mem) x2 test - includes user processes
45 # Display user processes
46 # graph user processes and cpu usage in the timeline (default: false)
|
| H A D | freeze.cfg | 45 # Display user processes
46 # graph user processes and cpu usage in the timeline (default: false)
|
| H A D | standby.cfg | 45 # Display user processes
46 # graph user processes and cpu usage in the timeline (default: false)
|
| H A D | standby-callgraph.cfg | 46 # Display user processes
47 # graph user processes and cpu usage in the timeline (default: false)
|
| H A D | freeze-dev.cfg | 45 # Display user processes
46 # graph user processes and cpu usage in the timeline (default: false)
|
| H A D | freeze-callgraph.cfg | 46 # Display user processes
47 # graph user processes and cpu usage in the timeline (default: false)
|
| /linux/security/landlock/ |
| H A D | Kconfig | 9 Landlock is a sandboxing mechanism that enables processes to restrict
14 configured and enforced by any processes for themselves using the
|
| /linux/Documentation/userspace-api/ |
| H A D | futex2.rst | 74 A futex can be either private or shared. Private is used for processes that
76 same for all processes. This allows for optimizations in the kernel. To use
78 flag. For processes that doesn't share the same memory space and therefore can
|
| /linux/Documentation/arch/riscv/ |
| H A D | vm-layout.rst | 47 … | Kernel-space virtual memory, shared between all processes:
84 … | Kernel-space virtual memory, shared between all processes:
120 … | Kernel-space virtual memory, shared between all processes:
|
| H A D | vector.rst | 16 for processes running under its domain. Calling these interfaces is not
108 processes in form of sysctl knob:
116 * 0: Do not allow Vector code to be executed as the default for new processes.
117 * 1: Allow Vector code to be executed as the default for new processes.
|
| /linux/Documentation/filesystems/fuse/ |
| H A D | fuse.rst | 232 other users' and the super user's processes
235 other users' or the super user's processes
260 undesired behavior in other users' processes, such as:
273 of other users' processes.
287 The solution to this as well as B) is not to allow processes
304 measures, that system processes will never enter non-privileged
309 disables the check for other users' processes.
316 processes in user namespaces where they're unprivileged. For this
321 set, super user's processes have unrestricted access to mounts
|
| /linux/Documentation/block/ |
| H A D | ioprio.rst | 9 The io priority feature enables users to io nice processes or process groups,
21 higher priority than any other in the system, processes from this class are
36 IOPRIO_CLASS_IDLE: This is the idle scheduling class, processes running at this
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | metafmt-pisp-be.rst | 18 The PiSP Back End processes images in tiles, and its configuration requires
41 As the ISP processes images in tiles, each set of tiles parameters describe how
|
| /linux/Documentation/locking/ |
| H A D | rt-mutex-design.rst | 35 processes, let's call them processes A, B, and C, where A is the highest
66 to understand, let's use the previous example, with processes A, B, and C again.
80 - The PI chain is an ordered series of locks and processes that cause
81 processes to inherit priorities from a previous process that is
114 - A list of processes that are blocked on a mutex.
125 differentiate between two processes that are being described together.
131 The PI chain is a list of processes and mutexes that may cause priority
172 For PI to work, the processes at the right end of these chains (or we may
174 than the processes to the left or below in the chain.
274 Now we add 4 processes that run each of these functions separately.
[all …]
|
| /linux/tools/testing/selftests/arm64/fp/ |
| H A D | TODO | 4 - Ensure ptraced processes actually see the register state visible through
|