| /linux-4.1.27/Documentation/namespaces/ |
| D | compatibility-list.txt | 4 may have when creating tasks living in different namespaces.
8 in different other namespaces (the rows):
18 1. Both the IPC and the PID namespaces provide IDs to address
28 2. Intentionally, two equal user IDs in different user namespaces
34 The same is true for the IPC namespaces being shared - two users
35 from different user namespaces should not access the same IPC objects
|
| D | resource-control.txt | 3 of processes is allowed to switch user ids. With user namespaces
8 kernels that enable user namespaces, and it is further recommended
|
| /linux-4.1.27/Documentation/filesystems/ |
| D | sysfs-tagging.txt | 12 namespaces to see the same interface that is currently presented in
21 namespaces. A sysfs_dirent is augmented with a void *s_ns. If a
32 the contents of other namespaces' sysfs mounts. Therefore, when a
|
| D | 00-INDEX | 129 - a description of shared subtrees for namespaces.
|
| D | sharedsubtree.txt | 167 namespaces.
196 namespaces. But namespaces are associated with processes. If
197 namespaces are made first class objects with user API to
|
| /linux-4.1.27/net/ |
| D | sysctl_net.c | 30 net_ctl_header_lookup(struct ctl_table_root *root, struct nsproxy *namespaces) in net_ctl_header_lookup() argument
32 return &namespaces->net_ns->sysctls; in net_ctl_header_lookup()
|
| /linux-4.1.27/Documentation/networking/ |
| D | ipvlan.txt | 11 driver in conjuntion with network namespaces and not sure if there is use case
81 (a) Create two network namespaces - ns0, ns1
89 (c) Assign slaves to the respective network namespaces
|
| D | netdev-features.txt | 145 network namespaces (e.g. loopback).
|
| D | ip-sysctl.txt | 35 only intended to secure e.g. name servers in namespaces where
119 is reached. This also serves as a maximum limit to namespaces
|
| /linux-4.1.27/fs/proc/ |
| D | Makefile | 24 proc-y += namespaces.o
|
| D | proc_sysctl.c | 75 struct ctl_table **pentry, struct nsproxy *namespaces);
322 lookup_header_set(struct ctl_table_root *root, struct nsproxy *namespaces) in lookup_header_set() argument
326 set = root->lookup(root, namespaces); in lookup_header_set()
978 struct ctl_table **pentry, struct nsproxy *namespaces) in sysctl_follow_link() argument
990 set = lookup_header_set(root, namespaces); in sysctl_follow_link()
|
| /linux-4.1.27/include/linux/ |
| D | sysctl.h | 158 struct nsproxy *namespaces);
|
| D | nvme.h | 89 struct list_head namespaces; member
|
| /linux-4.1.27/Documentation/ABI/stable/ |
| D | sysfs-firmware-efi-vars | 11 into separate namespaces through the use of a vendor
|
| /linux-4.1.27/Documentation/ |
| D | unshare.txt | 55 resources is not possible. Since namespaces are shared by default
61 2.1 Per-security context namespaces
72 can benefit from setting up private namespaces at login and
|
| D | 00-INDEX | 330 namespaces/
331 - directory with various information about namespaces
|
| /linux-4.1.27/drivers/block/ |
| D | nvme-core.c | 2133 list_add_tail(&ns->list, &dev->namespaces); in nvme_alloc_ns()
2590 list_for_each_entry(ns, &dev->namespaces, list) { in nvme_freeze_queues()
2606 list_for_each_entry(ns, &dev->namespaces, list) { in nvme_unfreeze_queues()
2645 list_for_each_entry(ns, &dev->namespaces, list) { in nvme_dev_remove()
2715 list_for_each_entry_safe(ns, next, &dev->namespaces, list) { in nvme_free_namespaces()
2783 if (list_empty(&dev->namespaces)) in nvme_dev_ioctl()
2785 ns = list_first_entry(&dev->namespaces, struct nvme_ns, list); in nvme_dev_ioctl()
2959 INIT_LIST_HEAD(&dev->namespaces); in nvme_probe()
|
| /linux-4.1.27/Documentation/security/ |
| D | Yama.txt | 46 so that any otherwise allowed process (even those in external pid namespaces)
|
| D | Smack.txt | 464 namespaces and access requests are only required to match the object in
|
| /linux-4.1.27/fs/ |
| D | Kconfig | 156 security.* namespaces.
|
| /linux-4.1.27/init/ |
| D | Kconfig | 1165 different namespaces.
1182 different IPC objects in different namespaces.
1188 This allows containers, i.e. vservers, to use user namespaces
1191 When user namespaces are enabled in the kernel it is
1203 Support process id namespaces. This allows having multiple
1205 pid namespaces. This is a building block of containers.
|
| /linux-4.1.27/drivers/tty/ |
| D | Kconfig | 129 If you want to have isolated PTY namespaces (eg: in containers),
|
| /linux-4.1.27/Documentation/cgroups/ |
| D | cgroups.txt | 85 namespaces. These all require the basic notion of a
|
| /linux-4.1.27/Documentation/gpio/ |
| D | gpio-legacy.txt | 382 two logically distinct namespaces (GPIO 0 need not use IRQ 0). You can
|