Searched refs:namespaces (Results 1 – 20 of 20) sorted by relevance
| /linux-3.4.99/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
|
| /linux-3.4.99/net/ |
| D | sysctl_net.c | 34 net_ctl_header_lookup(struct ctl_table_root *root, struct nsproxy *namespaces) in net_ctl_header_lookup() argument
36 return &namespaces->net_ns->sysctls; in net_ctl_header_lookup()
63 struct nsproxy *namespaces, struct ctl_table *table) in net_ctl_ro_header_perms() argument
65 if (net_eq(namespaces->net_ns, &init_net)) in net_ctl_ro_header_perms()
|
| /linux-3.4.99/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 | 98 - 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-3.4.99/fs/proc/ |
| D | Makefile | 23 proc-y += namespaces.o
|
| D | proc_sysctl.c | 52 struct ctl_table **pentry, struct nsproxy *namespaces);
288 lookup_header_set(struct ctl_table_root *root, struct nsproxy *namespaces) in lookup_header_set() argument
292 set = root->lookup(root, namespaces); in lookup_header_set()
964 struct ctl_table **pentry, struct nsproxy *namespaces) in sysctl_follow_link() argument
976 set = lookup_header_set(root, namespaces); in sysctl_follow_link()
|
| /linux-3.4.99/Documentation/ABI/stable/ |
| D | sysfs-firmware-efi-vars | 11 into separate namespaces through the use of a vendor
|
| /linux-3.4.99/include/linux/ |
| D | sysctl.h | 1067 struct nsproxy *namespaces);
1069 struct nsproxy *namespaces, struct ctl_table *table);
|
| /linux-3.4.99/drivers/block/ |
| D | nvme.c | 78 struct list_head namespaces; member
1500 list_add_tail(&ns->list, &dev->namespaces); in nvme_dev_add()
1502 list_for_each_entry(ns, &dev->namespaces, list) in nvme_dev_add()
1508 list_for_each_entry_safe(ns, next, &dev->namespaces, list) { in nvme_dev_add()
1528 list_for_each_entry_safe(ns, next, &dev->namespaces, list) { in nvme_dev_remove()
1599 INIT_LIST_HEAD(&dev->namespaces); in nvme_probe()
|
| /linux-3.4.99/Documentation/security/ |
| D | Yama.txt | 46 so that any otherwise allowed process (even those in external pid namespaces)
|
| D | Smack.txt | 301 namespaces and access requests are only required to match the object in
|
| /linux-3.4.99/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 | 239 namespaces/
240 - directory with various information about namespaces
|
| D | gpio.txt | 379 two logically distinct namespaces (GPIO 0 need not use IRQ 0). You can
|
| /linux-3.4.99/Documentation/networking/ |
| D | netdev-features.txt | 145 network namespaces (e.g. loopback).
|
| /linux-3.4.99/fs/ |
| D | Kconfig | 159 security.* namespaces.
|
| /linux-3.4.99/init/ |
| D | Kconfig | 809 different namespaces.
826 different IPC objects in different namespaces.
833 This allows containers, i.e. vservers, to use user namespaces
841 Support process id namespaces. This allows having multiple
843 pid namespaces. This is a building block of containers.
|
| /linux-3.4.99/drivers/tty/ |
| D | Kconfig | 118 If you want to have isolated PTY namespaces (eg: in containers),
|
| /linux-3.4.99/Documentation/cgroups/ |
| D | cgroups.txt | 85 namespaces. These all require the basic notion of a
|