| /linux/arch/arm64/kvm/hyp/nvhe/ |
| H A D | list_debug.c | 17 bool corruption = unlikely(condition); \ 18 if (corruption) { \ 24 corruption; \
|
| /linux/arch/x86/kernel/ |
| H A D | check.c | 143 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 D | README.txt | 10 corruption. A passing test means the RDS stack was able to recover 28 -c Simulates a percentage of packet corruption
|
| H A D | test.py | 365 # 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 D | tests.txt | 16 CORRUPT_LIST_ADD list_add corruption 17 CORRUPT_LIST_DEL list_del corruption
|
| /linux/drivers/ras/ |
| H A D | Kconfig | 26 correctly, including avoiding data corruption, whereas Availability 30 data corruption.
|
| /linux/Documentation/ABI/obsolete/ |
| H A D | sysfs-firmware-acpi | 7 the offline failure might lead to memory corruption and crashes)
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | dm-flakey.rst | 73 0 and 1000000000 meaning 0% to 100% probability of corruption. 78 0 and 1000000000 meaning 0% to 100% probability of corruption.
|
| H A D | dm-integrity.rst | 26 corruption on the disk or in the I/O path. 33 twice, but it is also less reliable, because if data corruption happens 140 will protect the data against accidental corruption.
|
| H A D | writecache.rst | 59 promoted, to avoid data corruption due to misordered
|
| /linux/Documentation/filesystems/xfs/ |
| H A D | xfs-self-describing-metadata.rst | 26 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 D | raid5-ppl.rst | 9 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/ABI/removed/ |
| H A D | sysfs-mce | 23 better uptime with the risk of a crash or even corruption
|
| /linux/Documentation/arch/sparc/ |
| H A D | adi.rst | 97 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/drivers/memstick/core/ |
| H A D | Kconfig | 15 in most cases result in data corruption.
|
| /linux/Documentation/admin-guide/mm/ |
| H A D | slab.rst | 241 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/Documentation/userspace-api/ |
| H A D | mseal.rst | 10 permission feature improves security stance on memory corruption bugs, i.e. 15 modifications. This is useful to mitigate memory corruption issues where a 139 attributes. This is useful to mitigate memory corruption issues where a
|
| /linux/Documentation/driver-api/ |
| H A D | io_ordering.rst | 51 possible data corruption.
|
| /linux/Documentation/arch/riscv/ |
| H A D | zicfilp.rst | 16 Memory corruption issues usually result in crashes. However, in the 26 to corruption. This can allow an adversary to control the program
|
| /linux/drivers/soc/samsung/ |
| H A D | Kconfig | 71 corruption over suspend and resume. A smaller value will mean that
|
| /linux/drivers/block/drbd/ |
| H A D | Kconfig | 63 512 insert data corruption on receiving side
|
| /linux/fs/ubifs/ |
| H A D | recovery.c | 687 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/Documentation/arch/arm64/ |
| H A D | kdump.rst | 10 kernel if corruption happens.
|
| /linux/tools/perf/Documentation/ |
| H A D | Build.txt | 57 AddressSanitizer (or ASan) is a GCC feature that detects memory corruption bugs
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-devices-platform-stratix10-rsu | 36 0xF003 bitstream corruption
|