| /linux-4.1.27/arch/x86/kernel/ |
| D | check.c | 121 int corruption = 0; in check_for_bios_corruption() local
135 corruption = 1; in check_for_bios_corruption()
140 WARN_ONCE(corruption, KERN_ERR "Memory corruption detected in low memory\n"); in check_for_bios_corruption()
|
| /linux-4.1.27/mm/ |
| D | Kconfig.debug | 20 of memory corruption.
26 that would result in incorrect warnings of memory corruption after
|
| /linux-4.1.27/Documentation/vm/ |
| D | slub.txt | 194 INFO: <corruption start>-<corruption_end> <more info>
211 Can be useful if the corruption does not stop with the start of the
217 corruption by a write after free.
237 of the corruption is may be more likely found by looking at the function that
270 may be optimized further by locating the slab that experiences corruption
277 If the corruption occurs by writing after the end of the object then it
|
| D | hwpoison.txt | 16 * When the current CPU tries to consume corruption the currently
19 * just ignore it because no corruption has been consumed yet. Instead
|
| D | pagemap.txt | 96 hardware detected memory corruption on this page: don't touch the data!
|
| /linux-4.1.27/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
|
| D | ceph.txt | 119 must rely on TCP's error correction to detect data corruption
|
| D | ubifs.txt | 88 of this option is that corruption of the contents
|
| D | btrfs.txt | 155 filesystem corruption on a system crash or power loss.
|
| D | ext4.txt | 85 * extent format more robust in face of on-disk corruption due to magics,
139 kernel to detect corruption in the kernel. It is a
|
| D | vfat.txt | 169 potentially causing data corruption. For this reason, this
|
| D | porting | 226 anything from oops to silent memory corruption.
|
| D | ext2.txt | 346 Tweedie. It avoids the risks of metadata corruption and the need to
|
| /linux-4.1.27/drivers/memstick/core/ |
| D | Kconfig | 14 in most cases result in data corruption.
|
| /linux-4.1.27/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-4.1.27/Documentation/ |
| D | io_ordering.txt | 47 possible data corruption.
|
| D | stable_kernel_rules.txt | 12 marked CONFIG_BROKEN), an oops, a hang, data corruption, a real
|
| D | md.txt | 58 undetectable data corruption. This is because the fact that it is
65 despite possible corruption. This is normally done with
|
| D | kernel-parameters.txt | 394 (may crash computer or cause data corruption)
827 of catching random memory corruption, but reduce the
831 memory corruption problems caused by bugs in kernel or
2012 looking for corruption. Enabling this will
2013 both detect corruption and prevent the kernel
2016 repeatable BIOS-originated corruption always
2021 By default it checks for corruption in the low
2024 corruption in more or less memory.
2027 By default it checks for corruption every 60
2250 doing this risks data corruption, since there are
|
| D | DMA-API-HOWTO.txt | 135 sharing problems (data corruption) on CPUs with DMA-incoherent caches.
559 from panics to silent data corruption. A couple of examples of incorrect ways
|
| D | bcache.txt | 106 filesystem corruption, though ext4's fsck does work miracles.
|
| D | edac.txt | 464 corruption. If the kernel has MCE configured, then EDAC will never
|
| D | applying-patches.txt | 417 tree is to weed out regressions, crashes, data corruption bugs, build
|
| D | DMA-API.txt | 583 result in data corruption up to destroyed filesystems.
|
| /linux-4.1.27/fs/ubifs/ |
| D | recovery.c | 699 int corruption = first_non_ff(buf, len); in ubifs_recover_leb() local
706 lnum, offs, corruption); in ubifs_recover_leb()
708 offs += corruption; in ubifs_recover_leb()
709 buf += corruption; in ubifs_recover_leb()
|
| /linux-4.1.27/drivers/block/drbd/ |
| D | Kconfig | 63 512 insert data corruption on receiving side
|
| /linux-4.1.27/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.
|
| D | lm93 | 122 achieved despite the signal corruption. In smart tach mode all
|
| /linux-4.1.27/Documentation/x86/x86_64/ |
| D | machinecheck | 56 with the risk of a crash or even corruption (for tolerant >= 3).
|
| /linux-4.1.27/Documentation/arm/Samsung-S3C24XX/ |
| D | Suspend.txt | 117 suspend to see if there has been any corruption of the contents.
|
| /linux-4.1.27/arch/arm/kernel/ |
| D | asm-offsets.c | 55 #error and result in filesystem corruption and oopses.
|
| /linux-4.1.27/Documentation/cdrom/ |
| D | packet-writing.txt | 82 filesystem corruption if the disc wears out.
|
| D | ide-cd | 331 f. Data corruption.
333 - Random data corruption was occasionally observed with the Hitachi
334 CDR-7730 CDROM. If you experience data corruption, using "hdx=slow"
|
| D | cdrom-standard.tex | 730 system corruption. If the drive is opened for audio ($O_NONBLOCK$ is
|
| /linux-4.1.27/Documentation/i2c/busses/ |
| D | i2c-piix4 | 60 crashes, data corruption, etc.). Try this only as a last resort (try BIOS
|
| /linux-4.1.27/Documentation/networking/ |
| D | skfp.txt | 218 - data corruption with kernel versions below 2.0.33.
|
| D | e1000e.txt | 236 GbE region in the ICHx NVM (in order to prevent accidental corruption of the
|
| D | cxgb.txt | 275 is operating at 133 Mhz", causing data corruption.
|
| D | cs89x0.txt | 313 corruption you should use your PC's BIOS to slow the EISA bus clock.
|
| D | ip-sysctl.txt | 150 from different IP datagrams, which could result in data corruption.
|
| /linux-4.1.27/Documentation/PCI/ |
| D | pci-error-recovery.txt | 19 corruption; for example, to halt system memory corruption due to DMA's
289 may result in hung devices, kernel panics, or silent data corruption.
|
| D | pci.txt | 462 corruption, hangs, and on some chip-sets a hard crash.
|
| /linux-4.1.27/arch/arm64/ |
| D | Kconfig | 323 on the AMBA 5 CHI interface, which can cause data corruption if the
357 bool "Cortex-A53: 819472: Store exclusive instructions might cause data corruption"
367 cause data corruption.
|
| /linux-4.1.27/drivers/scsi/arm/ |
| D | fas216.c | 229 int corruption = 0; in __fas216_checkmagic() local
232 corruption++; in __fas216_checkmagic()
236 corruption++; in __fas216_checkmagic()
238 if (corruption) { in __fas216_checkmagic()
|
| /linux-4.1.27/Documentation/powerpc/ |
| D | eeh-pci-error-recovery.txt | 24 can lead to data corruption, both of user data or of kernel data,
47 corruption caused by the bad DMA. A number of device driver
|
| /linux-4.1.27/arch/arm/plat-samsung/ |
| D | Kconfig | 294 corruption over suspend and resume. A smaller value will mean that
|
| /linux-4.1.27/drivers/net/ethernet/8390/ |
| D | Kconfig | 173 such as some BusLogic models) causes corruption problems with many
|
| /linux-4.1.27/Documentation/input/ |
| D | iforce-protocol.txt | 26 data corruption is handled or unsignificant.
|
| /linux-4.1.27/Documentation/scsi/ |
| D | aic79xx.txt | 77 SCB corruption on some PCI-33 busses.
164 - Correct data corruption issue that occurred under
|
| D | ncr53c8xx.txt | 68 14.4 Possible data corruption during a Memory Write and Invalidate
1199 14.4 Possible data corruption during a Memory Write and Invalidate
1211 the transfer, leaving to data corruption the remainder of this cache line.
|
| D | ChangeLog.megaraid | 396 i. Fix data corruption. Because of a typo in the driver, the IO packets
|
| D | ChangeLog.lpfc | 1649 * Fixed a memory corruption bug. This was caused by a memory
|
| /linux-4.1.27/arch/arm/ |
| D | Kconfig | 1094 bool "ARM errata: Incorrect hazard handling in the SCU may lead to data corruption"
1117 it behave as intended and avoiding data corruption.
1132 bool "ARM errata: Faulty hazard checking in the Store Buffer may lead to data corruption"
1139 corruption. This workaround sets a specific bit in the diagnostic
1179 bool "ARM errata: Possible cache data corruption with hit-under-miss enabled"
1183 r0p2 erratum (possible cache data corruption with
|
| /linux-4.1.27/fs/affs/ |
| D | Changes | 34 - fix for a possible bitmap corruption
|
| /linux-4.1.27/arch/arm/mach-shmobile/include/mach/ |
| D | head-kzm9g.txt | 397 LIST "Magic to avoid hangs and corruption on DRAM writes."
|
| /linux-4.1.27/Documentation/usb/ |
| D | persist.txt | 155 data corruption and to crash your system. You'll have no one to blame
|
| /linux-4.1.27/lib/ |
| D | Kconfig.debug | 659 corruption, especially if it appears in 'struct thread_info'
816 corruption or other issues.
857 bool "Detect stack corruption on calls to schedule()"
865 data corruption or a sporadic crash at a later stage once the region
1692 accessed by the cpu in a way that could cause data corruption. For
|
| /linux-4.1.27/Documentation/ide/ |
| D | ide.txt | 19 *** to prevent data corruption possible due to hardware design flaws.
|
| D | ChangeLog.ide-tape.1995-2002 | 153 * corruption, which could occur if the total number
|
| /linux-4.1.27/Documentation/filesystems/cifs/ |
| D | CHANGES | 158 bigendian architectures. Fix possible memory corruption when
218 Fix file corruption which could occur on some large file
862 Fix data corruption (in partial page after truncate) that caused fsx to
1011 Fixed major problem with dentry corruption (missing call to dput)
|
| /linux-4.1.27/arch/x86/ |
| D | Kconfig | 952 kernel if it detects a problem (e.g. overheating, data corruption).
1445 bool "Check for low memory corruption"
1447 Periodically check for memory corruption in low memory, which
1458 of memory and scans it infrequently. It both detects corruption
1462 BIOS-originated corruption always affects the same memory,
1499 typical corruption patterns.
|
| /linux-4.1.27/Documentation/RCU/ |
| D | rcu_dereference.txt | 13 will complain. Worse yet, your code can see random memory-corruption
|
| D | checklist.txt | 106 the following measures to prevent memory-corruption problems:
|
| D | RTFP.txt | 78 memory corruption can ensue, with no reasonable means of diagnosis.
422 but subject to random memory corruption under heavy load.
|
| /linux-4.1.27/drivers/ide/ |
| D | Kconfig | 235 design flaws that can cause severe data corruption under many common
339 severe data corruption under many conditions. Say Y here to include
|
| /linux-4.1.27/Documentation/device-mapper/ |
| D | thin-provisioning.txt | 178 must suspend it before creating the snapshot to avoid corruption.
|
| /linux-4.1.27/drivers/atm/ |
| D | Kconfig | 73 in the PCI chipset and cause data corruption. In such cases, large
|
| /linux-4.1.27/Documentation/video4linux/cx2341x/ |
| D | fw-decoder-regs.txt | 306 NOTE: Video corruption will occur if video window is shifted off the right
|
| /linux-4.1.27/arch/arm/mm/ |
| D | Kconfig | 922 bool "PL310 errata: Background Clean & Invalidate by Way operation can cause data corruption"
|
| /linux-4.1.27/Documentation/virtual/uml/ |
| D | UserModeLinux-HOWTO.txt | 1850 from a shared disk. It will result in filesystem corruption.
3170 apparent reason, and the cause looked like stack corruption. In hopes
3680 is not a case of data corruption. It happened on purpose somehow.
3785 the stack corruption problem disappeared.
|
| /linux-4.1.27/Documentation/laptops/ |
| D | thinkpad-acpi.txt | 640 and, on the X40, video corruption. By disabling automatic switching,
641 the flickering or video corruption can be avoided.
|
| /linux-4.1.27/Documentation/sysctl/ |
| D | vm.txt | 397 as soon as the corruption is detected. Note this is not supported
|
| /linux-4.1.27/Documentation/trace/ |
| D | ftrace.txt | 2792 can be in danger of a stack overflow, and corruption will occur,
|