Home
last modified time | relevance | path

Searched full:restrictions (Results 1 – 25 of 1024) sorted by relevance

12345678910>>...41

/kernel/linux/linux-6.6/Documentation/gpu/amdgpu/display/
Dmpo-overview.rst62 every DCN has different restrictions; here, we are just trying to provide the
65 Plane Restrictions
68 AMDGPU imposes restrictions on the use of DRM planes in the driver.
71 restrictions:
83 Cursor Restrictions
86 Before we start to describe some restrictions around cursor and MPO, see the
184 many more restrictions for a multi-display scenario. The below example shows a
/kernel/linux/linux-6.6/Documentation/firmware-guide/acpi/
Dacpi-lid.rst22 exceptional buggy platforms, special restrictions and exceptions should be
23 taken into account. This document describes the restrictions and the
27 Restrictions of the returning value of the _LID control method
39 Restrictions of the lid state change notifications
/kernel/linux/linux-5.10/Documentation/firmware-guide/acpi/
Dacpi-lid.rst22 exceptional buggy platforms, special restrictions and exceptions should be
23 taken into account. This document describes the restrictions and the
27 Restrictions of the returning value of the _LID control method
39 Restrictions of the lid state change notifications
/kernel/linux/linux-6.6/Documentation/userspace-api/
Dlandlock.rst43 kernel and user space may not know each other's supported restrictions), hence
173 security policy; only adding more restrictions is allowed. These threads are
246 restrictions from its parent. This is similar to the seccomp inheritance (cf.
259 Ptrace restrictions
263 then be subject to additional restrictions when manipulating another process.
403 restricted. However, thanks to the `ptrace restrictions`_, access to such
434 restrict access to files, also implies inheritance of the ruleset restrictions
478 Using user space process to enforce restrictions on kernel resources can lead
488 fine-grained restrictions). Moreover, their complexity can lead to security
/kernel/linux/linux-5.10/include/uapi/linux/
Dcapability.h121 /* Overrides all DAC restrictions regarding read and search on files
122 and directories, including ACL restrictions if [_POSIX_ACL] is
127 /* Overrides all restrictions about allowed operations on files, where
129 is applicable. It doesn't override MAC and DAC restrictions. */
133 /* Overrides the following restrictions that the effective user ID
303 /* Override size restrictions on IPC message queues */
/kernel/linux/linux-6.6/include/uapi/linux/
Dcapability.h122 /* Overrides all DAC restrictions regarding read and search on files
123 and directories, including ACL restrictions if [_POSIX_ACL] is
128 /* Overrides all restrictions about allowed operations on files, where
130 is applicable. It doesn't override MAC and DAC restrictions. */
134 /* Overrides the following restrictions that the effective user ID
303 /* Override size restrictions on IPC message queues */
/kernel/linux/linux-6.6/Documentation/admin-guide/LSM/
DSafeSetID.rst6 system-wide allowlist. These restrictions also prohibit the given UIDs/GIDs
37 additional restrictions imposed by this LSM would mean it is a "safer" version
114 setgroups() calls for processes with CAP_SETGID restrictions. Until we add
116 policies add no meaningful security. setgroups() restrictions will be enforced
DYama.rst45 restrictions, it can call ``prctl(PR_SET_PTRACER, PR_SET_PTRACER_ANY, ...)``
75 The original children-only logic was based on the restrictions in grsecurity.
/kernel/linux/linux-5.10/Documentation/admin-guide/LSM/
DSafeSetID.rst6 system-wide allowlist. These restrictions also prohibit the given UIDs/GIDs
37 additional restrictions imposed by this LSM would mean it is a "safer" version
114 setgroups() calls for processes with CAP_SETGID restrictions. Until we add
116 policies add no meaningful security. setgroups() restrictions will be enforced
DYama.rst45 restrictions, it can call ``prctl(PR_SET_PTRACER, PR_SET_PTRACER_ANY, ...)``
75 The original children-only logic was based on the restrictions in grsecurity.
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/interrupt-controller/
Dmsi.txt22 MSI controllers may have restrictions on permitted payloads.
70 If a device has restrictions on the allocation of MSIs, these restrictions
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/interrupt-controller/
Dmsi.txt22 MSI controllers may have restrictions on permitted payloads.
70 If a device has restrictions on the allocation of MSIs, these restrictions
/kernel/linux/linux-5.10/include/video/
Dimx-ipu-image-convert.h57 * ipu_image_convert_adjust() - adjust input/output images to IPU restrictions.
70 * and rotation mode meet IPU restrictions.
76 * Returns 0 if the formats and rotation mode meet IPU restrictions,
/kernel/linux/linux-6.6/include/video/
Dimx-ipu-image-convert.h57 * ipu_image_convert_adjust() - adjust input/output images to IPU restrictions.
70 * and rotation mode meet IPU restrictions.
76 * Returns 0 if the formats and rotation mode meet IPU restrictions,
/kernel/linux/linux-6.6/Documentation/gpu/rfc/
Di915_small_bar.rst37 Error Capture restrictions
39 With error capture we have two new restrictions:
/kernel/linux/linux-6.6/Documentation/mm/
Dhighmem.rst88 come with restrictions about the pointers validity. Contrary to kmap()
108 restrictions imposed on kmap_local_page(). Furthermore, the code between
134 restrictions imposed on kmap_local_page(). In particular, it is necessary to
141 restrictions on preemption or migration. It comes with an overhead as mapping
/kernel/linux/linux-6.6/drivers/cxl/
Dacpi.c123 static unsigned long cfmws_to_decoder_flags(int restrictions) in cfmws_to_decoder_flags() argument
127 if (restrictions & ACPI_CEDT_CFMWS_RESTRICT_TYPE2) in cfmws_to_decoder_flags()
129 if (restrictions & ACPI_CEDT_CFMWS_RESTRICT_TYPE3) in cfmws_to_decoder_flags()
131 if (restrictions & ACPI_CEDT_CFMWS_RESTRICT_VOLATILE) in cfmws_to_decoder_flags()
133 if (restrictions & ACPI_CEDT_CFMWS_RESTRICT_PMEM) in cfmws_to_decoder_flags()
135 if (restrictions & ACPI_CEDT_CFMWS_RESTRICT_FIXED) in cfmws_to_decoder_flags()
256 cxld->flags = cfmws_to_decoder_flags(cfmws->restrictions); in __cxl_parse_cfmws()
/kernel/linux/linux-6.6/security/landlock/
Dfs.c307 * @domain: The domain that defines the current restrictions.
351 * Check that a destination file hierarchy has more restrictions than a source
374 * Checks if the destination restrictions are a in no_more_access()
377 * restrictions(parent2) >= restrictions(child1) in no_more_access()
390 * Checks inverted restrictions for RENAME_EXCHANGE: in no_more_access()
391 * restrictions(parent1) >= restrictions(child2) in no_more_access()
475 * This helper first checks that the destination has a superset of restrictions
563 * least as much as restrictions on the destination than on the in is_access_to_paths_allowed()
794 * if the destination one has more (or the same) restrictions as the source
910 * hierarchy is not a superset of restrictions of the source directory in current_check_refer_path()
/kernel/linux/linux-6.6/security/integrity/
DKconfig78 bool "Enforce Machine Keyring CA Restrictions"
83 on any key added to it. By default no restrictions are in place
/kernel/linux/linux-6.6/Documentation/core-api/
Dmemory-allocation.rst83 driver for a device with such restrictions, avoid using these flags.
84 And even with hardware with restrictions it is preferable to use
161 will be retried with `vmalloc`. There are restrictions on which GFP
/kernel/linux/linux-5.10/drivers/gpu/drm/
Ddrm_encoder.c40 * userspace to infer cloning and connector/CRTC restrictions. Unfortunately
42 * top of that the exposed restrictions are too simple for today's hardware, and
43 * the recommended way to infer restrictions is by using the
/kernel/linux/linux-5.10/Documentation/core-api/
Dmemory-allocation.rst83 driver for a device with such restrictions, avoid using these flags.
84 And even with hardware with restrictions it is preferable to use
157 will be retried with `vmalloc`. There are restrictions on which GFP
/kernel/linux/linux-6.6/Documentation/misc-devices/
Dxilinx_sdfec.rst138 Setting the order can only be done if the following restrictions are met:
155 Adding LDPC codes can only be done if the following restrictions are met:
166 Adding Turbo decode can only be done if the following restrictions are met:
186 Bypassing the SD-FEC can only be done if the following restrictions are met:
/kernel/linux/linux-5.10/Documentation/misc-devices/
Dxilinx_sdfec.rst138 Setting the order can only be done if the following restrictions are met:
155 Adding LDPC codes can only be done if the following restrictions are met:
166 Adding Turbo decode can only be done if the following restrictions are met:
186 Bypassing the SD-FEC can only be done if the following restrictions are met:
/kernel/linux/linux-5.10/Documentation/powerpc/
Dvas-api.rst105 error codes and restrictions.
162 restrictions.
174 Only restrictions on mmap for a NX-GZIP device fd are:
179 Refer to mmap(2) man page for additional details/restrictions.

12345678910>>...41