| /Linux-v5.10/lib/ |
| D | test_meminit.c | 20 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()
350 int failures = 0, num_tests = 0; in test_kmemcache() local
[all …]
|
| D | test_stackinit.c | 342 unsigned int failures = 0; in test_stackinit_init() local
345 failures += test_u8_ ## init (); \ in test_stackinit_init()
346 failures += test_u16_ ## init (); \ in test_stackinit_init()
347 failures += test_u32_ ## init (); \ in test_stackinit_init()
348 failures += test_u64_ ## init (); \ in test_stackinit_init()
349 failures += test_char_array_ ## init (); \ in test_stackinit_init()
353 failures += test_small_hole_ ## init (); \ in test_stackinit_init()
354 failures += test_big_hole_ ## init (); \ in test_stackinit_init()
355 failures += test_trailing_hole_ ## init (); \ in test_stackinit_init()
356 failures += test_packed_ ## init (); \ in test_stackinit_init()
[all …]
|
| /Linux-v5.10/tools/testing/selftests/bpf/ |
| D | README.rst | 7 Additional information about selftest failures are
10 profiler[23] test failures with clang/llvm <12.0.0
48 bpf_iter test failures with clang/llvm 10.0.0
94 old to support them, they shouldn't cause build failures or runtime test
95 failures:
|
| /Linux-v5.10/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(), ...)
73 specifies the interval between failures, for calls to
81 specifies how many times failures may happen at most.
104 Any positive value limits failures to only processes indicated by
129 default is 'N', setting it to 'Y' won't inject failures into
137 default is 'N', setting it to 'Y' will inject failures
143 failures.
241 - add a hook to insert failures
[all …]
|
| D | provoke-crashes.rst | 47 You can also induce failures by mounting debugfs and writing the type to
|
| D | notifier-error-inject.rst | 6 notifier call chain failures which is rarely executed. There are kernel
|
| /Linux-v5.10/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 | 250 drive->failures++; in reset_pollfunc()
257 drive->failures = 0; in reset_pollfunc()
260 drive->failures++; in reset_pollfunc()
|
| /Linux-v5.10/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-v5.10/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-v5.10/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-v5.10/tools/testing/selftests/rcutorture/bin/ |
| D | kvm-check-branches.sh | 103 echo '!!! ' $nfail failures in $ntry 'runs!!!'
106 echo No failures in $ntry runs.
|
| /Linux-v5.10/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-v5.10/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-v5.10/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-v5.10/tools/testing/ktest/examples/include/ |
| D | defaults.conf | 151 STORE_FAILURES = ${THIS_DIR}/failures
|
| /Linux-v5.10/scripts/coccinelle/api/ |
| D | platform_get_irq.cocci | 2 /// Remove dev_err() messages after platform_get_irq*() failures
|
| /Linux-v5.10/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-v5.10/tools/testing/selftests/drivers/net/mlxsw/ |
| D | qos_lib.sh | 68 the other. That will cause spurious failures (or,
|
| /Linux-v5.10/drivers/usb/image/ |
| D | Kconfig | 26 Please report failures and successes.
|
| /Linux-v5.10/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-v5.10/Documentation/power/ |
| 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-v5.10/fs/xfs/ |
| 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
|
| /Linux-v5.10/Documentation/userspace-api/ |
| D | iommu.rst | 86 vIOMMU operation, such as cache invalidation failures cannot be nicely
88 catastrophic failures for the users.
|
