| /kernel/linux/linux-6.6/lib/ |
| D | list_debug.c | 17 * valid. Failures here indicate memory corruption (and possibly an exploit
26 "list_add corruption. prev is NULL.\n") || in __list_add_valid_or_report()
28 "list_add corruption. next is NULL.\n") || in __list_add_valid_or_report()
30 "list_add corruption. next->prev should be prev (%px), but was %px. (next=%px).\n", in __list_add_valid_or_report()
33 "list_add corruption. prev->next should be next (%px), but was %px. (prev=%px).\n", in __list_add_valid_or_report()
53 "list_del corruption, %px->next is NULL\n", entry) || in __list_del_entry_valid_or_report()
55 "list_del corruption, %px->prev is NULL\n", entry) || in __list_del_entry_valid_or_report()
57 "list_del corruption, %px->next is LIST_POISON1 (%px)\n", in __list_del_entry_valid_or_report()
60 "list_del corruption, %px->prev is LIST_POISON2 (%px)\n", in __list_del_entry_valid_or_report()
63 "list_del corruption. prev->next should be %px, but was %px. (prev=%px)\n", in __list_del_entry_valid_or_report()
[all …]
|
| /kernel/linux/linux-5.10/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\n", in __list_del_entry_valid()
[all …]
|
| /kernel/linux/linux-6.6/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()
|
| /kernel/linux/linux-5.10/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()
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | bug.h | 67 * Since detected data corruption should stop operation on the affected
73 bool corruption = unlikely(condition); \
74 if (corruption) { \
81 corruption; \
|
| /kernel/linux/linux-6.6/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; \
|
| /kernel/linux/linux-6.6/arch/arm64/kvm/hyp/nvhe/ |
| D | list_debug.c | 17 bool corruption = unlikely(condition); \
18 if (corruption) { \
24 corruption; \
|
| /kernel/linux/linux-5.10/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()
|
| /kernel/linux/linux-6.6/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()
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-6.6/Documentation/filesystems/ |
| 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
|
| /kernel/linux/linux-5.10/fs/xfs/ |
| D | xfs_error.c | 346 xfs_alert(mp, "Corruption detected. Unmount and run xfs_repair"); in xfs_corruption_error()
350 * Complain about the kinds of metadata corruption that we can't detect from a
364 "Metadata corruption detected at %pS, %s block 0x%llx", in xfs_buf_corruption_error()
395 bp->b_error == -EFSBADCRC ? "CRC error" : "corruption", in xfs_buf_verifier_error()
426 * Warnings for inode corruption problems. Don't bother with the stack
445 error == -EFSBADCRC ? "CRC error" : "corruption", in xfs_inode_verifier_error()
|
| /kernel/linux/linux-6.6/Documentation/mm/ |
| D | page_table_check.rst | 17 In case of most detected corruption, the kernel is crashed. There is a small
21 is synchronous, it can help with debugging double map memory corruption issues,
29 corruption in this case immediately, but that will cause read-only data to
75 still being mapped in the userspace, leading to "corruption" detected by the
|
| /kernel/linux/linux-5.10/tools/testing/selftests/lkdtm/ |
| D | tests.txt | 10 CORRUPT_LIST_ADD list_add corruption
11 CORRUPT_LIST_DEL list_del corruption
|
| /kernel/linux/linux-6.6/fs/xfs/ |
| D | xfs_error.c | 402 xfs_alert(mp, "Corruption detected. Unmount and run xfs_repair"); in xfs_corruption_error()
406 * Complain about the kinds of metadata corruption that we can't detect from a
420 "Metadata corruption detected at %pS, %s block 0x%llx", in xfs_buf_corruption_error()
451 bp->b_error == -EFSBADCRC ? "CRC error" : "corruption", in xfs_buf_verifier_error()
482 * Warnings for inode corruption problems. Don't bother with the stack
501 error == -EFSBADCRC ? "CRC error" : "corruption", in xfs_inode_verifier_error()
|
| /kernel/linux/linux-5.10/drivers/ras/ |
| D | Kconfig | 26 correctly, including avoiding data corruption, whereas Availability
30 data corruption.
|
| /kernel/linux/linux-6.6/drivers/ras/ |
| D | Kconfig | 26 correctly, including avoiding data corruption, whereas Availability
30 data corruption.
|
| /kernel/linux/linux-6.6/tools/testing/selftests/lkdtm/ |
| D | tests.txt | 11 CORRUPT_LIST_ADD list_add corruption
12 CORRUPT_LIST_DEL list_del corruption
|
| /kernel/linux/linux-6.6/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
107 entries are added and removed to user page tables, leaking, corruption
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-6.6/fs/xfs/scrub/ |
| D | inode.c | 63 * constructed due to corruption problems, lock the AGI so that we can single
113 * some other metadata corruption (e.g. inode forks) prevented in xchk_setup_inode()
120 * should flag the corruption and exit to userspace to let it fix the in xchk_setup_inode()
122 * failed due to corruption. in xchk_setup_inode()
155 * If the lookup signals corruption, we'll mark this inode corrupt and in xchk_setup_inode()
181 * the inode until we can flag the corruption in xchk_inode. The in xchk_setup_inode()
182 * scrub function has to note the corruption, since we're not really in xchk_setup_inode()
744 * and a NULL inode, so flag the corruption error and return. in xchk_inode()
|
| /kernel/linux/linux-5.10/Documentation/vm/ |
| 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
|
| /kernel/linux/linux-5.10/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
|