Home
last modified time | relevance | path

Searched refs:corruption (Results 1 – 7 of 7) sorted by relevance

/arch/arm64/kvm/hyp/nvhe/
A Dlist_debug.c17 bool corruption = unlikely(condition); \
18 if (corruption) { \
24 corruption; \
/arch/x86/kernel/
A Dcheck.c143 int corruption = 0; in check_for_bios_corruption() local
156 corruption = 1; in check_for_bios_corruption()
161 WARN_ONCE(corruption, KERN_ERR "Memory corruption detected in low memory\n"); in check_for_bios_corruption()
/arch/arm/
A DKconfig621 bool "ARM errata: Incorrect hazard handling in the SCU may lead to data corruption"
647 it behave as intended and avoiding data corruption.
662 bool "ARM errata: Faulty hazard checking in the Store Buffer may lead to data corruption"
669 corruption. This workaround sets a specific bit in the diagnostic
715 bool "ARM errata: Possible cache data corruption with hit-under-miss enabled"
719 r0p2 erratum (possible cache data corruption with
781 bool "ARM errata: A12: some seqs of opposed cond code instrs => deadlock or corruption"
788 lead to either a data corruption or a CPU deadlock. Not fixed in
831 bool "ARM errata: A17: some seqs of opposed cond code instrs => deadlock or corruption"
836 lead to either a data corruption or a CPU deadlock. Not fixed in
/arch/arm64/
A DKconfig481 for corruption, and an ISB after is sufficient to prevent younger
482 instructions from hitting the window for corruption.
522 on the AMBA 5 CHI interface, which can cause data corruption if the
557 bool "Cortex-A53: 819472: Store exclusive instructions might cause data corruption"
568 cause data corruption.
687 cause register corruption when accessing the timer registers
1010 bool "Cortex-A510: 2038923: workaround TRBE corruption with enable"
1033 bool "Cortex-A510: 1902691: workaround TRBE trace corruption"
1039 Affected Cortex-A510 core might cause trace data corruption, when being written
1068 bool "Cortex-A715: 2645198: Workaround possible [ESR|FAR]_ELx corruption"
[all …]
/arch/x86/
A DKconfig1154 kernel if it detects a problem (e.g. overheating, data corruption).
1600 bool "Check for low memory corruption"
1602 Periodically check for memory corruption in low memory, which
1613 of memory and scans it infrequently. It both detects corruption
1617 BIOS-originated corruption always affects the same memory,
1881 return address corruption. This helps mitigate ROP attacks.
/arch/
A DKconfig1456 corruption.
1481 roughly 5 bits of entropy, frustrating memory corruption
/arch/arm/mm/
A DKconfig1019 bool "PL310 errata: Background Clean & Invalidate by Way operation can cause data corruption"

Completed in 25 milliseconds