Home
last modified time | relevance | path

Searched refs:failures (Results 1 – 25 of 88) sorted by relevance

1234

/Linux-v5.4/lib/
Dtest_meminit.c20 if (failures) \
22 __func__, failures, num_tests); \
86 int failures = 0, num_tests = 0; in test_pages() local
90 num_tests += do_alloc_pages_order(i, &failures); in test_pages()
93 *total_failures += failures; in test_pages()
134 int failures = 0, num_tests = 0; in test_kvmalloc() local
139 num_tests += do_kmalloc_size(size, &failures); in test_kvmalloc()
140 num_tests += do_vmalloc_size(size, &failures); in test_kvmalloc()
144 *total_failures += failures; in test_kvmalloc()
332 int failures = 0, num_tests = 0; in test_kmemcache() local
[all …]
Dtest_stackinit.c334 unsigned int failures = 0; in test_stackinit_init() local
337 failures += test_u8_ ## init (); \ in test_stackinit_init()
338 failures += test_u16_ ## init (); \ in test_stackinit_init()
339 failures += test_u32_ ## init (); \ in test_stackinit_init()
340 failures += test_u64_ ## init (); \ in test_stackinit_init()
341 failures += test_char_array_ ## init (); \ in test_stackinit_init()
345 failures += test_small_hole_ ## init (); \ in test_stackinit_init()
346 failures += test_big_hole_ ## init (); \ in test_stackinit_init()
347 failures += test_trailing_hole_ ## init (); \ in test_stackinit_init()
348 failures += test_packed_ ## init (); \ in test_stackinit_init()
[all …]
/Linux-v5.4/drivers/ide/
Dide-disk_proc.c108 ide_devset_rw_field(failures, failures);
118 IDE_PROC_DEVSET(failures, 0, 65535),
Dide-eh.c250 drive->failures++; in reset_pollfunc()
257 drive->failures = 0; in reset_pollfunc()
260 drive->failures++; in reset_pollfunc()
/Linux-v5.4/Documentation/fault-injection/
Dfault-injection.rst13 injects slab allocation failures. (kmalloc(), kmem_cache_alloc(), ...)
17 injects page allocation failures. (alloc_pages(), get_free_pages(), ...)
69 specifies the interval between failures, for calls to
77 specifies how many times failures may happen at most.
100 Any positive value limits failures to only processes indicated by
125 default is 'N', setting it to 'Y' won't inject failures into
133 default is 'N', setting it to 'Y' will inject failures
139 failures.
236 - add a hook to insert failures
245 - Inject slab allocation failures into module init/exit code::
[all …]
Dprovoke-crashes.rst39 You can also induce failures by mounting debugfs and writing the type to
Dnotifier-error-inject.rst6 notifier call chain failures which is rarely executed. There are kernel
/Linux-v5.4/drivers/md/
Ddm-raid1.c62 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-v5.4/tools/testing/fault-injection/
Dfailcmd.sh31 specifies how many times failures may happen at most.
59 inject slab allocation failures
61 inject page allocation failures
/Linux-v5.4/tools/testing/selftests/networking/timestamping/
Drxtimestamp.c330 int failures = 0; in main() local
381 failures++; in main()
387 if (!failures) in main()
389 return failures; in main()
/Linux-v5.4/Documentation/vm/
Dhwpoison.rst31 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-v5.4/drivers/net/ethernet/i825xx/
Dether1.c447 int failures = 0; in ether1_init_for_open() local
537 failures += 1; in ether1_init_for_open()
554 failures += 1; in ether1_init_for_open()
571 failures += 1; in ether1_init_for_open()
604 if (failures) in ether1_init_for_open()
606 return failures ? 1 : 0; in ether1_init_for_open()
/Linux-v5.4/tools/testing/selftests/x86/
Dldt_gdt.c534 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()
/Linux-v5.4/tools/testing/ktest/examples/include/
Ddefaults.conf151 STORE_FAILURES = ${THIS_DIR}/failures
/Linux-v5.4/scripts/coccinelle/api/
Dplatform_get_irq.cocci2 /// Remove dev_err() messages after platform_get_irq*() failures
/Linux-v5.4/drivers/usb/image/
DKconfig26 Please report failures and successes.
/Linux-v5.4/Documentation/admin-guide/device-mapper/
Ddm-queue-length.rst23 <fail-count>: The number of path failures.
Ddm-dust.txt5 locations, and the ability to enable the emulation of the failures
94 Enabling block read failures:
100 kernel: device-mapper: dust: enabling read failures on bad sectors
Ddm-service-time.rst38 The number of path failures.
/Linux-v5.4/Documentation/
DDMA-attributes.txt139 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-v5.4/fs/xfs/
DKconfig139 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-v5.4/Documentation/power/
Dbasic-pm-debugging.rst191 That test can be used to check if failures to resume from hibernation are
194 unreliable, the platform firmware may be responsible for the failures.
199 kernel address space randomization, it also can be used to check if failures
258 failures:
/Linux-v5.4/drivers/staging/qlge/
DTODO2 queues become empty because of allocation failures (ex. under memory
/Linux-v5.4/Documentation/filesystems/
Dceph.txt13 * Fast recovery from node failures
35 and can tolerate arbitrary (well, non-Byzantine) node failures. The
/Linux-v5.4/drivers/scsi/aic7xxx/
DKconfig.aic79xx30 failures when many devices are attached to the system. For this reason,

1234