Searched refs:untrusted (Results 1 – 25 of 34) sorted by relevance
12
| /Linux-v6.6/drivers/gpu/drm/vc4/ |
| D | vc4_validate.c | 53 void *untrusted
139 validate_bin_pos(struct vc4_exec_info *exec, void *untrusted, uint32_t pos) in validate_bin_pos() argument
144 return (untrusted - 1 == exec->bin_u + pos); in validate_bin_pos()
224 if (!validate_bin_pos(exec, untrusted, exec->args->bin_cl_size - 1)) { in validate_flush()
253 if (!validate_bin_pos(exec, untrusted, exec->args->bin_cl_size - 2)) { in validate_increment_semaphore()
267 uint32_t length = *(uint32_t *)(untrusted + 1); in validate_indexed_prim_list()
268 uint32_t offset = *(uint32_t *)(untrusted + 5); in validate_indexed_prim_list()
269 uint32_t max_index = *(uint32_t *)(untrusted + 9); in validate_indexed_prim_list()
270 uint32_t index_size = (*(uint8_t *)(untrusted + 0) >> 4) ? 2 : 1; in validate_indexed_prim_list()
305 uint32_t length = *(uint32_t *)(untrusted + 1); in validate_gl_array_primitive()
[all …]
|
| /Linux-v6.6/Documentation/arch/x86/ |
| D | buslock.rst | 85 "untrusted" user processes on other cores. The hard real time cannot afford
86 to have any bus lock from the untrusted processes to hurt real time
88 solutions as they have no way to prevent the "untrusted" user code from
|
| D | mds.rst | 65 There is one exception, which is untrusted BPF. The functionality of
66 untrusted BPF is limited, but it needs to be thoroughly investigated
|
| D | tdx.rst | 107 information in shared memory, exposing it to the untrusted hypervisor.
123 userspace are completely untrusted.
|
| D | exception-tables.rst | 10 mode memory whose address has been passed by an untrusted program.
|
| /Linux-v6.6/Documentation/admin-guide/hw-vuln/ |
| D | l1tf.rst | 258 which run untrusted guests, reduces the attack vector space.
260 Whether the interrupts with are affine to CPUs, which run untrusted
472 3. Virtualization with untrusted guests
521 affinity to the CPUs which run the untrusted guests can depending on
590 SMT systems vulnerable when running untrusted guests with EPT enabled.
597 - If regular users run untrusted guests on their machine, then L1TF is
598 just an add on to other malware which might be embedded in an untrusted
601 There is no technical way to prevent a user from running untrusted code
|
| D | core-scheduling.rst | 167 core. But there could be small window of time during which untrusted tasks run
204 Another approach to resolve these would be to make every untrusted task on the
205 system to not trust every other untrusted task. While this could reduce
206 parallelism of the untrusted tasks, it would still solve the above issues while
|
| D | multihit.rst | 163 3. Virtualization with untrusted guests
165 If the guest comes from an untrusted source, the guest host kernel will need
|
| D | mds.rst | 281 execute untrusted code which is supplied externally, then the mitigation
290 3. Virtualization with untrusted guests
309 SMT systems vulnerable when running untrusted code. The same rationale as
|
| D | tsx_async_abort.rst | 254 untrusted code which is supplied externally, then the mitigation can be
261 If there are untrusted applications or guests on the system, enabling TSX
|
| D | spectre.rst | 319 If SMT is used, Spectre variant 2 attacks from an untrusted guest
564 in use, an untrusted guest running in the sibling thread can have
650 execute externally supplied untrusted code, then the mitigations can
661 3. Sandbox untrusted programs
667 This prevents untrusted programs from polluting the branch target
|
| D | processor_mmio_stale_data.rst | 10 provided to untrusted guests may need mitigation. These vulnerabilities are
145 is more critical, or the untrusted software has no MMIO access). Note that
|
| /Linux-v6.6/Documentation/ABI/testing/ |
| D | securityfs-secrets-coco | 12 and therefore are not readable by the untrusted host.
|
| D | sysfs-class-bdi | 123 affordable for given relatively slow (or untrusted) device. Turning
|
| /Linux-v6.6/drivers/pci/ |
| D | ats.c | 45 return (dev->untrusted == 0); in pci_ats_supported()
|
| D | probe.c | 1612 if (parent && (parent->untrusted || parent->external_facing)) in set_pcie_untrusted()
1613 dev->untrusted = true; in set_pcie_untrusted()
|
| /Linux-v6.6/Documentation/security/ |
| D | landlock.rst | 15 backdoored (i.e. untrusted), Landlock's features must be safe to use from the
|
| /Linux-v6.6/certs/ |
| D | Kconfig | 98 Keys in the keyring are considered entirely untrusted. Keys in this
|
| /Linux-v6.6/Documentation/admin-guide/aoe/ |
| D | aoe.rst | 53 untrusted networks should be ignored as a matter of security. See
|
| /Linux-v6.6/Documentation/networking/ |
| D | ipvlan.rst | 132 (c) If the slave device is to be put into the hostile / untrusted network
|
| /Linux-v6.6/Documentation/filesystems/ |
| D | overlayfs.rst | 372 Do not use metacopy=on with untrusted upper/lower directories. Otherwise
377 for untrusted layers like from a pen drive.
444 an untrusted lower layer can be used to supply validated file content
445 for all metacopy files. If additionally the untrusted lower
|
| /Linux-v6.6/Documentation/admin-guide/LSM/ |
| D | SafeSetID.rst | 35 other untrusted uids without full blown CAP_SETUID capabilities. The non-root
|
| /Linux-v6.6/arch/loongarch/ |
| D | Kconfig | 607 bool "Enable seccomp to safely compute untrusted bytecode"
612 that may need to compute untrusted bytecode during their
|
| /Linux-v6.6/Documentation/userspace-api/ |
| D | landlock.rst | 489 issues, especially when untrusted processes can manipulate them (cf.
|
| /Linux-v6.6/arch/ |
| D | Kconfig | 574 prompt "Enable seccomp to safely execute untrusted bytecode"
579 that may need to handle untrusted bytecode during their
|
12
