| /linux-4.1.27/Documentation/fault-injection/ |
| D | fault-injection.txt | 12 injects slab allocation failures. (kmalloc(), kmem_cache_alloc(), ...)
16 injects page allocation failures. (alloc_pages(), get_free_pages(), ...)
48 specifies the interval between failures, for calls to
56 specifies how many times failures may happen at most.
77 Any positive value limits failures to only processes indicated by
101 default is 'N', setting it to 'Y' won't inject failures into
108 default is 'N', setting it to 'Y' will inject failures
114 failures.
160 o add a hook to insert failures
169 o Inject slab allocation failures into module init/exit code
[all …]
|
| D | provoke-crashes.txt | 29 You can also induce failures by mounting debugfs and writing the type to
|
| D | notifier-error-inject.txt | 6 notifier call chain failures which is rarely executed. There are kernel
|
| /linux-4.1.27/drivers/md/ |
| D | dm-raid1.c | 58 struct bio_list failures; member
626 if (!ms->failures.head) in write_callback()
628 bio_list_add(&ms->failures, bio); in write_callback()
751 bio_list_merge(&ms->failures, &sync); in do_writes()
764 bio_list_add(&ms->failures, bio); in do_writes()
774 static void do_failures(struct mirror_set *ms, struct bio_list *failures) in do_failures() argument
778 if (likely(!failures->head)) in do_failures()
798 while ((bio = bio_list_pop(failures))) { in do_failures()
836 struct bio_list reads, writes, failures; in do_mirror() local
842 failures = ms->failures; in do_mirror()
[all …]
|
| D | Kconfig | 22 disk failures. This is called "Software RAID" since the combining of
|
| /linux-4.1.27/tools/testing/fault-injection/ |
| D | failcmd.sh | 30 specifies how many times failures may happen at most.
58 inject slab allocation failures
60 inject page allocation failures
|
| /linux-4.1.27/drivers/ide/ |
| D | ide-disk_proc.c | 159 ide_devset_rw_field(failures, failures);
169 IDE_PROC_DEVSET(failures, 0, 65535),
|
| D | ide-eh.c | 249 drive->failures++; in reset_pollfunc()
256 drive->failures = 0; in reset_pollfunc()
259 drive->failures++; in reset_pollfunc()
|
| D | ide-iops.c | 171 if (drive->max_failures && (drive->failures > drive->max_failures)) { in ide_wait_stat()
|
| D | ide-io.c | 318 if (drive->max_failures && (drive->failures > drive->max_failures)) { in start_request()
|
| /linux-4.1.27/Documentation/vm/ |
| D | hwpoison.txt | 24 * users, because memory failures could happen anytime and anywhere,
46 memory failures too. The expection is that near all applications
54 All memory failures cause a panic. Do not attempt recovery.
118 This only works for Linux injected failures, not for real
119 memory failures.
127 Only handle memory failures to pages associated with the file system defined
|
| D | transhuge.txt | 68 allocation failures to be noticeable from userland. It allows paging
|
| /linux-4.1.27/arch/blackfin/mach-common/ |
| D | arch_checks.c | 55 … part with anomaly 05000448, this issue causes random memory read/write failures - that means rand…
|
| /linux-4.1.27/drivers/net/ethernet/i825xx/ |
| D | ether1.c | 449 int failures = 0; in ether1_init_for_open() local
539 failures += 1; in ether1_init_for_open()
556 failures += 1; in ether1_init_for_open()
573 failures += 1; in ether1_init_for_open()
606 if (failures) in ether1_init_for_open()
608 return failures ? 1 : 0; in ether1_init_for_open()
|
| /linux-4.1.27/tools/testing/ktest/examples/include/ |
| D | defaults.conf | 151 STORE_FAILURES = ${THIS_DIR}/failures
|
| /linux-4.1.27/drivers/usb/image/ |
| D | Kconfig | 25 Please report failures and successes.
|
| /linux-4.1.27/Documentation/device-mapper/ |
| D | dm-queue-length.txt | 16 <fail-count>: The number of path failures.
|
| D | dm-service-time.txt | 30 <fail-count>: The number of path failures.
|
| D | log-writes.txt | 25 simulate the worst case scenario with regard to power failures. Consider the
|
| D | thin-provisioning.txt | 300 If the pool encounters certain types of device failures it will
|
| /linux-4.1.27/drivers/staging/media/lirc/ |
| D | lirc_zilog.c | 318 int failures = 0; in add_to_buf() local
373 if (failures >= 3) { in add_to_buf()
394 ++failures; in add_to_buf()
1106 int failures = 0; in write() local
1179 if (failures >= 3) { in write()
1190 ++failures; in write()
|
| /linux-4.1.27/Documentation/filesystems/ |
| D | ceph.txt | 13 * Fast recovery from node failures
37 and can tolerate arbitrary (well, non-Byzantine) node failures. The
|
| D | logfs.txt | 143 result in GC failures when, after moving some data, indirect blocks
|
| D | coda.txt | 1599 FS Driver at startup and upon shutdown or Venus failures. Before
|
| /linux-4.1.27/Documentation/blockdev/ |
| D | cciss.txt | 33 Detecting drive failures:
37 failures, you can use the cciss_vol_status program found here:
|
| D | paride.txt | 343 transfers, or unexpected failures, you may wish to increase the
|
| D | README.DAC960 | 338 operating normally and no failures have occurred, or "ALERT" if any logical
|
| /linux-4.1.27/Documentation/ABI/testing/ |
| D | sysfs-class-mtd | 193 The number of failures reported by this device's ECC. Typically,
194 these failures are associated with failed read operations.
|
| /linux-4.1.27/drivers/scsi/aic7xxx/ |
| D | Kconfig.aic79xx | 29 failures when many devices are attached to the system. For this reason,
|
| D | Kconfig.aic7xxx | 34 failures when many devices are attached to the system. For this reason,
|
| /linux-4.1.27/Documentation/dmaengine/ |
| D | dmatest.txt | 89 dmatest: dma0chan0-copy0: summary 1 test, 0 failures 1000 iops 100000 KB/s (0)
|
| /linux-4.1.27/Documentation/power/ |
| D | freezing-of-tasks.txt | 202 VI. Are there any precautions to be taken to prevent freezing failures?
214 that could lead to freezing failures, because if the suspend/hibernate code
225 mutex_[un]lock(&pm_mutex). That would prevent freezing failures.
|
| D | basic-pm-debugging.txt | 219 failures:
|
| /linux-4.1.27/Documentation/ |
| D | SubmitChecklist | 82 failures. See Documentation/fault-injection/.
|
| D | flexible-arrays.txt | 22 allocation failures should be relatively rare. The down sides are that the
|
| D | md-cluster.txt | 151 Device failures are handled and communicated with the metadata update
|
| D | sysfs-rules.txt | 169 In general, failures to read or write sysfs device attributes shall
|
| D | intel_txt.txt | 122 - Policy action is flexible and can include halting on failures
|
| D | cpu-hotplug.txt | 240 last CPU, this will not be permitted. You can find such failures by
|
| D | DMA-API-HOWTO.txt | 558 returned address without checking for errors could result in failures ranging
|
| D | SubmittingPatches | 693 it may not be necessary to include _all_ of the compile failures; just
|
| /linux-4.1.27/drivers/mtd/ubi/ |
| D | wl.c | 1412 int failures = 0; local
1442 if (failures++ > WL_MAX_FAILURES) {
1454 failures = 0;
|
| /linux-4.1.27/Documentation/filesystems/pohmelfs/ |
| D | design_notes.txt | 39 to which they are sent and, in case of failures, are eventually resent or dropped with an error.
|
| /linux-4.1.27/Documentation/locking/ |
| D | locktorture.txt | 145 were no locking failures, CPU-hotplug problems were detected.
|
| /linux-4.1.27/Documentation/scsi/ |
| D | ChangeLog.sym53c8xx_2 | 97 - Check pci dma mapping failures and complete the IO with some
|
| D | scsi_eh.txt | 299 command failures (autosense). Autosense is recommended for
|
| D | ChangeLog.lpfc | 1114 * Added scsi_buf safety pool to address scsi_buf failures in
|
| /linux-4.1.27/Documentation/RCU/ |
| D | torture.txt | 119 values for stall_cpu might well induce failures and
334 were no RCU failures, CPU-hotplug problems were detected.
|
| /linux-4.1.27/drivers/parisc/ |
| D | Kconfig | 167 This includes NVRAM battery level, overtemp or failures such as
|
| /linux-4.1.27/Documentation/hid/ |
| D | hid-transport.txt | 66 Transport drivers are responsible of detecting device failures and unplugging.
68 device failures. Once transport drivers detect unplug or failure events, they
|
| /linux-4.1.27/Documentation/powerpc/ |
| D | transactional_memory.txt | 38 ... test for odd failures ...
|
| D | eeh-pci-error-recovery.txt | 53 The vast majority of "true hardware failures" can be cured by
|
| /linux-4.1.27/Documentation/cpu-freq/ |
| D | cpu-drivers.txt | 217 failures as core would send notifications for that.
|
| /linux-4.1.27/Documentation/networking/ |
| D | 3c509.txt | 92 failures will occur - at the very least, you'll see massive numbers of packet
|
| D | bonding.txt | 155 degradation will occur during link failures. Very few devices do not
485 inspected for link failures. A value of zero disables MII
1950 some fixed interval. In this case, miimon will detect failures, but
1952 miimon is very slow in detecting link failures, try specifying
2116 failures, then either the MII or ARP monitors should work. For
2124 end connectivity failures (which may be caused by the failure of any
2135 Its purpose is to propagate link failures from logically "exterior" ports
2579 only able to detect link failures between the ESM and the JS20 system.
2582 detect failures to the "external" port, which is then directly
2643 be unable to detect link failures, and will assume that all links are
|
| D | netdev-FAQ.txt | 208 "allmodconfig" build without new warnings or failures.
|
| D | ixgb.txt | 365 Memory allocation failures have been observed on Linux systems with 64 MB
|
| /linux-4.1.27/Documentation/sound/alsa/ |
| D | compress_offload.txt | 106 configuration failures. For example, for a complex codec such as AAC,
|
| /linux-4.1.27/Documentation/usb/ |
| D | ehci.txt | 134 Those hubs report some failures, such as disconnections, differently when
|
| /linux-4.1.27/include/linux/ |
| D | ide.h | 535 unsigned int failures; /* current failure count */ member
|
| /linux-4.1.27/Documentation/filesystems/caching/ |
| D | netfs-api.txt | 762 All possible failures are handled internally. The caller should consider
779 All possible failures are handled internally. The cookie will only be marked
|
| D | fscache.txt | 219 nal=N Number of object allocation failures
|
| /linux-4.1.27/Documentation/kdump/ |
| D | kdump.txt | 391 * The "irqpoll" boot parameter reduces driver initialization failures
|
| /linux-4.1.27/lib/ |
| D | Kconfig.debug | 1361 handling of notifier call chain failures.
1518 copy operations into compile time failures.
1538 inducing system failures at predefined crash points.
|
| /linux-4.1.27/Documentation/PCI/ |
| D | pci-error-recovery.txt | 368 Note, however, not all failures are truly "permanent". Some are
|
| /linux-4.1.27/mm/ |
| D | Kconfig | 372 Enables code to recover from some memory failures on systems
|
| /linux-4.1.27/Documentation/development-process/ |
| D | 4.Coding | 278 fail; these failures can be restricted to a specific range of code.
|
| /linux-4.1.27/Documentation/sysctl/ |
| D | vm.txt | 231 values towards 1000 imply failures are due to fragmentation and -1 implies
|
| /linux-4.1.27/Documentation/filesystems/cifs/ |
| D | CHANGES | 413 Do not flag user_xattr mount parm in dmesg. Retry failures setting file time
|
| /linux-4.1.27/Documentation/sound/oss/ |
| D | README.OSS | 1324 and kernel failures when sound is used.
|