Searched refs:after (Results 1 – 10 of 10) sorted by relevance
| /lib/tests/ |
| A D | randstruct_kunit.c | 96 int after; member
102 int after; member
|
| A D | memcpy_kunit.c | 238 struct some_bytes after = { in memset_test() local
286 compare("memset_after()", dest, after); in memset_test()
|
| /lib/ |
| A D | Kconfig.kfence | 13 access, use-after-free, and invalid-free errors. KFENCE is designed
80 pages, resulting in spurious use-after-frees. The main purpose of
|
| A D | Kconfig.kgdb | 131 int "KDB: continue after catastrophic errors"
155 won't actually be processed until dbg_late_init() just after the
|
| A D | Kconfig.kasan | 44 error detector designed to find out-of-bounds and use-after-free bugs.
192 out-of-bounds and use-after-free accesses. Useful for testing whether
|
| A D | Kconfig.kcsan | 106 For tasks, the microsecond delay after setting up a watchpoint.
112 For interrupts, the microsecond delay after setting up a watchpoint.
|
| A D | Kconfig.debug | 34 Since toggling after boot makes the code racy, currently there is
95 by inserting a short delay after each one. The delay is
495 The section mismatch analysis is always performed after a full
1065 anything erroneous after an oops which could result in data
1127 to cause the system to reboot automatically after a
1275 to cause the system to reboot automatically after a
1603 after the fact on the running kernel to be tested, if desired.
1629 module may be built after the fact on the running kernel to
1711 to get the CRNG seeded sooner after the system is booted.
1739 However, some buggy drivers assume that after such an operation,
[all …]
|
| /lib/kunit/ |
| A D | Kconfig | 89 tests will not run after initialization unless kunit.autorun=1 is
|
| /lib/crypto/x86/ |
| A D | chacha-avx512vl-x86_64.S | 37 # rearrange the words after each round.
|
| A D | chacha-avx2-x86_64.S | 47 # rearrange the words after each round.
|
Completed in 22 milliseconds