| /Linux-v4.19/drivers/ide/ |
| D | ide-disk_proc.c | 108 ide_devset_rw_field(failures, failures);
118 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()
|
| /Linux-v4.19/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(), ...)
66 specifies the interval between failures, for calls to
74 specifies how many times failures may happen at most.
95 Any positive value limits failures to only processes indicated by
119 default is 'N', setting it to 'Y' won't inject failures into
126 default is 'N', setting it to 'Y' will inject failures
132 failures.
225 o add a hook to insert failures
234 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-v4.19/drivers/md/ |
| D | dm-raid1.c | 62 struct bio_list failures; member
638 if (!ms->failures.head) in write_callback()
640 bio_list_add(&ms->failures, bio); in write_callback()
764 bio_list_merge(&ms->failures, &sync); in do_writes()
777 bio_list_add(&ms->failures, bio); in do_writes()
787 static void do_failures(struct mirror_set *ms, struct bio_list *failures) in do_failures() argument
791 if (likely(!failures->head)) in do_failures()
811 while ((bio = bio_list_pop(failures))) { in do_failures()
854 struct bio_list reads, writes, failures; in do_mirror() local
860 failures = ms->failures; in do_mirror()
[all …]
|
| /Linux-v4.19/tools/testing/fault-injection/ |
| D | failcmd.sh | 31 specifies how many times failures may happen at most.
59 inject slab allocation failures
61 inject page allocation failures
|
| /Linux-v4.19/tools/testing/selftests/networking/timestamping/ |
| D | rxtimestamp.c | 329 int failures = 0; in main() local
380 failures++; in main()
386 if (!failures) in main()
388 return failures; in main()
|
| /Linux-v4.19/Documentation/vm/ |
| D | hwpoison.rst | 31 * users, because memory failures could happen anytime and anywhere,
53 memory failures too. The expection is that near all applications
62 All memory failures cause a panic. Do not attempt recovery.
125 injected failures, not for real memory failures.
131 Only handle memory failures to pages associated with the file
|
| /Linux-v4.19/drivers/net/ethernet/i825xx/ |
| D | ether1.c | 450 int failures = 0; in ether1_init_for_open() local
540 failures += 1; in ether1_init_for_open()
557 failures += 1; in ether1_init_for_open()
574 failures += 1; in ether1_init_for_open()
607 if (failures) in ether1_init_for_open()
609 return failures ? 1 : 0; in ether1_init_for_open()
|
| /Linux-v4.19/tools/testing/ktest/examples/include/ |
| D | defaults.conf | 151 STORE_FAILURES = ${THIS_DIR}/failures
|
| /Linux-v4.19/tools/testing/selftests/x86/ |
| D | ldt_gdt.c | 534 int failures = 0, iters = 5, i; in do_multicpu_tests() local
608 failures++; in do_multicpu_tests()
618 if (failures) { in do_multicpu_tests()
619 printf("[FAIL]\t%d of %d iterations failed\n", failures, iters); in do_multicpu_tests()
|
| D | mpx-mini-test.c | 1448 int failures = 0; in check_mpx_insns_and_tables() local
1482 failures++; in check_mpx_insns_and_tables()
1497 dprintf1(" failures: %d\n", failures); in check_mpx_insns_and_tables()
1501 if (failures) { in check_mpx_insns_and_tables()
1514 eprintf(" failures: %d\n", failures); in check_mpx_insns_and_tables()
|
| /Linux-v4.19/drivers/usb/image/ |
| D | Kconfig | 25 Please report failures and successes.
|
| /Linux-v4.19/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.
|
| /Linux-v4.19/Documentation/ |
| D | DMA-attributes.txt | 139 On some architectures allocation failures are reported with error messages
141 drivers which handle failures (eg, retry later) have no problems with them,
146 where allocation failures are not a problem, and shouldn't bother the logs.
|
| /Linux-v4.19/fs/xfs/ |
| D | Kconfig | 139 Say Y here to cause DEBUG mode ASSERT failures to result in fatal
140 errors that BUG() the kernel by default. If you say N, ASSERT failures
|
| /Linux-v4.19/Documentation/power/ |
| D | basic-pm-debugging.txt | 180 That test can be used to check if failures to resume from hibernation are
183 unreliable, the platform firmware may be responsible for the failures.
188 kernel address space randomization, it also can be used to check if failures
244 failures:
|
| D | freezing-of-tasks.txt | 203 VI. Are there any precautions to be taken to prevent freezing failures?
215 that could lead to freezing failures, because if the suspend/hibernate code
226 mutex_[un]lock(&system_transition_mutex). That would prevent freezing failures.
|
| /Linux-v4.19/Documentation/filesystems/ |
| D | ceph.txt | 13 * Fast recovery from node failures
37 and can tolerate arbitrary (well, non-Byzantine) node failures. The
|
| /Linux-v4.19/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-v4.19/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-v4.19/mm/ |
| D | Kconfig.debug | 87 due to migration failures caused by page reference mismatches. Be
|
