openssl/test/lhash_test.c, branch dependabot/github_actions/actions/setup-python-7

Add mfail test for ossl_ht_free

2026-05-21T09:09:28Z

Reviewed-by: Neil Horman Reviewed-by: Paul Dale Reviewed-by: Tomas Mraz MergeDate: Thu May 21 09:09:37 2026 (Merged from https://github.com/openssl/openssl/pull/31237)

Add various MFAIL tests to excercise ht insert

2026-05-11T08:21:48Z

Reviewed-by: Nikola Pajkovsky Reviewed-by: Neil Horman Reviewed-by: Tomas Mraz MergeDate: Mon May 11 08:21:56 2026 (Merged from https://github.com/openssl/openssl/pull/31092)

Add ability to extract computed hash from hashtable

2026-03-24T16:22:47Z

One thing we can do to speed up hash table lookups is to cache/reuse computed hash values when interrogating a hash table multiple times in rapid succession. We follow this pattern frequently when using hashtables: value = lookup_hash(key) if (value == NULL) value = new_value() insert_to_hash(key, value) Note that we use the same key for the lookup and the insert. So if we had a way to preserve the value this key hashed to, we can avoid having to do a second hash computation during the lookup. These new macros give us that. The HT_KEY structure now stores the computed hash value in the key, which can be extracted and reused by the caller with the HT_INIT_KEY_CACHED macro. When set, the cached hash value is used, rather than needing to recompute the hash for any subsequent operations Reviewed-by: Paul Dale Reviewed-by: Saša Nedvědický MergeDate: Tue Mar 24 16:23:05 2026 (Merged from https://github.com/openssl/openssl/pull/30254)

Defang the lhash test

2025-12-17T13:45:38Z

This is bascially eating my mac, as it now runs for 80 seconds and eats all the CPU's exercising lock contention. This dials it back to consume at most a quarter of the CPU's in use by HARNESS_JOBS, unless LHASH_WORKERS is set to override it in which case we use that. Reviewed-by: Neil Horman Reviewed-by: Tom Cosgrove (Merged from https://github.com/openssl/openssl/pull/29406)

4.0-POST-CLANG-FORMAT-WEBKIT

2025-12-09T07:28:19Z

Reviewed-by: Saša Nedvědický Reviewed-by: Neil Horman Reviewed-by: Nikola Pajkovsky (Merged from https://github.com/openssl/openssl/pull/29242)

hashtable: add option to disable RCU locks

2025-10-02T12:05:02Z

a new config option _no_rcu_ is added into HT_CONFIG. When _no_rcu_ is set then hashtable can be guarded with any other locking primitives, and behives as ordinary hashtable. Also, all the impact of the atomics used internally to the hash table was mitigated. RCU performance # INFO: @ test/lhash_test.c:747 # multithread stress runs 40000 ops in 40.779656 seconds No RCU, guarded with RWLOCK # INFO: @ test/lhash_test.c:747 # multithread stress runs 40000 ops in 36.976926 seconds Signed-off-by: Nikola Pajkovsky Reviewed-by: Saša Nedvědický Reviewed-by: Tomas Mraz Reviewed-by: Neil Horman (Merged from https://github.com/openssl/openssl/pull/28677)

hashtable: pass HT into hash function

2025-10-02T12:04:47Z

When defining a custom hash function for a hashtable key, you typically start with: HT_START_KEY_DEFN(key) HT_DEF_KEY_FIELD(k, unsigned char *) HT_END_KEY_DEFN(KEY) In this setup, the hash function signature requires keybuf and len as parameters rather than the hashtable key itself. As a result, accessing members of the hashtable structure becomes awkward, since you must do something like: #define FROM_KEYBUF_TO_HT_KEY(keybuf, type) (type)((keybuf) - sizeof(HT_KEY)) static uint64_t ht_hash(uint8_t *keybuf, size_t keylen) { KEY *k = FROM_KEYBUF_TO_HT_KEY(keybuf, KEY *); ... } This kind of pointer arithmetic is both unnecessary and error-prone. A cleaner approach is to pass the HT pointer directly into the hash function. From there, you can safely cast it to the required type without the pointer gymnastics. Signed-off-by: Nikola Pajkovsky Reviewed-by: Saša Nedvědický Reviewed-by: Tomas Mraz Reviewed-by: Neil Horman (Merged from https://github.com/openssl/openssl/pull/28677)

Fix failure checking on rcu_read_lock

2025-08-09T13:22:13Z

during memfail testing: https://github.com/openssl/openssl/actions/runs/16794088536/job/47561223902 We get lots of test failures in ossl_rcu_read_lock. This occurs because we have a few cases in the read lock path that attempt mallocs, which, if they fail, trigger an assert or a silent failure, which isn't really appropriate. We should instead fail gracefully, by informing the caller that the lock failed, like we do for CRYPTO_THREAD_read_lock. Fortunately, these are all internal apis, so we can convert ossl_rcu_read_lock to return an int indicating success/failure, and fail gracefully during the test, rather than hitting an assert abort. Fixes openssl/project#1315 Reviewed-by: Paul Yang Reviewed-by: Dmitry Belyavskiy Reviewed-by: Paul Dale (Merged from https://github.com/openssl/openssl/pull/28195)

test: Silence warnings on Win64 builds

2025-07-02T15:26:26Z

Reviewed-by: Saša Nedvědický Reviewed-by: Neil Horman (Merged from https://github.com/openssl/openssl/pull/27806)

Copyright year updates

2025-03-12T13:35:59Z

Reviewed-by: Neil Horman Reviewed-by: Matt Caswell Release: yes