Searched refs:corruption (Results 1 – 25 of 95) sorted by relevance
1234
| /Linux-v4.19/include/linux/ |
| D | bug.h | 68 bool corruption = unlikely(condition); \
69 if (corruption) { \
76 corruption; \
|
| /Linux-v4.19/arch/x86/kernel/ |
| D | check.c | 123 int corruption = 0; in check_for_bios_corruption() local
137 corruption = 1; in check_for_bios_corruption()
142 WARN_ONCE(corruption, KERN_ERR "Memory corruption detected in low memory\n"); in check_for_bios_corruption()
|
| /Linux-v4.19/drivers/ras/ |
| D | Kconfig | 25 correctly, including avoiding data corruption, whereas Availability
29 data corruption.
|
| /Linux-v4.19/Documentation/ABI/obsolete/ |
| D | sysfs-firmware-acpi | 7 the offline failure might lead to memory corruption and crashes)
|
| /Linux-v4.19/Documentation/filesystems/ |
| D | xfs-self-describing-metadata.txt | 22 determine the root cause of a corruption problem, but it is still mainly a
24 weren't the ultimate cause of a corruption event. It may take a few hours to a
104 determine the scope of the corruption. For example, if we have a extent btree
106 filesystem to find the owner of the block. Worse, the corruption could mean that
108 in the metadata we have no idea of the scope of the corruption. If we have an
123 whether the corruptions are related, whether there's been multiple corruption
141 modification occurred between the corruption being written and when it was
155 As such, we cannot catch all types of corruption that can occur within a block
157 metadata, or there may be corruption of interblock relationships (e.g. corrupted
|
| /Linux-v4.19/Documentation/md/ |
| D | raid5-ppl.txt | 7 disks is missing. This can lead to silent data corruption when rebuilding the
34 silent data corruption. If a dirty disk of a stripe is lost, no PPL recovery is
|
| /Linux-v4.19/mm/ |
| D | Kconfig.debug | 19 slowdown, but helps to find certain types of memory corruption.
25 that would result in incorrect warnings of memory corruption after
|
| /Linux-v4.19/Documentation/vm/ |
| D | slub.rst | 206 INFO: <corruption start>-<corruption_end> <more info>
223 Can be useful if the corruption does not stop with the start of the
229 corruption by a write after free.
249 of the corruption is may be more likely found by looking at the function that
282 may be optimized further by locating the slab that experiences corruption
289 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-v4.19/Documentation/sparc/ |
| D | adi.txt | 93 Disrupting memory corruption
98 the corresponding cacheline, a memory corruption trap occurs. By
112 Precise memory corruption
117 the corresponding cacheline, a memory corruption trap occurs. If
|
| /Linux-v4.19/drivers/memstick/core/ |
| D | Kconfig | 14 in most cases result in data corruption.
|
| /Linux-v4.19/Documentation/block/ |
| D | data-integrity.txt | 5 protect against data corruption. However, the detection of the
6 corruption is done at read time which could potentially be months
27 integrity of the I/O and reject it if corruption is detected. This
28 allows not only corruption prevention but also isolation of the point
|
| /Linux-v4.19/Documentation/ |
| D | io_ordering.txt | 51 possible data corruption.
|
| /Linux-v4.19/drivers/staging/vc04_services/interface/vchi/ |
| D | TODO | 30 leads to data corruption during the following command:
|
| /Linux-v4.19/fs/ubifs/ |
| D | recovery.c | 698 int corruption = first_non_ff(buf, len); in ubifs_recover_leb() local
705 lnum, offs, corruption); in ubifs_recover_leb()
707 offs += corruption; in ubifs_recover_leb()
708 buf += corruption; in ubifs_recover_leb()
|
| /Linux-v4.19/drivers/block/drbd/ |
| D | Kconfig | 64 512 insert data corruption on receiving side
|
| /Linux-v4.19/arch/arm/kernel/ |
| D | asm-offsets.c | 47 #error and result in filesystem corruption and oopses.
|
| /Linux-v4.19/Documentation/hwmon/ |
| D | max16065 | 69 power loss, board resets, and/or Flash corruption. Worst case, your board may
|
| D | zl6100 | 84 and/or Flash corruption. Worst case, your board may turn into a brick.
|
| /Linux-v4.19/Documentation/x86/x86_64/ |
| D | machinecheck | 56 with the risk of a crash or even corruption (for tolerant >= 3).
|
| /Linux-v4.19/Documentation/arm/Samsung-S3C24XX/ |
| D | Suspend.txt | 117 suspend to see if there has been any corruption of the contents.
|
| /Linux-v4.19/Documentation/device-mapper/ |
| D | dm-integrity.txt | 22 corruption on the disk or in the I/O path.
107 will protect the data against accidental corruption.
|
| D | dm-raid.txt | 332 target version, thus avoiding data corruption on a raid set
342 1.10.1 Fix data corruption on reshape request
352 deadlock/potential data corruption. Update superblock when
|
| /Linux-v4.19/Documentation/cdrom/ |
| D | packet-writing.txt | 82 filesystem corruption if the disc wears out.
|
| D | ide-cd | 327 f. Data corruption.
329 - Random data corruption was occasionally observed with the Hitachi
330 CDR-7730 CDROM. If you experience data corruption, using "hdx=slow"
|
1234
