| /linux/lib/ |
| A D | test_meminit.c | 20 if (failures) \
22 __func__, failures, num_tests); \
86 int failures = 0, num_tests = 0; in test_pages() local
93 *total_failures += failures; in test_pages()
134 int failures = 0, num_tests = 0; in test_kvmalloc() local
144 *total_failures += failures; in test_kvmalloc()
363 &failures); in test_kmemcache()
368 *total_failures += failures; in test_kmemcache()
383 *total_failures += failures; in test_rcu_persistent()
400 if (failures == 0) in test_meminit_init()
[all …]
|
| A D | test_stackinit.c | 455 unsigned int failures = 0; in test_stackinit_init() local
458 failures += test_u8_ ## init (); \ in test_stackinit_init()
459 failures += test_u16_ ## init (); \ in test_stackinit_init()
460 failures += test_u32_ ## init (); \ in test_stackinit_init()
461 failures += test_u64_ ## init (); \ in test_stackinit_init()
492 failures += test_switch_1_none(); in test_stackinit_init()
493 failures += test_switch_2_none(); in test_stackinit_init()
499 failures += test_user(); in test_stackinit_init()
501 if (failures == 0) in test_stackinit_init()
504 pr_err("failures: %u\n", failures); in test_stackinit_init()
[all …]
|
| /linux/tools/testing/selftests/vm/ |
| A D | mremap_test.c | 188 static void run_mremap_test_case(struct test test_case, int *failures, in run_mremap_test_case() argument
201 *failures += 1; in run_mremap_test_case()
261 int failures = 0; in main() local
339 run_mremap_test_case(test_cases[i], &failures, threshold_mb, in main()
346 run_mremap_test_case(perf_test_cases[i], &failures, in main()
350 if (failures > 0) in main()
|
| /linux/Documentation/fault-injection/ |
| A D | fault-injection.rst | 13 injects slab allocation failures. (kmalloc(), kmem_cache_alloc(), ...)
29 injects kernel RPC client and server failures.
77 specifies the interval between failures, for calls to
85 specifies how many times failures may happen at most. A value of -1
110 Any positive value limits failures to only processes indicated by
135 default is 'N', setting it to 'Y' won't inject failures into
143 default is 'N', setting it to 'Y' will inject failures
149 failures.
263 - add a hook to insert failures
272 - Inject slab allocation failures into module init/exit code::
[all …]
|
| A D | provoke-crashes.rst | 46 You can also induce failures by mounting debugfs and writing the type to
|
| A D | notifier-error-inject.rst | 6 notifier call chain failures which is rarely executed. There are kernel
|
| /linux/drivers/md/ |
| A 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()
791 if (likely(!failures->head)) in do_failures()
811 while ((bio = bio_list_pop(failures))) { in do_failures()
860 failures = ms->failures; in do_mirror()
863 bio_list_init(&ms->failures); in do_mirror()
870 do_failures(ms, &failures); in do_mirror()
[all …]
|
| /linux/tools/testing/selftests/net/ |
| A D | rxtimestamp.c | 361 int failures = 0; in main() local
420 failures++; in main()
424 failures++; in main()
427 if (!failures) in main()
429 return failures; in main()
|
| /linux/tools/testing/fault-injection/ |
| A D | failcmd.sh | 31 specifies how many times failures may happen at most.
59 inject slab allocation failures
61 inject page allocation failures
|
| /linux/Documentation/vm/ |
| A 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/tools/testing/selftests/rcutorture/bin/ |
| A D | kvm-check-branches.sh | 102 echo '!!! ' $nfail failures in $ntry 'runs!!!'
105 echo No failures in $ntry runs.
|
| A D | torture.sh | 245 touch $T/failures
279 echo "$curflavor($retcode)" $resdir >> $T/failures
334 echo "allmodconfig($retcode)" $amcdir >> $T/failures
418 nfailures="`wc -l "$T/failures" | awk '{ print $1 }'`"
|
| /linux/arch/x86/kernel/cpu/sgx/ |
| A D | virt.c | 157 long failures = 0; in sgx_vepc_remove_all() local
164 failures++; in sgx_vepc_remove_all()
185 return failures; in sgx_vepc_remove_all()
|
| /linux/tools/testing/selftests/bpf/ |
| A D | README.rst | 41 Additional information about selftest failures are
44 profiler[23] test failures with clang/llvm <12.0.0
83 bpf_iter test failures with clang/llvm 10.0.0
169 old to support them, they shouldn't cause build failures or runtime test
170 failures:
|
| /linux/drivers/net/ethernet/i825xx/ |
| A D | ether1.c | 447 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/tools/testing/selftests/x86/ |
| A 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()
|
| /linux/Documentation/core-api/ |
| A D | dma-attributes.rst | 113 On some architectures allocation failures are reported with error messages
115 drivers which handle failures (eg, retry later) have no problems with them,
120 where allocation failures are not a problem, and shouldn't bother the logs.
|
| /linux/tools/testing/ktest/examples/include/ |
| A D | defaults.conf | 151 STORE_FAILURES = ${THIS_DIR}/failures
|
| /linux/scripts/coccinelle/api/ |
| A D | platform_get_irq.cocci | 2 /// Remove dev_err() messages after platform_get_irq*() failures
|
| /linux/tools/testing/selftests/drivers/net/mlxsw/ |
| A D | qos_lib.sh | 68 the other. That will cause spurious failures (or,
|
| /linux/drivers/usb/image/ |
| A D | Kconfig | 26 Please report failures and successes.
|
| /linux/Documentation/admin-guide/device-mapper/ |
| A D | dm-queue-length.rst | 23 <fail-count>: The number of path failures.
|
| A D | dm-dust.rst | 5 locations, and the ability to enable the emulation of the failures
108 Enabling block read failures
114 kernel: device-mapper: dust: enabling read failures on bad sectors
|
| /linux/Documentation/power/ |
| A D | basic-pm-debugging.rst | 191 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/fs/xfs/ |
| A D | Kconfig | 164 Say Y here to cause DEBUG mode ASSERT failures to result in fatal
165 errors that BUG() the kernel by default. If you say N, ASSERT failures
|