| /src/tools/regression/security/proc_to_proc/ |
| H A D | scenario.c | 54 struct scenario { struct
89 static const struct scenario scenarios[] = {
137 int scenarios_count = sizeof(scenarios) / sizeof(struct scenario);
265 enact_scenario(int scenario) in enact_scenario() argument
281 error = cred_set(scenarios[scenario].sc_cred2); in enact_scenario()
314 error = cred_set(scenarios[scenario].sc_cred1); in enact_scenario()
337 scenarios[scenario].sc_canptrace_errno; in enact_scenario()
351 scenarios[scenario].sc_canktrace_errno; in enact_scenario()
359 scenarios[scenario].sc_cansighup_errno; in enact_scenario()
366 scenarios[scenario].sc_cansigsegv_errno; in enact_scenario()
[all …]
|
| H A D | Makefile | 8 SRCS= testuid.c scenario.c
|
| /src/tools/test/stress2/misc/ |
| H A D | execpath.sh | 90 /* Test scenario by Tobias Kortkamp <tobik@freebsd.org> */
|
| H A D | mprotect4.sh | 13 /* N readers and 1 writer threaded test scenario */
|
| H A D | mprotect5.sh | 13 /* N writers threaded test scenario */
|
| H A D | namecache.sh | 96 /* Test scenario for possible name cache problem */
|
| H A D | sendfile19.sh | 89 /* Slightly modified scenario from sendfile.sh */
|
| /src/sys/contrib/device-tree/src/arm64/rockchip/ |
| H A D | rk3588-jaguar-pre-ict-tester.dtso | 106 * the worst case scenario and the pass scenario expect
|
| /src/crypto/openssl/doc/man3/ |
| H A D | SSL_pending.pod | 40 this scenario for SSL_has_pending() to continue to return 1 even after an
|
| H A D | OSSL_ALGORITHM.pod | 110 In that scenario, you must make sure that the corresponding B<OSSL_ALGORITHM>'s
|
| H A D | OPENSSL_ia32cap.pod | 197 A more likely usage scenario would be to disable specific instruction set extensions.
|
| /src/crypto/openssl/doc/man7/ |
| H A D | EVP_PKEY-SM2.pod | 56 or EVP_DigestVerifyInit() in such a scenario.
|
| H A D | ossl-guide-tls-client-block.pod | 458 received one back. Usually in this scenario you would call L<SSL_shutdown(3)>
462 call to L<SSL_read_ex(3)>. So this scenario should never happen in practice. We
|
| /src/contrib/kyua/utils/process/ |
| H A D | executor_pid_test.cpp | 36 realistic scenario for this step.
|
| /src/contrib/unbound/testcode/ |
| H A D | fake_event.c | 247 struct replay_range* p = runtime->scenario->range_list; in pending_find_match()
797 runtime->now = runtime->scenario->mom_first; in advance_moment()
899 runtime->now = runtime->scenario->mom_first; in run_scenario()
998 runtime->scenario = saved_scenario; in comm_base_create()
1013 runtime->scenario= NULL; in comm_base_delete()
|
| /src/crypto/openssl/doc/designs/ |
| H A D | slh-dsa.md | 90 The scenario that is stated that this is useful for is when this encoded message
|
| H A D | ml-dsa.md | 85 The scenario that is stated that this is useful for is when this encoded message
|
| /src/crypto/openssl/doc/designs/quic-design/ |
| H A D | stream-receive-buffers.md | 128 in the single-copy scenario.
|
| /src/crypto/heimdal/doc/ |
| H A D | kerberos4.texi | 48 In a complex scenario you will need some kind of host lookup mechanism.
|
| /src/sys/contrib/zstd/ |
| H A D | CONTRIBUTING.md | 216 hands on a desktop, this is usually a better scenario.
270 bench option. You can run Zstd as you typically would for your scenario using some set of options
322 We will once again consider the scenario where you think you've identified a piece of code
|
| /src/contrib/nvi/cl/ |
| H A D | README.signal | 142 process group, not sent to a single process. The scenario goes something
|
| /src/crypto/krb5/src/plugins/kdb/db2/libdb2/test/SEQ_TEST/ |
| H A D | mbox | 374 ! * twice if you have duplicate records. The scenario is that the
|
| /src/sys/contrib/libsodium/m4/ |
| H A D | ax_pthread.m4 | 281 # linking. Such a scenario is extremely rare in practice.
|
| /src/sys/contrib/zstd/programs/ |
| H A D | README.md | 232 One such scenario is `tar --zstd`.
|
| /src/contrib/unbound/ |
| H A D | ax_pthread.m4 | 378 # linking. Such a scenario is extremely rare in practice.
|