Searched refs:corruption (Results 1 – 25 of 103) sorted by relevance
12345
| /Linux-v5.4/include/linux/ |
| D | bug.h | 73 bool corruption = unlikely(condition); \
74 if (corruption) { \
81 corruption; \
|
| /Linux-v5.4/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-v5.4/drivers/ras/ |
| D | Kconfig | 26 correctly, including avoiding data corruption, whereas Availability
30 data corruption.
|
| /Linux-v5.4/Documentation/ABI/obsolete/ |
| D | sysfs-firmware-acpi | 7 the offline failure might lead to memory corruption and crashes)
|
| /Linux-v5.4/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
|
| /Linux-v5.4/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-v5.4/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-v5.4/Documentation/vm/ |
| D | slub.rst | 212 INFO: <corruption start>-<corruption_end> <more info>
229 Can be useful if the corruption does not stop with the start of the
235 corruption by a write after free.
255 of the corruption is may be more likely found by looking at the function that
288 may be optimized further by locating the slab that experiences corruption
295 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-v5.4/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-v5.4/drivers/memstick/core/ |
| D | Kconfig | 15 in most cases result in data corruption.
|
| /Linux-v5.4/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-v5.4/tools/perf/Documentation/ |
| D | Build.txt | 57 AddressSanitizer (or ASan) is a GCC feature that detects memory corruption bugs
|
| /Linux-v5.4/Documentation/ |
| D | io_ordering.txt | 51 possible data corruption.
|
| /Linux-v5.4/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-v5.4/drivers/block/drbd/ |
| D | Kconfig | 63 512 insert data corruption on receiving side
|
| /Linux-v5.4/Documentation/devicetree/bindings/pci/ |
| D | designware-pcie.txt | 38 for data corruption. CDM registers include standard PCIe configuration
|
| /Linux-v5.4/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-v5.4/Documentation/devicetree/bindings/serial/ |
| D | nvidia,tegra20-hsuart.txt | 41 corruption/invalid framing errors. Parker errata suggests adjusting baud
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | sysfs-devices-platform-stratix10-rsu | 36 0xF003 bitstream corruption
|
| /Linux-v5.4/Documentation/hwmon/ |
| D | max16065.rst | 89 power loss, board resets, and/or Flash corruption. Worst case, your board may
|
| /Linux-v5.4/Documentation/x86/x86_64/ |
| D | machinecheck.rst | 58 with the risk of a crash or even corruption (for tolerant >= 3).
|
| /Linux-v5.4/arch/arm/kernel/ |
| D | asm-offsets.c | 44 #error and result in filesystem corruption and oopses.
|
| /Linux-v5.4/drivers/staging/vc04_services/interface/vchi/ |
| D | TODO | 30 leads to data corruption during the following command:
|
| /Linux-v5.4/Documentation/arm/samsung-s3c24xx/ |
| D | suspend.rst | 118 suspend to see if there has been any corruption of the contents.
|
12345
