| /openbmc/qemu/tests/qemu-iotests/ |
| H A D | 060.out | 129 …e as corrupt: L2 table offset 0x42a00 unaligned (L1 index: 0); further corruption events will be s…
134 …e as corrupt: L2 table offset 0x42a00 unaligned (L1 index: 0); further corruption events will be s…
156 …orrupt: Refblock offset 0x22a00 unaligned (reftable index: 0); further corruption events will be s…
159 === Testing non-fatal corruption on freeing ===
164 qcow2: Image is corrupt: Cannot free unaligned cluster 0x52a00; further non-fatal corruption events…
168 === Testing read-only corruption report ===
177 === Testing non-fatal and then fatal corruption report ===
182 qcow2: Image is corrupt: Cannot free unaligned cluster 0x52a00; further non-fatal corruption events…
231 …orrupt: Preventing invalid allocation of L2 table at offset 0; further corruption events will be s…
338 …corrupt: Refblock offset 0x2a00 unaligned (reftable index: 0); further corruption events will be s…
[all …]
|
| H A D | 305.out | 14 …rupt: Refblock offset 0x20600 unaligned (reftable index: 0x1); further corruption events will be s…
|
| /openbmc/linux/arch/arm64/kvm/hyp/nvhe/ |
| H A D | list_debug.c | 17 bool corruption = unlikely(condition); \
18 if (corruption) { \
24 corruption; \
|
| /openbmc/linux/include/linux/ |
| H A D | bug.h | 83 bool corruption = unlikely(condition); \
84 if (corruption) { \
91 corruption; \
|
| /openbmc/linux/arch/x86/kernel/ |
| H A 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()
|
| /openbmc/linux/Documentation/mm/ |
| H A D | page_table_check.rst | 17 In case of detected corruption, the kernel is crashed. There is a small
21 is synchronous, it can help with debugging double map memory corruption issues,
68 still being mapped in the userspace, leading to "corruption" detected by the
|
| H A 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
|
| /openbmc/linux/drivers/ras/ |
| H A D | Kconfig | 26 correctly, including avoiding data corruption, whereas Availability
30 data corruption.
|
| /openbmc/linux/tools/testing/selftests/lkdtm/ |
| H A D | tests.txt | 11 CORRUPT_LIST_ADD list_add corruption
12 CORRUPT_LIST_DEL list_del corruption
|
| /openbmc/linux/Documentation/ABI/obsolete/ |
| H A D | sysfs-firmware-acpi | 7 the offline failure might lead to memory corruption and crashes)
|
| /openbmc/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.
|
| /openbmc/linux/Documentation/devicetree/bindings/reserved-memory/ |
| H A 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
|
| /openbmc/linux/Documentation/filesystems/ |
| 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
|
| /openbmc/qemu/docs/devel/ |
| H A D | blkverify.txt | 14 Blkverify solves this problem by catching data corruption inside QEMU the first
68 If the installation is aborted when blkverify detects corruption, use qemu-io
|
| /openbmc/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
|
| /openbmc/linux/Documentation/gpu/amdgpu/display/ |
| H A D | dc-debug.rst | 41 * There should **not** be any visual corruption
44 * There should **not** be any cursor corruption
|
| /openbmc/openbmc-test-automation/extended/ |
| H A D | test_ac_cycles.robot | 3 Documentation Test file corruption on hard power cycle.
|
| /openbmc/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
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-extended/tgt/files/ |
| H A D | tgtd.service | 24 # NOTE: Shutdown of the iscsi target may cause data corruption
|
| /openbmc/linux/Documentation/ABI/removed/ |
| H A D | sysfs-mce | 23 better uptime with the risk of a crash or even corruption
|
| /openbmc/linux/drivers/memstick/core/ |
| H A D | Kconfig | 15 in most cases result in data corruption.
|
| /openbmc/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
107 entries are added and removed to user page tables, leaking, corruption
|
| /openbmc/openbmc/poky/meta/classes-global/ |
| H A D | packagedata.bbclass | 28 …ate package %s which was already written by recipe %s. This will cause corruption, please resolve …
|
| /openbmc/u-boot/doc/ |
| H A D | I2C_Edge_Conditions | 5 and the CPU was reset. This may result in EEPROM data corruption.
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/yajl/yajl/ |
| H A D | CVE-2022-24795.patch | 17 corruption.
|