| /linux/lib/ |
| H A 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 in __list_del_entry_valid_or_report()
[all...] |
| /linux/arch/x86/kernel/ |
| H A 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/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/arm64/kvm/hyp/nvhe/ |
| H A D | list_debug.c | 17 bool corruption = unlikely(condition); \
18 if (corruption) { \
24 corruption; \
|
| /linux/fs/ubifs/ |
| H A 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 …]
|
| H A 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/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/fs/xfs/ |
| H A D | xfs_error.c | 408 xfs_alert(mp, "Corruption detected. Unmount and run xfs_repair"); in xfs_corruption_error()
412 * Complain about the kinds of metadata corruption that we can't detect from a
426 "Metadata corruption detected at %pS, %s block 0x%llx", in xfs_buf_corruption_error()
457 bp->b_error == -EFSBADCRC ? "CRC error" : "corruption", in xfs_buf_verifier_error()
488 * Warnings for inode corruption problems. Don't bother with the stack
507 error == -EFSBADCRC ? "CRC error" : "corruption", in xfs_inode_verifier_error()
|
| H A D | xfs_health.c | 39 * Warn about metadata corruption that we detected but haven't fixed, and
56 /* Measure AG corruption levels. */ in xfs_health_unmount()
60 /* Measure realtime group corruption levels. */ in xfs_health_unmount()
65 * Measure fs corruption and keep the sample around for the warning. in xfs_health_unmount()
540 /* Record observations of btree corruption with the health tracking system. */
556 * Record observations of dir/attr btree corruption with the health tracking
582 * Record observations of dir/attr btree corruption with the health tracking
|
| /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/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 | 78 parser.add_argument('-c', '--corruption', help="Simulate tcp packet corruption",
85 packet_corruption=str(args.corruption)+'%'
129 # simulate packet loss, duplication and 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/fs/xfs/scrub/ |
| H A D | inode.c | 85 * constructed due to corruption problems, lock the AGI so that we can single
141 * some other metadata corruption (e.g. inode forks) prevented in xchk_setup_inode()
148 * should flag the corruption and exit to userspace to let it fix the in xchk_setup_inode()
150 * failed due to corruption. in xchk_setup_inode()
183 * If the lookup signals corruption, we'll mark this inode corrupt and in xchk_setup_inode()
209 * the inode until we can flag the corruption in xchk_inode. The in xchk_setup_inode()
210 * scrub function has to note the corruption, since we're not really in xchk_setup_inode()
808 * and a NULL inode, so flag the corruption error and return. in xchk_inode()
|
| /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/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/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.
|
| /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/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/mtd/ubi/ |
| H A 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/fs/xfs/libxfs/ |
| H A D | xfs_health.h | 21 * When scrub detects corruption in a piece of metadata it will set the
186 * a corruption.
189 * Fsck tools should call this when corruption is
|
| /linux/net/mptcp/ |
| H A D | mib.h | 31 MPTCP_MIB_DSSCORRUPTIONFALLBACK,/* DSS corruption detected, fallback */
32 MPTCP_MIB_DSSCORRUPTIONRESET, /* DSS corruption detected, MPJ subflow reset */
|
| /linux/fs/nilfs2/ |
| H A D | gcinode.c | 51 * * %-EIO - I/O error (including metadata corruption).
116 * * %-EIO - I/O error (including metadata corruption).
|