Searched refs:corruption (Results 1 – 25 of 110) sorted by relevance
12345
| /linux-6.1.9/arch/arm64/kvm/hyp/nvhe/ |
| D | list_debug.c | 17 bool corruption = unlikely(condition); \
18 if (corruption) { \
24 corruption; \
|
| /linux-6.1.9/include/linux/ |
| D | bug.h | 83 bool corruption = unlikely(condition); \
84 if (corruption) { \
91 corruption; \
|
| /linux-6.1.9/arch/x86/kernel/ |
| 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-6.1.9/Documentation/mm/ |
| D | page_table_check.rst | 19 In case of detected corruption, the kernel is crashed. There is a small
23 is synchronous, it can help with debugging double map memory corruption issues,
|
| D | slub.rst | 233 INFO: <corruption start>-<corruption_end> <more info>
250 Can be useful if the corruption does not stop with the start of the
256 corruption by a write after free.
276 of the corruption is may be more likely found by looking at the function that
309 may be optimized further by locating the slab that experiences corruption
316 If the corruption occurs by writing after the end of the object then it
|
| D | hwpoison.rst | 23 When the current CPU tries to consume corruption the currently
26 just ignore it because no corruption has been consumed yet. Instead
|
| /linux-6.1.9/drivers/ras/ |
| D | Kconfig | 26 correctly, including avoiding data corruption, whereas Availability
30 data corruption.
|
| /linux-6.1.9/tools/testing/selftests/lkdtm/ |
| D | tests.txt | 11 CORRUPT_LIST_ADD list_add corruption
12 CORRUPT_LIST_DEL list_del corruption
|
| /linux-6.1.9/Documentation/ABI/obsolete/ |
| D | sysfs-firmware-acpi | 7 the offline failure might lead to memory corruption and crashes)
|
| /linux-6.1.9/Documentation/devicetree/bindings/reserved-memory/ |
| D | shared-dma-pool.yaml | 37 corruption. The feature on its own provides a basic level of
40 leakage and system memory corruption, the system needs to
|
| /linux-6.1.9/Documentation/filesystems/ |
| D | xfs-self-describing-metadata.rst | 25 determine the root cause of a corruption problem, but it is still mainly a
27 weren't the ultimate cause of a corruption event. It may take a few hours to a
107 determine the scope of the corruption. For example, if we have a extent btree
109 filesystem to find the owner of the block. Worse, the corruption could mean that
111 in the metadata we have no idea of the scope of the corruption. If we have an
126 whether the corruptions are related, whether there's been multiple corruption
144 modification occurred between the corruption being written and when it was
158 As such, we cannot catch all types of corruption that can occur within a block
160 metadata, or there may be corruption of interblock relationships (e.g. corrupted
|
| /linux-6.1.9/mm/ |
| 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
106 entries are added and removed to user page tables, leaking, corruption
|
| /linux-6.1.9/Documentation/driver-api/md/ |
| 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-6.1.9/Documentation/gpu/amdgpu/display/ |
| D | dc-debug.rst | 41 * There should **not** be any visual corruption
44 * There should **not** be any cursor corruption
|
| /linux-6.1.9/Documentation/sparc/ |
| 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-6.1.9/Documentation/ABI/removed/ |
| D | sysfs-mce | 23 better uptime with the risk of a crash or even corruption
|
| /linux-6.1.9/drivers/memstick/core/ |
| D | Kconfig | 15 in most cases result in data corruption.
|
| /linux-6.1.9/Documentation/devicetree/bindings/pci/ |
| D | snps,dw-pcie-ep.yaml | 53 for data corruption. CDM registers include standard PCIe configuration
|
| D | snps,dw-pcie.yaml | 66 for data corruption. CDM registers include standard PCIe configuration
|
| /linux-6.1.9/Documentation/block/ |
| 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-6.1.9/tools/perf/Documentation/ |
| D | Build.txt | 57 AddressSanitizer (or ASan) is a GCC feature that detects memory corruption bugs
|
| /linux-6.1.9/Documentation/driver-api/ |
| D | io_ordering.rst | 51 possible data corruption.
|
| /linux-6.1.9/fs/ubifs/ |
| 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-6.1.9/drivers/block/drbd/ |
| D | Kconfig | 63 512 insert data corruption on receiving side
|
| /linux-6.1.9/Documentation/devicetree/bindings/serial/ |
| D | nvidia,tegra20-hsuart.txt | 41 corruption/invalid framing errors. Parker errata suggests adjusting baud
|
12345