| /linux-3.3/Documentation/security/ |
| D | keys-request-key.txt | 9 The process starts by either the kernel requesting a service by calling
56 The two async in-kernel calls may return keys that are still in the process of
60 The userspace interface links the key to a keyring associated with the process
71 THE PROCESS
76 (1) Process A calls request_key() [the userspace syscall calls the kernel
79 (2) request_key() searches the process's subscribed keyrings to see if there's
81 and callout_info is not set, an error is returned. Otherwise the process
89 (b) An authorisation key V that refers to key U and notes that process A
105 This will permit it to then search the keyrings of process A with the
106 UID, GID, groups and security info of process A as if it was process A,
[all …]
|
| D | keys.txt | 72 are used to control what a process may do to a key from userspace, and
140 (*) Each process subscribes to three keyrings: a thread-specific keyring, a
141 process-specific keyring, and a session-specific keyring.
147 The process-specific keyring is replaced with an empty one in the child on
149 shared. execve also discards the process's process keyring and creates a
154 process can, however, replace its current session keyring with a new one
165 When a process changes its real UID, if it used to have no session key, it
168 If a process attempts to access its session key when it doesn't have one,
179 Process-specific and thread-specific keyrings are not counted towards a
192 userspace to request a key that can't be found in a process's keyrings.
[all …]
|
| D | Smack.txt | 32 start-up process. On Fedora rc5.d/S02smack is recommended.
86 A process can see the smack label it is running with by
87 reading /proc/self/attr/current. A privileged process can
88 set the process smack by writing there.
304 Process objects reflect tasks on the system and the Smack label used to access
307 from the signaler to the recipient. Debugging a process requires both reading
312 one process to another requires that the sender have write access to the
331 The Smack label of a process can be read from /proc/<pid>/attr/current. A
332 process can read its own Smack label from /proc/self/attr/current. A
333 privileged process can change its own Smack label by writing to
[all …]
|
| /linux-3.3/Documentation/ |
| D | rt-mutex-design.txt | 23 Priority inversion is when a lower priority process executes while a higher
24 priority process wants to run. This happens for several reasons, and
25 most of the time it can't be helped. Anytime a high priority process wants
26 to use a resource that a lower priority process has (a mutex for example),
27 the high priority process must wait until the lower priority process is done
30 priority process is prevented from running by a lower priority process for
35 priority process, C is the lowest, and B is in between. A tries to grab a lock
38 but by doing so, it is in fact preempting A which is a higher priority process.
63 PI is where a process inherits the priority of another process if the other
64 process blocks on a lock owned by the current process. To make this easier
[all …]
|
| D | unshare.txt | 28 as multiple execution contexts within a process. These kernels provide
47 shared resources without creating a new process. unshare is a natural
49 the concept of process/thread as a virtual machine.
54 where creating a new process to control sharing/unsharing of process
56 when creating a new process using fork or clone, unshare can benefit
64 the kernel's per-process namespace mechanism. Polyinstantiated directories,
81 decide what needs to be shared at the time of creating the process
85 ability to unshare after the process was created can be very
119 unshare - disassociate parts of the process execution context
127 unshare allows a process to disassociate parts of its execution
[all …]
|
| D | numastat.txt | 8 numa_hit A process wanted to allocate memory from this node,
10 numa_miss A process wanted to allocate memory from another node,
12 numa_foreign A process wanted to allocate on this node,
14 local_node A process ran on this node and got memory from it.
15 other_node A process ran on this node and got memory from another node.
|
| /linux-3.3/include/linux/ |
| D | prctl.h | 44 /* Get/set whether we use statistical process timing or accurate timestamp
45 * based process timing */
49 statistical process timing */
51 process timing */
53 #define PR_SET_NAME 15 /* Set process name */
54 #define PR_GET_NAME 16 /* Get process name */
56 /* Get/set process endian */
63 /* Get/set process seccomp mode */
71 /* Get/set the process' ability to use the timestamp counter instruction */
93 * This influences when the process gets killed on a memory corruption.
[all …]
|
| D | acct.h | 2 * BSD Process Accounting for Linux - Definitions
7 * BSD-style process accounting. The kernel accounting code and all
9 * process accounting log must include this file.
38 * process accounting file whenever a process exits.
51 __u32 ac_btime; /* Process Creation Time */
81 __u32 ac_pid; /* Process ID */
82 __u32 ac_ppid; /* Parent Process ID */
83 __u32 ac_btime; /* Process Creation Time */
103 /* bit set when the process ... */
|
| /linux-3.3/Documentation/trace/postprocess/ |
| D | trace-pagealloc-postprocess.pl | 10 # --read-procstat If the trace lacks process info, get it from /proc
161 die("Failed to math stat line for process name :: $statline");
176 die("Failed to match stat line process ppid:: $statline");
202 my $process = $1;
207 if ($opt_read_procstat && $process eq '') {
302 # Dump per-process stats
306 # Get the maximum process name
317 …"Process", "Pages", "Pages", "Pages", "Pages", "PCPU", "PCPU", "PCPU", "Fragment", "F…
355 my $process;
359 $process = $process_pid;
[all …]
|
| D | trace-vmscan-postprocess.pl | 8 # --read-procstat If the trace lacks process info, get it from /proc
246 die("Failed to math stat line for process name :: $statline");
277 my $process = $1;
280 if ($process eq "") {
281 $process = $last_procmap{$pid};
282 $process_pid = "$process-$pid";
284 $last_procmap{$pid} = $process;
288 if ($opt_read_procstat && $process eq '') {
444 # Dump per-process stats
448 # Get the maximum process name
[all …]
|
| /linux-3.3/Documentation/vm/ |
| D | page_migration | 5 nodes in a numa system while the process is running. This means that the
6 virtual addresses that the process sees do not change. However, the
10 by moving pages near to the processor where the process accessing that memory
13 Page migration allows a process to manually relocate the node on which its
15 a new memory policy via mbind(). The pages of process can also be relocated
16 from another process using the sys_migrate_pages() function call. The
18 process that are located on the from nodes to the destination nodes.
24 pages of a process are located. See also the numa_maps documentation in the
28 a process to a processor on a distant node. A batch scheduler or an
29 administrator may detect the situation and move the pages of the process
[all …]
|
| D | active_mm.txt | 32 - "tsk->mm" points to the "real address space". For an anonymous process,
33 tsk->mm will be NULL, for the logical reason that an anonymous process
40 The rule is that for a process with a real address space (ie tsk->mm is
44 For a anonymous process, tsk->mm == NULL, and tsk->active_mm is the
45 "borrowed" mm while the anonymous process is running. When the
46 anonymous process gets scheduled away, the borrowed address space is
|
| /linux-3.3/Documentation/accounting/ |
| D | taskstats.txt | 6 per-process statistics from the kernel to userspace.
21 "tgid", "process" and "thread group" are used interchangeably and refer to the
22 tasks that share an mm_struct i.e. the traditional Unix process. Despite the
24 leader - a process is deemed alive as long as it has any task belonging to it.
32 statistics for all tasks of the process (if tgid is specified).
48 send commands and process responses, listen for per-tid/tgid exit data,
80 the task/process for which userspace wants statistics.
111 e) TASKSTATS_TYPE_TGID: contains tgid of process to which task belongs
112 f) TASKSTATS_TYPE_STATS: contains the per-tgid stats for exiting task's process
118 Taskstats provides per-process stats, in addition to per-task stats, since
[all …]
|
| /linux-3.3/arch/powerpc/kernel/ |
| D | ptrace32.c | 81 * Read 4 bytes of the other process' storage in compat_arch_ptrace()
85 * address in the other process of the 4 bytes that is to be read in compat_arch_ptrace()
86 * (this is run in a 32-bit process looking at a 64-bit process) in compat_arch_ptrace()
97 /* Get the addr in the other process that we want to read */ in compat_arch_ptrace()
138 * Read 4 bytes out of the other process' pt_regs area in compat_arch_ptrace()
141 * addr is the offset into the other process' pt_regs structure in compat_arch_ptrace()
143 * (this is run in a 32-bit process looking at a 64-bit process) in compat_arch_ptrace()
183 * Write 4 bytes into the other process' storage in compat_arch_ptrace()
186 * 8 byte address in the other process where the 4 bytes in compat_arch_ptrace()
188 * (this is run in a 32-bit process looking at a 64-bit process) in compat_arch_ptrace()
[all …]
|
| /linux-3.3/Documentation/filesystems/caching/ |
| D | cachefiles.txt | 318 behalf of a process, and running in that process's context, and that includes a
320 because the files in the cache are inaccessible to that process, or because if
321 the process creates a file in the cache, that file may be inaccessible to other
325 fsgid and actor security label) that the process acts as - without changing the
326 security context of the process when it the target of an operation performed by
327 some other process (so signalling and suchlike still work correctly).
338 (2) Finds the security label of the process which issued the bind request
351 type_transition <daemon's-ID> kernel_t : process <module's-ID>;
355 type_transition cachefilesd_t kernel_t : process cachefiles_kernel_t;
411 when it acts on behalf of another process, in that process's context.
[all …]
|
| /linux-3.3/tools/perf/util/ |
| D | header.h | 90 int (*process)(struct perf_file_section *section,
102 perf_event__handler_t process);
105 perf_event__handler_t process);
110 perf_event__handler_t process,
113 perf_event__handler_t process,
120 perf_event__handler_t process);
126 perf_event__handler_t process,
|
| /linux-3.3/Documentation/block/ |
| D | ioprio.txt | 10 processes or process groups, similar to what has been possible with cpu
18 served for a process.
23 care, one io RT process can starve the entire system. Within the RT class,
25 process needs the disk for on each service. In the future this might change
30 for any process that hasn't set a specific io priority. The class data
31 determines how much io bandwidth the process will get, it's directly mappable
47 If pid isn't given, the current process is assumed. IO priority settings
48 are inherited on fork, so you can use ionice to start the process at a given
54 For a running process, you can give the pid instead:
|
| /linux-3.3/Documentation/development-process/ |
| D | 1.Intro | 1 1: A GUIDE TO THE KERNEL DEVELOPMENT PROCESS
8 there is some technical material here, this is very much a process-oriented
15 The rest of this section covers the scope of the kernel development process
23 Section 2 introduces the development process, the kernel release cycle, and
33 Section 4 is about the coding process; several pitfalls which have been
38 Section 5 talks about the process of posting patches for review. To be
46 development process; this section offers a number of tips on how to avoid
82 process. But, if anything, the kernel is even more open than most other
93 surprising that Linux kernel development process differs greatly from
96 The kernel's development process may come across as strange and
[all …]
|
| /linux-3.3/Documentation/filesystems/ |
| D | mandatory-locking.txt | 17 A process may then see file data change even while a mandatory
21 read has actually completed, and the reading process may see
34 normally a process' responsibility to check for locks on a file it wishes to
47 block attempts by a process to write to a file that another process holds a
49 file that a process holds a "write " -or- "exclusive" lock on.
90 another process has outstanding mandatory locks. This is in direct
122 2. If a process has locked a region of a file with a mandatory read lock, then
125 released, unless the process has opened the file with the O_NONBLOCK
129 3. If a process has locked a region of a file with a mandatory write lock, all
131 unless a process has opened the file with the O_NONBLOCK flag in which case
|
| D | proc.txt | 23 1.1 Process-Specific Subdirectories
35 3 Per-Process Parameters
114 1.1 Process-Specific Subdirectories
118 process running on the system, which is named after the process ID (PID).
120 The link self points to the process reading the file system. Each process
124 Table 1-1: Process specific entries in /proc
132 exe Link to the executable of this process
135 mem Memory held by this process
136 root Link to the root directory of this process
137 stat Process status
[all …]
|
| /linux-3.3/arch/mips/kernel/ |
| D | ptrace32.c | 40 * Tracing a 32-bit process with a 64-bit strace and vice versa will not
53 * Read 4 bytes of the other process' storage in compat_arch_ptrace()
57 * address in the other process of the 4 bytes that is to be read in compat_arch_ptrace()
58 * (this is run in a 32-bit process looking at a 64-bit process) in compat_arch_ptrace()
69 /* Get the addr in the other process that we want to read */ in compat_arch_ptrace()
198 * Write 4 bytes into the other process' storage in compat_arch_ptrace()
201 * 8 byte address in the other process where the 4 bytes in compat_arch_ptrace()
203 * (this is run in a 32-bit process looking at a 64-bit process) in compat_arch_ptrace()
210 /* Get the addr in the other process that we want to write into */ in compat_arch_ptrace()
|
| /linux-3.3/Documentation/RCU/ |
| D | UP.txt | 17 elements A, B, and C in process context, and can delete elements from
18 this same list in softirq context. Suppose that the process-context scan
36 from process context. However, this can fail in a similar manner.
39 elements A, B, and C in process contexts, but that it invokes a function
112 RCU callback, then a process-context acquisition of this
116 If the process-context code were to simply use spin_lock(),
119 the process-context critical section. This would result in
|
| /linux-3.3/include/trace/events/ |
| D | signal.h | 32 * Current process sends a 'sig' signal to 'task' process with
70 * A 'sig' signal is delivered to current process with 'info' siginfo,
130 * @group: signal to process group or not (bool)
135 * 'group' is not 0 if the signal will be sent to a process group.
148 * @group: signal to process group or not (bool)
153 * 'group' is not 0 if the signal will be sent to a process group.
|
| /linux-3.3/Documentation/infiniband/ |
| D | user_verbs.txt | 40 This also allows the kernel to clean up when a process exits and
41 prevent one process from touching another process's resources.
49 amount of memory pinned in the process's locked_vm, and checks that
54 number of pages pinned by a process.
|
| /linux-3.3/mm/ |
| D | process_vm_access.c | 156 * @addr: start memory address of target process
224 /* Maximum number of entries for process pages array
230 * @pid: PID of process to read/write from/to
233 * @rvec: iovec array specifying where to copy to/from in the other process
236 * @vm_write: 0 if reading from other process, 1 if writing to other process
239 * process.
290 /* Get process information */ in process_vm_rw_core()
344 * @pid: PID of process to read/write from/to
347 * @rvec: iovec array specifying where to copy to/from in the other process
350 * @vm_write: 0 if reading from other process, 1 if writing to other process
[all …]
|