/openbmc/linux/drivers/gpu/drm/vc4/ |
H A 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 …]
|
/openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/ |
H A D | python3-itsdangerous_2.2.0.bb | 1 SUMMARY = "Various helpers to pass trusted data to untrusted environments and back."
|
/openbmc/linux/Documentation/arch/x86/ |
H A 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
|
H A 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
|
H A D | tdx.rst | 107 information in shared memory, exposing it to the untrusted hypervisor. 123 userspace are completely untrusted.
|
/openbmc/openbmc/meta-google/recipes-google/bare-metal-espi/ |
H A D | bare-metal-espi.bb | 2 DESCRIPTION = "Disable eSPI while an untrusted host OS is running"
|
/openbmc/openbmc/meta-google/recipes-google/ipmi/ |
H A D | bare-metal-active.bb | 4 is running an untrusted operating system. \
|
/openbmc/openbmc/meta-google/recipes-google/bare-metal-obmc-console/ |
H A D | bare-metal-obmc-console.bb | 2 DESCRIPTION = "Disable obmc-console while an untrusted host OS is running"
|
/openbmc/openbmc/meta-google/recipes-google/bare-metal-ipmi-kcs/ |
H A D | bare-metal-ipmi-kcs.bb | 2 DESCRIPTION = "Disable ipmi kcs while an untrusted host OS is running"
|
/openbmc/linux/Documentation/admin-guide/hw-vuln/ |
H A 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
|
H A 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
|
H A D | multihit.rst | 163 3. Virtualization with untrusted guests 165 If the guest comes from an untrusted source, the guest host kernel will need
|
H A 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
|
H A 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
|
H A D | spectre.rst | 318 If SMT is used, Spectre variant 2 attacks from an untrusted guest 584 in use, an untrusted guest running in the sibling thread can have 682 execute externally supplied untrusted code, then the mitigations can 693 3. Sandbox untrusted programs 699 This prevents untrusted programs from polluting the branch target
|
H A 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
|
/openbmc/openbmc/meta-security/recipes-security/Firejail/ |
H A D | firejail_0.9.72.bb | 6 by restricting the running environment of untrusted applications using Linux namespaces, \
|
/openbmc/linux/Documentation/ABI/testing/ |
H A D | securityfs-secrets-coco | 12 and therefore are not readable by the untrusted host.
|
H A D | sysfs-class-bdi | 123 affordable for given relatively slow (or untrusted) device. Turning
|
/openbmc/linux/drivers/pci/ |
H A D | ats.c | 45 return (dev->untrusted == 0); in pci_ats_supported()
|
/openbmc/openbmc/meta-security/meta-parsec/recipes-parsec/parsec-tool/ |
H A D | parsec-tool-crates.inc | 155 crate://crates.io/untrusted/0.7.1 \ 337 SRC_URI[untrusted-0.7.1.sha256sum] = "a156c684c91ea7d62626509bce3cb4e1d9ed5c4d978f7b4352658f96a4c26…
|
/openbmc/qemu/docs/devel/ |
H A D | secure-coding-practices.rst | 96 is therefore considered untrusted even though it is typically generated by QEMU
|
/openbmc/linux/Documentation/security/ |
H A D | landlock.rst | 15 backdoored (i.e. untrusted), Landlock's features must be safe to use from the
|
/openbmc/linux/certs/ |
H A D | Kconfig | 98 Keys in the keyring are considered entirely untrusted. Keys in this
|
/openbmc/linux/Documentation/admin-guide/aoe/ |
H A D | aoe.rst | 53 untrusted networks should be ignored as a matter of security. See
|