Searched refs:untrusted (Results 1 – 25 of 33) sorted by relevance
12
| /Linux-v5.4/drivers/gpu/drm/vc4/ |
| D | vc4_validate.c | 53 void *untrusted
135 validate_bin_pos(struct vc4_exec_info *exec, void *untrusted, uint32_t pos) in validate_bin_pos() argument
140 return (untrusted - 1 == exec->bin_u + pos); in validate_bin_pos()
216 if (!validate_bin_pos(exec, untrusted, exec->args->bin_cl_size - 1)) { in validate_flush()
245 if (!validate_bin_pos(exec, untrusted, exec->args->bin_cl_size - 2)) { in validate_increment_semaphore()
259 uint32_t length = *(uint32_t *)(untrusted + 1); in validate_indexed_prim_list()
260 uint32_t offset = *(uint32_t *)(untrusted + 5); in validate_indexed_prim_list()
261 uint32_t max_index = *(uint32_t *)(untrusted + 9); in validate_indexed_prim_list()
262 uint32_t index_size = (*(uint8_t *)(untrusted + 0) >> 4) ? 2 : 1; in validate_indexed_prim_list()
297 uint32_t length = *(uint32_t *)(untrusted + 1); in validate_gl_array_primitive()
[all …]
|
| /Linux-v5.4/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 | multihit.rst | 159 3. Virtualization with untrusted guests
161 If the guest comes from an untrusted source, the guest host kernel will need
|
| D | mds.rst | 278 execute untrusted code which is supplied externally, then the mitigation
287 3. Virtualization with untrusted guests
306 SMT systems vulnerable when running untrusted code. The same rationale as
|
| D | tsx_async_abort.rst | 253 untrusted code which is supplied externally, then the mitigation can be
260 If there are untrusted applications or guests on the system, enabling TSX
|
| D | spectre.rst | 306 If SMT is used, Spectre variant 2 attacks from an untrusted guest
528 in use, an untrusted guest running in the sibling thread can have
659 execute externally supplied untrusted code, then the mitigations can
670 3. Sandbox untrusted programs
676 This prevents untrusted programs from polluting the branch target
|
| /Linux-v5.4/arch/um/ |
| D | Kconfig | 174 prompt "Enable seccomp to safely compute untrusted bytecode"
177 that may need to compute untrusted bytecode during their
|
| /Linux-v5.4/arch/microblaze/ |
| D | Kconfig | 124 bool "Enable seccomp to safely compute untrusted bytecode"
129 that may need to compute untrusted bytecode during their
|
| /Linux-v5.4/certs/ |
| D | Kconfig | 73 Keys in the keyring are considered entirely untrusted. Keys in this
|
| /Linux-v5.4/Documentation/x86/ |
| 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 | exception-tables.rst | 10 mode memory whose address has been passed by an untrusted program.
|
| /Linux-v5.4/arch/parisc/ |
| D | Kconfig | 378 prompt "Enable seccomp to safely compute untrusted bytecode"
381 that may need to compute untrusted bytecode during their
|
| /Linux-v5.4/drivers/pci/ |
| D | of.c | 45 bus->self->untrusted = true; in pci_set_bus_of_node()
|
| D | pci-acpi.c | 1231 dev->untrusted = 1; in pci_acpi_set_untrusted()
|
| D | probe.c | 1500 if (parent && parent->untrusted) in set_pcie_untrusted()
1501 dev->untrusted = true; in set_pcie_untrusted()
|
| /Linux-v5.4/Documentation/admin-guide/aoe/ |
| D | aoe.rst | 53 untrusted networks should be ignored as a matter of security. See
|
| /Linux-v5.4/arch/sparc/ |
| D | Kconfig | 236 bool "Enable seccomp to safely compute untrusted bytecode"
241 that may need to compute untrusted bytecode during their
|
| /Linux-v5.4/Documentation/networking/ |
| D | ipvlan.txt | 99 (c) If the slave device is to be put into the hostile / untrusted network
|
| /Linux-v5.4/Documentation/admin-guide/LSM/ |
| D | SafeSetID.rst | 35 other untrusted uids without full blown CAP_SETUID capabilities. The non-root
|
| /Linux-v5.4/arch/sh/ |
| D | Kconfig | 649 bool "Enable seccomp to safely compute untrusted bytecode"
653 that may need to compute untrusted bytecode during their
|
| /Linux-v5.4/drivers/iommu/ |
| D | intel-iommu.c | 384 to_pci_dev(d)->untrusted)
1426 if (!pdev->untrusted && info->ats_supported && in iommu_enable_dev_iotlb()
2490 if (!pdev->untrusted && in dmar_insert_one_dev_info()
2924 if (pdev->untrusted) in device_def_domain_type()
3607 if (intel_iommu_strict || (pdev && pdev->untrusted) || in intel_unmap()
4851 if (pdev->untrusted) in has_untrusted_dev()
|
| /Linux-v5.4/arch/s390/ |
| D | Kconfig | 842 prompt "Enable seccomp to safely compute untrusted bytecode"
846 that may need to compute untrusted bytecode during their
|
| /Linux-v5.4/Documentation/filesystems/ |
| D | overlayfs.txt | 282 Do not use metacopy=on with untrusted upper/lower directories. Otherwise
287 for untrusted layers like from a pen drive.
|
| /Linux-v5.4/arch/powerpc/ |
| D | Kconfig | 906 bool "Enable seccomp to safely compute untrusted bytecode"
911 that may need to compute untrusted bytecode during their
|
| /Linux-v5.4/arch/arm64/ |
| D | Kconfig | 952 bool "Enable seccomp to safely compute untrusted bytecode"
955 that may need to compute untrusted bytecode during their
|
12
