| /linux/arch/arm64/kvm/hyp/nvhe/ |
| H A D | list_debug.c | 17 bool corruption = unlikely(condition); \
18 if (corruption) { \
24 corruption; \
|
| /linux/include/linux/ |
| H A D | bug.h | 83 * Since detected data corruption should stop operation on the affected
89 bool corruption = unlikely(condition); \
90 if (corruption) { \
99 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 | 7 corruption. A workload of 50000 hashes, each 64 characters in size,
22 -c Simulates a percentage of packet corruption
|
| H A D | test.py | 85 packet_corruption=str(args.corruption)+'%'
|
| /linux/tools/testing/selftests/lkdtm/ |
| H A D | tests.txt | 12 CORRUPT_LIST_ADD list_add corruption
13 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/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
135 will protect the data against accidental corruption.
|
| /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/ABI/obsolete/ |
| H A D | sysfs-firmware-acpi | 7 the offline failure might lead to memory corruption and crashes)
|
| /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/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/Documentation/block/ |
| H A D | data-integrity.rst | 9 protect against data corruption. However, the detection of the
10 corruption is done at read time which could potentially be months
31 integrity of the I/O and reject it if corruption is detected. This
32 allows not only corruption prevention but also isolation of the point
|
| /linux/Documentation/mm/ |
| H A D | slub.rst | 242 INFO: <corruption start>-<corruption_end> <more info>
259 Can be useful if the corruption does not stop with the start of the
265 corruption by a write after free.
285 of the corruption is may be more likely found by looking at the function that
318 may be optimized further by locating the slab that experiences corruption
325 If the corruption occurs by writing after the end of the object then it
|
| H A D | hwpoison.rst | 21 When the current CPU tries to consume corruption the currently
24 just ignore it because no corruption has been consumed yet. Instead
|
| /linux/Documentation/ABI/removed/ |
| H A D | sysfs-mce | 23 better uptime with the risk of a crash or even corruption
|
| /linux/mm/ |
| H A D | Kconfig.debug | 19 slowdown, but helps to find certain types of memory corruption.
23 often happen for same reasons as memory corruption (e.g. double free,
32 incorrect warnings of memory corruption after a resume because free
131 entries are added and removed to user page tables, leaking, corruption
|
| /linux/drivers/memstick/core/ |
| H A D | Kconfig | 15 in most cases result in data corruption.
|
| /linux/Documentation/driver-api/ |
| H A D | io_ordering.rst | 51 possible data corruption.
|
| /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/drivers/block/drbd/ |
| H A D | Kconfig | 63 512 insert data corruption on receiving side
|
| /linux/drivers/soc/samsung/ |
| H A D | Kconfig | 71 corruption over suspend and resume. A smaller value will mean that
|
| /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
|
| /linux/tools/perf/Documentation/ |
| H A D | Build.txt | 57 AddressSanitizer (or ASan) is a GCC feature that detects memory corruption bugs
|