/linux-6.1.9/lib/ |
D | test_meminit.c | 20 if (failures) \ 22 __func__, failures, num_tests); \ 93 int failures = 0, num_tests = 0; in test_pages() local 97 num_tests += do_alloc_pages_order(i, &failures); in test_pages() 100 *total_failures += failures; in test_pages() 155 int failures = 0, num_tests = 0; in test_kvmalloc() local 160 num_tests += do_kmalloc_size(size, &failures); in test_kvmalloc() 161 num_tests += do_vmalloc_size(size, &failures); in test_kvmalloc() 165 *total_failures += failures; in test_kvmalloc() 380 int failures = 0, num_tests = 0; in test_kmemcache() local [all …]
|
/linux-6.1.9/tools/testing/selftests/kvm/x86_64/ |
D | tsc_scaling_sync.c | 50 unsigned long failures = 0; in run_vcpu() local 83 failures++; in run_vcpu() 91 return (void *)failures; in run_vcpu() 107 unsigned long failures = 0; in main() local 111 failures += (unsigned long)this_cpu_failures; in main() 114 TEST_ASSERT(!failures, "TSC sync failed"); in main()
|
/linux-6.1.9/tools/testing/selftests/vm/ |
D | mremap_test.c | 306 static void run_mremap_test_case(struct test test_case, int *failures, in run_mremap_test_case() argument 319 *failures += 1; in run_mremap_test_case() 379 int failures = 0; in main() local 458 run_mremap_test_case(test_cases[i], &failures, threshold_mb, in main() 467 run_mremap_test_case(perf_test_cases[i], &failures, in main() 471 if (failures > 0) in main()
|
/linux-6.1.9/tools/testing/selftests/bpf/ |
D | test_xsk.sh | 196 failures=0 202 failures=1 206 if [ $failures -eq 0 ]; then
|
D | README.rst | 49 Additional information about selftest failures are 52 profiler[23] test failures with clang/llvm <12.0.0 91 bpf_iter test failures with clang/llvm 10.0.0 177 old to support them, they shouldn't cause build failures or runtime test 178 failures:
|
/linux-6.1.9/Documentation/fault-injection/ |
D | fault-injection.rst | 13 injects slab allocation failures. (kmalloc(), kmem_cache_alloc(), ...) 17 injects page allocation failures. (alloc_pages(), get_free_pages(), ...) 21 injects failures in user memory access functions. (copy_from_user(), get_user(), ...) 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 108 Any positive value limits failures to only processes indicated by 133 default is 'Y', setting it to 'N' will also inject failures into 141 default is 'Y', setting it to 'N' will also inject failures 147 failures. [all …]
|
D | provoke-crashes.rst | 46 You can also induce failures by mounting debugfs and writing the type to
|
/linux-6.1.9/drivers/md/ |
D | dm-raid1.c | 62 struct bio_list failures; member 636 if (!ms->failures.head) in write_callback() 638 bio_list_add(&ms->failures, bio); in write_callback() 762 bio_list_merge(&ms->failures, &sync); in do_writes() 775 bio_list_add(&ms->failures, bio); in do_writes() 785 static void do_failures(struct mirror_set *ms, struct bio_list *failures) in do_failures() argument 789 if (likely(!failures->head)) in do_failures() 809 while ((bio = bio_list_pop(failures))) { in do_failures() 852 struct bio_list reads, writes, failures; in do_mirror() local 858 failures = ms->failures; in do_mirror() [all …]
|
/linux-6.1.9/tools/testing/selftests/net/ |
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-6.1.9/tools/perf/tests/ |
D | pmu-events.c | 845 int *failures = data; in test__parsing_callback() local 860 (*failures)++; in test__parsing_callback() 885 (*failures)--; in test__parsing_callback() 918 (*failures)--; in test__parsing_callback() 941 int failures = 0; in test__parsing() local 943 pmu_for_each_core_event(test__parsing_callback, &failures); in test__parsing() 944 pmu_for_each_sys_event(test__parsing_callback, &failures); in test__parsing() 946 return failures == 0 ? TEST_OK : TEST_FAIL; in test__parsing()
|
/linux-6.1.9/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-6.1.9/tools/testing/selftests/rcutorture/bin/ |
D | kvm-check-branches.sh | 97 echo '!!! ' $nfail failures in $ntry 'runs!!!' 100 echo No failures in $ntry runs.
|
D | torture.sh | 252 touch $T/failures 286 echo "$curflavor($retcode)" $resdir >> $T/failures 342 echo "allmodconfig($retcode)" $amcdir >> $T/failures 437 nfailures="`wc -l "$T/failures" | awk '{ print $1 }'`"
|
/linux-6.1.9/Documentation/mm/ |
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. 123 injected failures, not for real memory failures. Once any hardware 130 Only handle memory failures to pages associated with the file
|
/linux-6.1.9/arch/x86/kernel/cpu/sgx/ |
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-6.1.9/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()
|
/linux-6.1.9/drivers/net/ethernet/i825xx/ |
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-6.1.9/tools/testing/ktest/examples/include/ |
D | defaults.conf | 151 STORE_FAILURES = ${THIS_DIR}/failures
|
/linux-6.1.9/scripts/coccinelle/api/ |
D | platform_get_irq.cocci | 2 /// Remove dev_err() messages after platform_get_irq*() failures
|
/linux-6.1.9/tools/testing/selftests/drivers/net/mlxsw/ |
D | qos_lib.sh | 68 the other. That will cause spurious failures (or,
|
/linux-6.1.9/Documentation/core-api/ |
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-6.1.9/drivers/usb/image/ |
D | Kconfig | 26 Please report failures and successes.
|
/linux-6.1.9/Documentation/admin-guide/device-mapper/ |
D | dm-queue-length.rst | 23 <fail-count>: The number of path failures.
|
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-6.1.9/drivers/platform/x86/amd/ |
D | Kconfig | 15 mechanism to investigate the S2Idle transactions and failures.
|