openssl/crypto/hashtable, branch openssl-3.5.6

Copyright year updates

2026-04-07T12:24:29Z

Reviewed-by: Neil Horman Reviewed-by: Eugene Syromiatnikov MergeDate: Tue Apr 7 12:24:30 2026 Release: yes

Ensure entries in the neighborhood struct are 8 byte aligned

2026-03-10T18:18:56Z

This struct is accessed via atomics, which on some platforms require 8 byte alignment. Generally compilers provide that alignment, since the first element of the struct is a uint64_t, but it appears that not all do. Force the alignment to be correct Reviewed-by: Eugene Syromiatnikov Reviewed-by: Tomas Mraz Reviewed-by: Nikola Pajkovsky MergeDate: Tue Mar 10 18:16:34 2026 (Merged from https://github.com/openssl/openssl/pull/30293) (cherry picked from commit a743be6d2d3f8b2eaebe7ff933f27b1e74cfebe5)

3.5-POST-CLANG-FORMAT-WEBKIT

2025-12-09T09:40:50Z

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

Copyright year updates

2025-03-12T13:35:59Z

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

Rename fnv1a_hash() to ossl_fnv1a_hash()

2025-02-25T14:45:42Z

It is no longer static. Also add it to libssl only with quic enabled. Reviewed-by: Paul Dale Reviewed-by: Neil Horman Reviewed-by: Saša Nedvědický Reviewed-by: Tim Hudson (Merged from https://github.com/openssl/openssl/pull/26882)

de-duplicate fnv1a_hash

2025-02-17T16:27:34Z

I cloned a copy of fnv1a_hash from hashtable.c. Deduplicate that so we have common source code. Reviewed-by: Matt Caswell Reviewed-by: Saša Nedvědický (Merged from https://github.com/openssl/openssl/pull/26517)

ossl_ht_insert(): Allow for 4 iterations of grow_hashtable()

2024-08-22T12:52:43Z

Reviewed-by: Matt Caswell Reviewed-by: Neil Horman (Merged from https://github.com/openssl/openssl/pull/25273)

hashtable.c: Code style fixes

2024-08-21T13:21:26Z

Reviewed-by: Neil Horman Reviewed-by: Paul Dale (Merged from https://github.com/openssl/openssl/pull/24504)

For lockless reads use the whole hashtable for colliding entries

2024-08-21T13:21:26Z

Instead of just using the neighborhood, fill subsequent neighborhoods with colliding entries. If the hashtable is properly sized, it won't degrade performance too much. Reviewed-by: Neil Horman Reviewed-by: Paul Dale (Merged from https://github.com/openssl/openssl/pull/24504)

hashtable: Support lockless reads

2024-08-21T13:21:25Z

Also build it in the FIPS provider too and properly report error on insert when hashtable cannot be grown. Reviewed-by: Neil Horman Reviewed-by: Paul Dale (Merged from https://github.com/openssl/openssl/pull/24504)