| /Linux-v6.1/lib/ |
| D | list_debug.c | 16 * valid. Failures here indicate memory corruption (and possibly an exploit
24 "list_add corruption. prev is NULL.\n") || in __list_add_valid()
26 "list_add corruption. next is NULL.\n") || in __list_add_valid()
28 "list_add corruption. next->prev should be prev (%px), but was %px. (next=%px).\n", in __list_add_valid()
31 "list_add corruption. prev->next should be next (%px), but was %px. (prev=%px).\n", in __list_add_valid()
50 "list_del corruption, %px->next is NULL\n", entry) || in __list_del_entry_valid()
52 "list_del corruption, %px->prev is NULL\n", entry) || in __list_del_entry_valid()
54 "list_del corruption, %px->next is LIST_POISON1 (%px)\n", in __list_del_entry_valid()
57 "list_del corruption, %px->prev is LIST_POISON2 (%px)\n", in __list_del_entry_valid()
60 "list_del corruption. prev->next should be %px, but was %px. (prev=%px)\n", in __list_del_entry_valid()
[all …]
|
| /Linux-v6.1/arch/x86/kernel/ |
| D | check.c | 136 pr_info("Scanning %d areas for low memory corruption\n", num_scan_areas); in setup_bios_corruption_check()
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()
179 pr_info("Scanning for low memory corruption every %d seconds\n", corruption_check_period); in start_periodic_check_for_corruption()
|
| /Linux-v6.1/include/linux/ |
| D | bug.h | 77 * Since detected data corruption should stop operation on the affected
83 bool corruption = unlikely(condition); \
84 if (corruption) { \
91 corruption; \
|
| /Linux-v6.1/arch/arm64/kvm/hyp/nvhe/ |
| D | list_debug.c | 17 bool corruption = unlikely(condition); \
18 if (corruption) { \
24 corruption; \
|
| /Linux-v6.1/fs/ubifs/ |
| D | recovery.c | 22 * from corruption caused by other reasons. And UBIFS tries to distinguish
34 * not true, the corruption cannot be the result of a power cut, and UBIFS
81 * get_master_node - get the last valid master node allowing for corruption.
86 * @cor: corruption, if found, is returned here
89 * returns the last valid master node allowing for one area of corruption.
134 /* Could have been corruption so check one place back */ in get_master_node()
141 * We accept only one area of corruption because in get_master_node()
159 /* Check for corruption */ in get_master_node()
163 dbg_rcvry("found corruption at %d:%d", lnum, offs); in get_master_node()
222 * This function recovers the master node from corruption that may occur due to
[all …]
|
| D | scan.c | 219 * ubifs_scanned_corruption - print information after UBIFS scanned corruption.
221 * @lnum: LEB number of corruption
222 * @offs: offset of corruption
223 * @buf: buffer containing corruption
230 ubifs_err(c, "corruption at LEB %d:%d", lnum, offs); in ubifs_scanned_corruption()
|
| /Linux-v6.1/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-v6.1/fs/xfs/ |
| D | xfs_error.c | 370 xfs_alert(mp, "Corruption detected. Unmount and run xfs_repair"); in xfs_corruption_error()
374 * Complain about the kinds of metadata corruption that we can't detect from a
388 "Metadata corruption detected at %pS, %s block 0x%llx", in xfs_buf_corruption_error()
419 bp->b_error == -EFSBADCRC ? "CRC error" : "corruption", in xfs_buf_verifier_error()
450 * Warnings for inode corruption problems. Don't bother with the stack
469 error == -EFSBADCRC ? "CRC error" : "corruption", in xfs_inode_verifier_error()
|
| D | xfs_health.c | 19 * Warn about metadata corruption that we detected but haven't fixed, and
36 /* Measure AG corruption levels. */ in xfs_health_unmount()
45 /* Measure realtime volume corruption levels. */ in xfs_health_unmount()
53 * Measure fs corruption and keep the sample around for the warning. in xfs_health_unmount()
|
| /Linux-v6.1/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-v6.1/drivers/ras/ |
| D | Kconfig | 26 correctly, including avoiding data corruption, whereas Availability
30 data corruption.
|
| /Linux-v6.1/tools/testing/selftests/lkdtm/ |
| D | tests.txt | 11 CORRUPT_LIST_ADD list_add corruption
12 CORRUPT_LIST_DEL list_del corruption
|
| /Linux-v6.1/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-v6.1/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-v6.1/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-v6.1/Documentation/mm/ |
| 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 | 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,
|
| /Linux-v6.1/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-v6.1/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-v6.1/tools/testing/selftests/powerpc/mm/ |
| D | tlbie_test.c | 75 * A "corruption" is defined to be the failed COMPARE operation in a
78 * A rim_thread that detects a corruption informs about it to all the
528 * any rim_thread has found a corruption. in rim_fn()
533 * a corruption :( in rim_fn()
574 /* Stop memory migration once corruption is found */ in mem_snapshot_fn()
588 * so corruption does not appear to be introduced at the in mem_snapshot_fn()
726 printf(" Data Corruption Detected\n"); in main()
|
| /Linux-v6.1/fs/xfs/scrub/ |
| D | common.h | 113 * a fs corruption. This is intended for callers checking an ondisk reference
140 * Don't bother cross-referencing if we already found corruption or cross
|
| /Linux-v6.1/Documentation/admin-guide/device-mapper/ |
| 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
130 will protect the data against accidental corruption.
|
| /Linux-v6.1/Documentation/ABI/obsolete/ |
| D | sysfs-firmware-acpi | 7 the offline failure might lead to memory corruption and crashes)
|
| /Linux-v6.1/drivers/mtd/ubi/ |
| D | attach.c | 46 * When UBI detects a corruption (CRC-32 mismatch) in a PEB, and it looks like
58 * scanning). UBI assumes corruption type 2 if the VID header is corrupted and
61 * area. Otherwise UBI assumes corruption type 1. So the decision criteria
64 * to just erase this PEB - this is corruption type 1.
67 * happened, so this is corruption type 1. However, this is just a guess,
69 * o Otherwise this is corruption type 2.
264 * physical eraseblock @pnum and adds it to the 'corr' list. The corruption
868 * If the corruption reason was a power cut, UBI can safely erase this PEB.
885 * It is difficult to say for sure what type of corruption is in check_corruption()
902 …ubi_err(ubi, "this may be a non-UBI PEB or a severe VID header corruption which requires manual in… in check_corruption()
[all …]
|
| /Linux-v6.1/arch/sparc/kernel/ |
| D | sun4v_mcd.S | 2 /* sun4v_mcd.S: Sun4v memory corruption detected precise exception handler
|
