Searched full:restrictions (Results 1 – 25 of 455) sorted by relevance
12345678910>>...19
| /Linux-v5.10/Documentation/firmware-guide/acpi/ |
| D | acpi-lid.rst | 22 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
|
| /Linux-v5.10/include/uapi/linux/ |
| D | capability.h | 121 /* 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 */
|
| /Linux-v5.10/Documentation/admin-guide/LSM/ |
| D | SafeSetID.rst | 6 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
|
| D | Yama.rst | 45 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.
|
| /Linux-v5.10/Documentation/devicetree/bindings/interrupt-controller/ |
| D | msi.txt | 22 MSI controllers may have restrictions on permitted payloads.
70 If a device has restrictions on the allocation of MSIs, these restrictions
|
| /Linux-v5.10/include/video/ |
| D | imx-ipu-image-convert.h | 57 * 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,
|
| /Linux-v5.10/drivers/gpu/drm/ |
| D | drm_encoder.c | 40 * 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
|
| /Linux-v5.10/Documentation/core-api/ |
| D | memory-allocation.rst | 83 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
|
| /Linux-v5.10/Documentation/misc-devices/ |
| D | xilinx_sdfec.rst | 138 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:
|
| /Linux-v5.10/Documentation/powerpc/ |
| D | vas-api.rst | 105 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.
|
| /Linux-v5.10/Documentation/gpu/ |
| D | vkms.rst | 101 Atomic drivers have lots of restrictions which are not exposed to userspace in
107 implement a library of different restrictions.
|
| /Linux-v5.10/arch/m68k/math-emu/ |
| D | fp_emu.h | 21 * required INSTEAD OF the above restrictions. (This clause is
23 * the restrictions contained in a BSD-style copyright.)
|
| D | fp_move.S | 21 * required INSTEAD OF the above restrictions. (This clause is
23 * the restrictions contained in a BSD-style copyright.)
|
| D | fp_cond.S | 21 * required INSTEAD OF the above restrictions. (This clause is
23 * the restrictions contained in a BSD-style copyright.)
|
| /Linux-v5.10/Documentation/admin-guide/ |
| D | abi-stable.rst | 7 restrictions, and backward compatibility for them will be guaranteed
|
| /Linux-v5.10/tools/testing/selftests/powerpc/mm/ |
| D | pkey_siginfo.c | 109 /* No read, write and execute restrictions */ in protect()
214 * Restore the restrictions originally imposed by the in protect_access()
279 * AMR and IAMR, i.e. impose no restrictions, for all available in test()
|
| /Linux-v5.10/security/safesetid/ |
| D | Kconfig | 10 approved by a system-wide whitelist. These restrictions also prohibit
|
| /Linux-v5.10/Documentation/ABI/testing/ |
| D | sysfs-devices-system-xen_cpu | 20 logic restrictions and assumptions.
|
| /Linux-v5.10/Documentation/devicetree/bindings/i2c/ |
| D | i2c.txt | 91 states that additional SMBus restrictions and features apply to this bus.
93 restrictions are more reserved addresses and timeout definitions.
|
| /Linux-v5.10/LICENSES/deprecated/ |
| D | GPL-1.0 | 38 To protect your rights, we need to make restrictions that forbid
40 These restrictions translate to certain responsibilities for you if you
156 terms and conditions. You may not impose any further restrictions on the
|
| D | Zlib | 20 to the following restrictions:
|
| /Linux-v5.10/LICENSES/exceptions/ |
| D | GCC-exception-2.0 | 16 this file. (The General Public License restrictions do apply in other
|
| /Linux-v5.10/fs/minix/ |
| D | Kconfig | 11 because of certain built-in restrictions, but it is sometimes found
|
| /Linux-v5.10/Documentation/devicetree/bindings/leds/backlight/ |
| D | common.yaml | 33 due to restrictions in a specific system, such as mounting conditions.
|
| /Linux-v5.10/arch/powerpc/include/asm/book3s/64/ |
| D | mmu.h | 231 * Hash has more strict restrictions. At this point we don't in setup_initial_memory_limit()
233 * restrictions. in setup_initial_memory_limit()
|
12345678910>>...19
