| /openbmc/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
|
| /openbmc/linux/Documentation/driver-api/ |
| H A D | io_ordering.rst | 51 possible data corruption.
|
| /openbmc/linux/tools/perf/Documentation/ |
| H A D | Build.txt | 57 AddressSanitizer (or ASan) is a GCC feature that detects memory corruption bugs
|
| /openbmc/u-boot/fs/ubifs/ |
| H A D | recovery.c | 695 int corruption = first_non_ff(buf, len); in ubifs_recover_leb() local
702 lnum, offs, corruption); in ubifs_recover_leb()
704 offs += corruption; in ubifs_recover_leb()
705 buf += corruption; in ubifs_recover_leb()
|
| /openbmc/linux/fs/ubifs/ |
| H A 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()
|
| /openbmc/openbmc/poky/meta/recipes-core/busybox/busybox/ |
| H A D | busybox-cross-menuconfig.patch | 18 differently than the host's version. This causes display corruption
|
| /openbmc/linux/drivers/soc/samsung/ |
| H A D | Kconfig | 74 corruption over suspend and resume. A smaller value will mean that
|
| /openbmc/linux/drivers/block/drbd/ |
| H A D | Kconfig | 63 512 insert data corruption on receiving side
|
| /openbmc/linux/Documentation/mm/ |
| 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
|
| /openbmc/qemu/tests/qemu-iotests/ |
| H A D | 137.out | 42 …orrupt: Preventing invalid allocation of L2 table at offset 0; further corruption events will be s…
|
| H A D | 271.out | 458 …alid cluster entry found (L2 offset: 0x40000, L2 index: 0x1); further corruption events will be s…
473 …nvalid cluster entry found (L2 offset: 0x40000, L2 index: 0); further corruption events will be s…
480 …alid cluster entry found (L2 offset: 0x40000, L2 index: 0x1); further corruption events will be s…
503 …valid cluster entry found (L2 offset: 0x40000, L2 index: 0x1); further corruption events will be s…
518 …Invalid cluster entry found (L2 offset: 0x40000, L2 index: 0); further corruption events will be s…
525 …valid cluster entry found (L2 offset: 0x40000, L2 index: 0x1); further corruption events will be s…
557 …on offset 0x50200 unaligned (L2 offset: 0x40000, L2 index: 0); further corruption events will be s…
|
| /openbmc/linux/Documentation/hwmon/ |
| H A D | max16065.rst | 89 power loss, board resets, and/or Flash corruption. Worst case, your board may
|
| /openbmc/linux/Documentation/devicetree/bindings/serial/ |
| H A D | nvidia,tegra20-hsuart.yaml | 73 received data will have corruption/invalid framing errors. Parker errata suggests adjusting
|
| /openbmc/linux/Documentation/arch/arm64/ |
| H A D | kdump.rst | 10 kernel if corruption happens.
|
| /openbmc/linux/Documentation/admin-guide/device-mapper/ |
| H A 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
135 will protect the data against accidental corruption.
|
| H A D | dm-raid.rst | 397 target version, thus avoiding data corruption on a raid set
407 1.10.1 Fix data corruption on reshape request
417 deadlock/potential data corruption. Update superblock when
|
| H A D | writecache.rst | 59 promoted, to avoid data corruption due to misordered
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-devices-platform-stratix10-rsu | 36 0xF003 bitstream corruption
|
| /openbmc/linux/Documentation/cdrom/ |
| H A D | packet-writing.rst | 89 filesystem corruption if the disc wears out.
|
| /openbmc/docs/designs/ |
| H A D | bios-bmc-smm-error-logging.md | 53 against corruption, but it should not be relied upon.
70 … BIOS before logging. BMC can change this number when it suspects data corruption to prevent BIOS …
|
| /openbmc/linux/arch/arm/ |
| H A D | Kconfig | 698 bool "ARM errata: Incorrect hazard handling in the SCU may lead to data corruption"
724 it behave as intended and avoiding data corruption.
739 bool "ARM errata: Faulty hazard checking in the Store Buffer may lead to data corruption"
746 corruption. This workaround sets a specific bit in the diagnostic
792 bool "ARM errata: Possible cache data corruption with hit-under-miss enabled"
796 r0p2 erratum (possible cache data corruption with
858 bool "ARM errata: A12: some seqs of opposed cond code instrs => deadlock or corruption"
865 lead to either a data corruption or a CPU deadlock. Not fixed in
908 bool "ARM errata: A17: some seqs of opposed cond code instrs => deadlock or corruption"
913 lead to either a data corruption or a CPU deadlock. Not fixed in
|
| /openbmc/qemu/docs/devel/ |
| H A D | secure-coding-practices.rst | 84 request completes. Unexpected accesses must not cause memory corruption or
|
| /openbmc/u-boot/lib/lzma/ |
| H A D | history.txt | 244 - Some detection of data corruption was enabled.
|
| /openbmc/linux/Documentation/i2c/busses/ |
| H A D | i2c-piix4.rst | 64 crashes, data corruption, etc.). Try this only as a last resort (try BIOS
|
| /openbmc/qemu/docs/ |
| H A D | nvdimm.txt | 76 order to avoid the data corruption.
107 may result guest data corruption (e.g. breakage of guest file
|