Home
last modified time | relevance | path

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

123

/linux/arch/arm64/kvm/hyp/nvhe/
H A Dlist_debug.c17 bool corruption = unlikely(condition); \
18 if (corruption) { \
24 corruption; \
/linux/arch/x86/kernel/
H 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()
/linux/tools/testing/selftests/net/rds/
H A DREADME.txt10 corruption. A passing test means the RDS stack was able to recover
28 -c Simulates a percentage of packet corruption
H A Dtest.py365 # simulate packet loss, duplication and corruption
455 # simulate packet loss, duplication and corruption
487 parser.add_argument('-c', '--corruption', help="Simulate tcp packet corruption",
494 PACKET_CORRUPTION=str(args.corruption)+'%'
/linux/tools/testing/selftests/lkdtm/
H A Dtests.txt16 CORRUPT_LIST_ADD list_add corruption
17 CORRUPT_LIST_DEL list_del corruption
/linux/Documentation/ABI/obsolete/
H A Dsysfs-firmware-acpi7 the offline failure might lead to memory corruption and crashes)
/linux/Documentation/admin-guide/device-mapper/
H A Ddm-flakey.rst73 0 and 1000000000 meaning 0% to 100% probability of corruption.
78 0 and 1000000000 meaning 0% to 100% probability of corruption.
H A Dwritecache.rst59 promoted, to avoid data corruption due to misordered
/linux/Documentation/filesystems/xfs/
H A Dxfs-self-describing-metadata.rst26 determine the root cause of a corruption problem, but it is still mainly a
28 weren't the ultimate cause of a corruption event. It may take a few hours to a
108 determine the scope of the corruption. For example, if we have a extent btree
110 filesystem to find the owner of the block. Worse, the corruption could mean that
112 in the metadata we have no idea of the scope of the corruption. If we have an
127 whether the corruptions are related, whether there's been multiple corruption
145 modification occurred between the corruption being written and when it was
159 As such, we cannot catch all types of corruption that can occur within a block
161 metadata, or there may be corruption of interblock relationships (e.g. corrupted
/linux/Documentation/driver-api/md/
H A Draid5-ppl.rst9 disks is missing. This can lead to silent data corruption when rebuilding the
36 silent data corruption. If a dirty disk of a stripe is lost, no PPL recovery is
/linux/Documentation/arch/sparc/
H A Dadi.rst97 Disrupting memory corruption
103 the corresponding cacheline, a memory corruption trap occurs. By
117 Precise memory corruption
123 the corresponding cacheline, a memory corruption trap occurs. If
/linux/Documentation/ABI/removed/
H A Dsysfs-mce23 better uptime with the risk of a crash or even corruption
/linux/Documentation/admin-guide/mm/
H A Dslab.rst241 INFO: <corruption start>-<corruption_end> <more info>
258 Can be useful if the corruption does not stop with the start of the
264 corruption by a write after free.
284 of the corruption is may be more likely found by looking at the function that
317 may be optimized further by locating the slab that experiences corruption
324 If the corruption occurs by writing after the end of the object then it
/linux/drivers/memstick/core/
H A DKconfig15 in most cases result in data corruption.
/linux/Documentation/driver-api/
H A Dio_ordering.rst51 possible data corruption.
/linux/Documentation/arch/riscv/
H A Dzicfilp.rst16 Memory corruption issues usually result in crashes. However, in the
26 to corruption. This can allow an adversary to control the program
/linux/fs/ubifs/
H A Drecovery.c687 int corruption = first_non_ff(buf, len); in ubifs_recover_leb() local
694 lnum, offs, corruption); in ubifs_recover_leb()
696 offs += corruption; in ubifs_recover_leb()
697 buf += corruption; in ubifs_recover_leb()
/linux/drivers/soc/samsung/
H A DKconfig71 corruption over suspend and resume. A smaller value will mean that
/linux/drivers/block/drbd/
H A DKconfig63 512 insert data corruption on receiving side
/linux/Documentation/arch/arm64/
H A Dkdump.rst10 kernel if corruption happens.
/linux/tools/perf/Documentation/
H A DBuild.txt57 AddressSanitizer (or ASan) is a GCC feature that detects memory corruption bugs
/linux/arch/arm/
H A DKconfig637 bool "ARM errata: Incorrect hazard handling in the SCU may lead to data corruption"
663 it behave as intended and avoiding data corruption.
678 bool "ARM errata: Faulty hazard checking in the Store Buffer may lead to data corruption"
685 corruption. This workaround sets a specific bit in the diagnostic
731 bool "ARM errata: Possible cache data corruption with hit-under-miss enabled"
735 r0p2 erratum (possible cache data corruption with
797 bool "ARM errata: A12: some seqs of opposed cond code instrs => deadlock or corruption"
804 lead to either a data corruption or a CPU deadlock. Not fixed in
847 bool "ARM errata: A17: some seqs of opposed cond code instrs => deadlock or corruption"
852 lead to either a data corruption or a CPU deadlock. Not fixed in
/linux/security/
H A DKconfig.hardening265 bool "Trigger a BUG when data corruption is detected"
269 data corruption in kernel memory structures when they get checked
/linux/Documentation/networking/device_drivers/fddi/
H A Dskfp.rst253 - data corruption with kernel versions below 2.0.33.
/linux/Documentation/mm/
H A Dvmalloced-kernel-stacks.rst65 immediately rather than causing difficult-to-diagnose corruption.

123