| /Linux-v5.4/Documentation/sphinx/ |
| D | load_config.py | 9 def loadConfig(namespace): argument
21 and os.path.normpath(namespace["__file__"]) != os.path.normpath(config_file) ):
35 latex_documents = namespace['latex_documents']
44 namespace['latex_documents'] = new_latex_docs
49 config = namespace.copy()
53 namespace.update(config)
55 config = namespace.copy()
57 namespace.update(config)
|
| /Linux-v5.4/Documentation/admin-guide/sysctl/ |
| D | user.rst | 16 per user per user namespace limits.
24 The creation of per user per user namespace objects are charged to
25 the user in the user namespace who created the object and
26 verified to be below the per user limit in that user namespace.
34 user namespace does not allow a user to escape their current limits.
42 user namespace may create.
48 user namespace may create.
54 user namespace may create.
60 current user namespace may create.
66 user namespace may create.
[all …]
|
| /Linux-v5.4/Documentation/core-api/ |
| D | symbol-namespaces.rst | 25 documentation purposes (think of the SUBSYSTEM_DEBUG namespace) as well as for
28 are required to import the namespace. Otherwise the kernel will, depending on
34 Symbols can be exported into namespace using different methods. All of them are
43 available to export symbols into a certain namespace: EXPORT_SYMBOL_NS() and
44 EXPORT_SYMBOL_NS_GPL(). They take one additional argument: the namespace.
47 namespace `USB_STORAGE`, use::
52 `namespace` set accordingly. A symbol that is exported without a namespace will
53 refer to `NULL`. There is no default namespace if none is defined. `modpost`
54 and kernel/module.c make use the namespace at build time or module load time,
63 and EXPORT_SYMBOL_GPL() macro expansions that do not specify a namespace.
[all …]
|
| /Linux-v5.4/Documentation/filesystems/ |
| D | sysfs-tagging.txt | 8 namespace active multiple devices with the same name can show up in
15 By using the network namespace pointers as tags to separate out the
20 Each sysfs directory entry may be tagged with a namespace via the
23 and KOBJ_NS_TYPES, and ns will point to the namespace to which it
27 *ns[KOBJ_NS_TYPES]. When a task in a tagging namespace
30 s_fs_info->ns[kobj_nstype] set to the new namespace. Note that
33 namespace exits, it will call kobj_ns_exit() to invalidate any
39 - current_ns() which returns current's namespace
40 - netlink_ns() which returns a socket's namespace
|
| D | sharedsubtree.txt | 20 A process wants to clone its own namespace, but still wants to access the CD
24 It provides the necessary building blocks for features like per-user-namespace
152 A) A process wants to clone its own namespace, but still wants to
161 Now any process that clones off a new namespace will have a
163 parent namespace.
179 A new process can clone off a new namespace. And mark some part
180 of its namespace as slave
185 process will not show up in any other namespace. However mounts
186 done in the parent namespace under /myprivatetree still shows
187 up in the process's namespace.
[all …]
|
| /Linux-v5.4/Documentation/firmware-guide/acpi/ |
| D | namespace.rst | 17 The Linux ACPI subsystem converts ACPI namespace objects into a Linux
42 data structure called the ACPI namespace whose topology reflects the
83 All definition blocks are loaded into a single namespace. The namespace
86 namespace:
93 5. The '\' symbol represents the root of the namespace (i.e. names
94 prepended with '\' are relative to the namespace root).
95 6. The '^' symbol represents the parent of the current namespace node
97 current namespace node).
99 The figure below shows an example ACPI namespace::
106 +-| _PR | Scope(_PR): the processor namespace
[all …]
|
| D | enumeration.rst | 12 SoC/Chipset to appear only in ACPI namespace. These are typically devices
31 the ACPI namespace.
34 enumerated from ACPI namespace. This handle can be used to extract other
153 Here is what the ACPI namespace for a SPI slave might look like::
350 parts of the ACPI namespace that relate to them. In the Linux MFD subsystem
360 If the ACPI namespace has a device that we can match using an ACPI id or ACPI
378 Device Tree namespace link device ID
384 regarded as a device identification namespace analogous to the ACPI/PNP device
385 ID namespace. Consequently, in principle it should not be necessary to allocate
387 identification string in the Device Tree (DT) namespace, especially if that ID
[all …]
|
| D | aml-debugger.rst | 73 the entire ACPI namespace::
75 # acpidbg -b "namespace"
|
| /Linux-v5.4/Documentation/admin-guide/namespaces/ |
| D | compatibility-list.rst | 9 occur when tasks share some namespace (the columns) while living
28 other task living in a different namespace via a shared filesystem
30 within the namespace it was obtained in and may refer to some
31 other object in another namespace.
35 words, user 10 in one user namespace shouldn't have the same
37 namespace.
|
| /Linux-v5.4/Documentation/admin-guide/LSM/ |
| D | SafeSetID.rst | 8 allowing a user to set up user namespace UID mappings.
40 namespace). The higher level goal is to allow for uid-based sandboxing of system
69 namespace and give programs in the tree setid capabilities. In this way,
71 own user namespace, and only approved UIDs/GIDs could be mapped back to the
72 initial system user namespace, affectively preventing privilege escalation.
74 without pairing them with other namespace types, which is not always an option.
75 Linux checks for capabilities based off of the user namespace that ???owns??? some
77 the user namespace in which they were created. A consequence of this is that
78 capability checks for access to a given network namespace are done by checking
79 whether a task has the given capability in the context of the user namespace
[all …]
|
| /Linux-v5.4/Documentation/driver-api/acpi/ |
| D | scan_handlers.rst | 12 During system initialization and ACPI-based device hot-add, the ACPI namespace
15 registered with the driver core for every device object in the ACPI namespace
16 and the hierarchy of those struct acpi_device objects reflects the namespace
17 layout (i.e. parent device objects in the namespace are represented by parent
26 The core ACPI namespace scanning code in drivers/acpi/scan.c carries out basic
54 The namespace scanning function, acpi_bus_scan(), first registers all of the
55 device nodes in the given namespace scope with the driver core. Then, it tries
68 the namespace scan should be terminated due to a serious error. The error code
71 The namespace trimming function, acpi_bus_trim(), first executes .detach()
72 callbacks from the scan handlers of all device nodes in the given namespace
[all …]
|
| /Linux-v5.4/tools/testing/selftests/tc-testing/plugin-lib/ |
| D | nsPlugin.py | 19 if self.args.namespace:
30 if self.args.namespace:
50 if not self.args.namespace:
85 if not self.args.namespace:
99 if self.args.namespace:
117 if self.args.namespace:
|
| /Linux-v5.4/drivers/infiniband/hw/mlx5/ |
| D | flow.c | 23 enum mlx5_flow_namespace_type *namespace) in mlx5_ib_ft_type_to_namespace() argument
27 *namespace = MLX5_FLOW_NAMESPACE_BYPASS; in mlx5_ib_ft_type_to_namespace()
30 *namespace = MLX5_FLOW_NAMESPACE_EGRESS; in mlx5_ib_ft_type_to_namespace()
33 *namespace = MLX5_FLOW_NAMESPACE_FDB; in mlx5_ib_ft_type_to_namespace()
36 *namespace = MLX5_FLOW_NAMESPACE_RDMA_RX; in mlx5_ib_ft_type_to_namespace()
352 enum mlx5_flow_namespace_type namespace; in mlx5_ib_create_modify_header() local
356 ret = mlx5_ib_ft_type_to_namespace(ft_type, &namespace); in mlx5_ib_create_modify_header()
365 mlx5_modify_header_alloc(dev->mdev, namespace, num_actions, in); in mlx5_ib_create_modify_header()
480 enum mlx5_flow_namespace_type namespace; in mlx5_ib_flow_action_create_packet_reformat_ctx() local
484 ret = mlx5_ib_ft_type_to_namespace(ft_type, &namespace); in mlx5_ib_flow_action_create_packet_reformat_ctx()
[all …]
|
| /Linux-v5.4/scripts/mod/ |
| D | modpost.c | 169 char *namespace; member
242 const char *namespace) in contains_namespace() argument
247 if (strcmp(ns_entry->namespace, namespace) == 0) in contains_namespace()
253 static void add_namespace(struct namespace_list **list, const char *namespace) in add_namespace() argument
257 if (!contains_namespace(*list, namespace)) { in add_namespace()
259 strlen(namespace) + 1)); in add_namespace()
260 strcpy(ns_entry->namespace, namespace); in add_namespace()
267 const char *namespace) in module_imports_namespace() argument
269 return contains_namespace(module->imported_namespaces, namespace); in module_imports_namespace()
358 static void sym_update_namespace(const char *symname, const char *namespace) in sym_update_namespace() argument
[all …]
|
| /Linux-v5.4/tools/perf/util/c++/ |
| D | clang.h | 11 namespace perf {
13 using namespace llvm;
|
| /Linux-v5.4/Documentation/driver-api/nvdimm/ |
| D | nvdimm.rst | 38 libnvdimm: namespace
39 libndctl: namespace enumeration example
40 libndctl: namespace creation example
41 Why the Term "namespace"?
221 BLK-namespace can be configured with a BTT with unique atomic sector
223 not provide for a sector size to be specified for a PMEM namespace.
259 single PMEM namespace is created in the REGION0-SPA-range that spans most
269 well as DIMM2 and DIMM3. Some of REGION1 is allocated to a PMEM namespace
486 "nstype" indicates the integer type of namespace-device this region
577 1. There are already more than two REGION and "namespace" types. For
[all …]
|
| /Linux-v5.4/drivers/nvdimm/ |
| D | Kconfig | 13 namespaces (/dev/ndblkX.Y). A PMEM namespace refers to a
15 (see CONFIG_DAX). A BLK namespace refers to an NVDIMM control
69 NVDIMM namespace, i.e. a namespace can be in raw mode (pmemX,
99 namespace. For environments that want to hard partition
101 sub-divide a namespace into character devices that can only be
|
| /Linux-v5.4/scripts/coccinelle/misc/ |
| D | add_namespace.cocci | 5 /// This script is usually called from scripts/nsdeps with -D ns=<namespace> to
6 /// add a missing namespace tag to a module source file.
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | sysfs-devices-firmware_node | 15 namespace. This attribute is read-only. If the device does not have
16 an _STR method associated with it in the ACPI namespace, this
|
| /Linux-v5.4/drivers/net/ethernet/mellanox/mlx5/core/ |
| D | fs_cmd.h | 83 enum mlx5_flow_namespace_type namespace,
90 u8 namespace, u8 num_actions,
|
| /Linux-v5.4/tools/testing/selftests/tc-testing/ |
| D | README | 6 execute them inside a network namespace dedicated to the task.
15 * The kernel must have network namespace support if using nsPlugin
58 network namespace and creates a veth pair which may be used in those test
59 cases. To disable execution within the namespace, pass the -N option
161 options for nsPlugin (run commands in net namespace)
163 -N, --no-namespace
164 Do not run commands in a network namespace.
233 sets up a network namespace and runs all commands in that namespace,
|
| /Linux-v5.4/Documentation/userspace-api/ |
| D | unshare.rst | 60 from default shared namespace. The following lists two use-cases
67 the kernel's per-process namespace mechanism. Polyinstantiated directories,
71 module can easily setup a private namespace for a user at login.
136 of execution context, such as the namespace, is shared by default
158 If CLONE_NEWNS is set, the namespace of the caller is
159 disassociated from the shared namespace.
204 both virtual memory and namespace. After successfully unsharing
206 new namespace structure, the error return code will have to
306 namespace without specifying unsharing of filesystem, correctly
307 unshares both namespace and filesystem information.
[all …]
|
| /Linux-v5.4/scripts/gdb/linux/ |
| D | proc.py | 166 namespace = task['nsproxy']['mnt_ns']
167 if not namespace:
170 for vfs in lists.list_for_each_entry(namespace['list'],
|
| /Linux-v5.4/kernel/cgroup/ |
| D | Makefile | 2 obj-y := cgroup.o rstat.o namespace.o cgroup-v1.o freezer.o
|
| /Linux-v5.4/ipc/ |
| D | Makefile | 10 obj-$(CONFIG_IPC_NS) += namespace.o
|
