Lines Matching refs:of
5 provides an overview of the feature, why it is needed, how it can
27 Most legacy operating system kernels support an abstraction of threads
34 power of implementing threads in this manner comes not only from
36 outside the confinement of all-or-nothing shared resources of legacy
37 threads. On Linux, at the time of thread creation using the clone system
43 shared at the time of their creation. unshare was conceptualized by
44 Al Viro in the August of 2000, on the Linux-Kernel mailing list, as part
45 of the discussion on POSIX threads on Linux. unshare augments the
46 usefulness of Linux threads for applications that would like to control
48 addition to the set of available primitives on Linux that implement
49 the concept of process/thread as a virtual machine.
54 where creating a new process to control sharing/unsharing of process
65 such as per-user and/or per-security context instance of /tmp, /var/tmp or
66 per-security context instance of a user's home directory, isolate user
71 of shared-tree feature in the Linux kernel, even regular Linux systems
76 2.2 unsharing of virtual memory and/or open files
81 decide what needs to be shared at the time of creating the process
83 disassociate parts of the context during the servicing of the
97 review of the changes and creation of an unshare test for the LTP
98 the benefits of this new feature can exceed its cost.
107 the meaning of the flags from the way they are used in clone(2).
111 unshare interface should accommodate possible future addition of
112 new context flags without requiring a rebuild of old applications.
114 incremental unsharing of those resources on an as needed basis.
119 unshare - disassociate parts of the process execution context
127 unshare allows a process to disassociate parts of its execution
129 of execution context, such as the namespace, is shared by default
135 The main use of unshare is to allow a process to control its
138 The flags argument specifies one or bitwise-or'ed of several of
142 If CLONE_FS is set, file system information of the caller
146 If CLONE_FILES is set, the file descriptor table of the
151 If CLONE_NEWNS is set, the namespace of the caller is
155 If CLONE_VM is set, the virtual memory of the caller is
165 ENOMEM Cannot allocate sufficient memory to copy parts of caller's
183 versions. Helper functions of clone (copy_*) could not be used
184 directly by unshare because of the following two reasons.
193 to backout due to an error. Consider the case of unsharing
197 reverse the unsharing of vm. As part of the reversal the
219 Implementation of unshare can be grouped in the following 4 different
221 a) Reorganization of existing copy_* functions
224 d) Registration of system call number for different architectures
226 7.1) Reorganization of copy_* functions
272 namespace without specifying unsharing of filesystem, correctly
274 3) For each of the four (namespace, filesystem, files and vm)
280 an address in the shm segment to synchronize execution of
281 about 10 threads. Have a couple of threads execute execve,
283 of flags. Verify that unsharing is performed as expected and
288 The current implementation of unshare does not allow unsharing of
290 to unshare signals and/or signal handlers of a currently running
292 need to allow unsharing of signals and/or signal handlers, it can