openbsd/src/lib/libcrypto/man/lh_new.3, branch OPENBSD_7_9A mirror of https://github.com/libressl/openbsd.git
https://git.lua4.win/openbsd/atom?h=OPENBSD_7_92025-06-08T22:40:31+00:00.Lb libcrypto ; OK tb@2025-06-08T22:40:31+00:00schwarze2025-06-08T22:40:31+00:00urn:sha1:8be86af02fed1bda350c8dd14ee064cb66e3b0f5lh_<type>_error() is no longer implemented as a macro2024-03-05T22:15:29+00:00tb2024-03-05T22:15:29+00:00urn:sha1:ffec77e9bf09656d183822d723e988e43b83b765lh_new.3: zap a trailing comma2024-03-04T19:03:31+00:00tb2024-03-04T19:03:31+00:00urn:sha1:267b72de187376154c7e012f835dd4e9b70ce07dRemove lh stats2024-03-02T11:04:52+00:00tb2024-03-02T11:04:52+00:00urn:sha1:792421b3f220abcbd1405485edc9bf6b39485769
This could have been removed in an earlier bump. Now it's time for it to
say goodbye.
ok jsing
Make it safe to delete entries from an lhash doall callback.2024-01-24T14:02:52+00:00jsing2024-01-24T14:02:52+00:00urn:sha1:43687ee924fc2437d5b22b75c6b497ef06c60e4a
Currently, the callback cannot safely delete entries as it could lead to
contraction of the hash table, which in turn could lead to doall skipping
entries (and that typically leads to memory leaks). The recommended
workaround is to reach in and fiddle with the hash table internals in
order to prevent contraction, call the doall function and then restore
the internals that were changed.
Rather than just improving our documentation, actually make it safe to
delete entries from an lhash doall callback by pausing contractions prior
to starting the callback loop, then restoring the down load factor and
triggering contraction once completed. This means that callers no longer
need access to change hash table internals in order to achieve this same
behaviour.
ok tb@
man pages: add missing commas between subordinate and main clauses2022-03-31T17:27:26+00:00naddy2022-03-31T17:27:26+00:00urn:sha1:3d8be07546f5ec331a0f851b0ea88212376ebb95
jmc@ dislikes a comma before "then" in a conditional, so leave those
untouched.
ok jmc@
mention lh_strhash(3) in the NAME, SYNOPSIS, and HISTORY sections;2021-12-17T16:32:07+00:00schwarze2021-12-17T16:32:07+00:00urn:sha1:46aaaf46f8d64720d6a5143144b978caf6f8904c
while here, repair a typo in the lh_retrieve(3) synopsis
Be concise: do not say that void functions return no values, that's obvious.2020-03-28T22:40:58+00:00schwarze2020-03-28T22:40:58+00:00urn:sha1:f3775b337cafc42fea310ef0fd85720ffffe009e
Useless text reported by Martin Vahlensieck (academicsolutions.ch) on tech@.
add links back to crypto(3) to function group entry pages2019-06-10T09:49:48+00:00schwarze2019-06-10T09:49:48+00:00urn:sha1:56ffd9f2668f101af36752838043714323fc3351
and to isolated obsolete pages;
OK bcook@ jmc@
OPENSSL_realloc(3) is no longer used, we now use reallocarray(3)2019-06-04T18:31:33+00:00schwarze2019-06-04T18:31:33+00:00urn:sha1:1f727f4b3c8d675c27dc47de0aac03fca7d6ff98