#
f352c808 |
| 17-Apr-2024 |
Richard Levitte |
For Unix, refactor OSSL_sleep() to use nanosleep() instead of usleep() usleep() is obsolete since POSIX.1-2001 and removed in POSIX.1-2008, in favor of nanosleep(), which has been presen
For Unix, refactor OSSL_sleep() to use nanosleep() instead of usleep() usleep() is obsolete since POSIX.1-2001 and removed in POSIX.1-2008, in favor of nanosleep(), which has been present since POSIX.1-2001. The exceptions for DJGPP and TANDEM are preserved. Also, just in case nanosleep() turns out to be unavailable on any Unix machinery that we are unaware of, we allow a revert to using usleep() by defining OPENSSL_USE_USLEEP. Reviewed-by: Tom Cosgrove <tom.cosgrove@arm.com> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from https://github.com/openssl/openssl/pull/24173)
show more ...
|
#
496bc128 |
| 29-Mar-2024 |
Matt Caswell |
Copyright year updates Reviewed-by: Neil Horman <nhorman@openssl.org> Release: yes (cherry picked from commit 3764f200f9d44622faa8ac1b15d2f3eb7c39e473) Reviewed-by: Hugo Lan
Copyright year updates Reviewed-by: Neil Horman <nhorman@openssl.org> Release: yes (cherry picked from commit 3764f200f9d44622faa8ac1b15d2f3eb7c39e473) Reviewed-by: Hugo Landau <hlandau@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from https://github.com/openssl/openssl/pull/24034)
show more ...
|
#
0d2a5f60 |
| 30-Mar-2024 |
Randall S. Becker |
NonStop: Do not call sleep() with a 0 value This change ensures that sleep(0) is not invoked to cause unexpected duplicate thread context switches when _REENTRANT is specified.
NonStop: Do not call sleep() with a 0 value This change ensures that sleep(0) is not invoked to cause unexpected duplicate thread context switches when _REENTRANT is specified. Fixes: #24009 Signed-off-by: Randall S. Becker <randall.becker@nexbridge.ca> Reviewed-by: Neil Horman <nhorman@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from https://github.com/openssl/openssl/pull/24012) (cherry picked from commit c89fe574493f438dd0e94bb9a89227e4ca84c0b7)
show more ...
|
#
4a9e48f7 |
| 21-Mar-2024 |
Randall S. Becker |
Correct OSSL_sleep for NonStop PUT model by introducing sleep(). This fix also removes SPT model support as it was previously deprecated. Upcoming threading models on the platform should
Correct OSSL_sleep for NonStop PUT model by introducing sleep(). This fix also removes SPT model support as it was previously deprecated. Upcoming threading models on the platform should be supportable without change to this method. Fixes: #23923 Fixes: #23927 Fixes: #23928 Signed-off-by: Randall S. Becker <randall.becker@nexbridge.ca> Reviewed-by: Neil Horman <nhorman@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> Reviewed-by: Matt Caswell <matt@openssl.org> (Merged from https://github.com/openssl/openssl/pull/23926)
show more ...
|
#
da1c088f |
| 07-Sep-2023 |
Matt Caswell |
Copyright year updates Reviewed-by: Richard Levitte <levitte@openssl.org> Release: yes
|
#
2631a941 |
| 22-May-2023 |
Rajarshi Karmakar |
OSSL_sleep(): Calling sleep() function if sleepTime > 1sec On some systems usleep() func does not support time >1sec. Reviewed-by: Matt Caswell <matt@openssl.org> Reviewed-by: R
OSSL_sleep(): Calling sleep() function if sleepTime > 1sec On some systems usleep() func does not support time >1sec. Reviewed-by: Matt Caswell <matt@openssl.org> Reviewed-by: Richard Levitte <levitte@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from https://github.com/openssl/openssl/pull/21010)
show more ...
|
#
c0e090bd |
| 11-Apr-2023 |
Aidan Khoury |
Fix UEFI support on win32 Reviewed-by: Hugo Landau <hlandau@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from https://github.com/openssl/openssl/pull/20714)
|
#
bea92b8c |
| 17-Mar-2023 |
Tomas Mraz |
sleep.c: Limit the sleep time instead of sleeping for days or even years As the sleep() call is interruptible, it is not even a good idea to call it in a loop if the caller uses some rid
sleep.c: Limit the sleep time instead of sleeping for days or even years As the sleep() call is interruptible, it is not even a good idea to call it in a loop if the caller uses some ridiculously large value as an infinity just waiting for an interrupt. Fixes #20524 Reviewed-by: David von Oheimb <david.von.oheimb@siemens.com> Reviewed-by: Richard Levitte <levitte@openssl.org> Reviewed-by: Tom Cosgrove <tom.cosgrove@arm.com> (Merged from https://github.com/openssl/openssl/pull/20533)
show more ...
|
#
82d28c6b |
| 03-Oct-2022 |
Richard Levitte |
Rename ossl_sleep() to OSSL_sleep() and make it public ossl_sleep() was implemented as a static inline function in internal/e_os.h, using usleep() on Unix and Sleep() on Windows. So far
Rename ossl_sleep() to OSSL_sleep() and make it public ossl_sleep() was implemented as a static inline function in internal/e_os.h, using usleep() on Unix and Sleep() on Windows. So far well and good. However, it also has a fallback implementation for systems that do not have usleep() or Sleep(), and that implementation happens to use ossl_time_now(), which is a normal function, private to libcrypto, and is judged to be too complex to sanely make into a static inline function. This fallback creates a problem, because we do use ossl_sleep() in apps/ and a few test programs in test/, and when they are linked with libcrypto in shared library form, ossl_time_now() can't be found, since it's not publicly exposed. Something needs to give, and the easiest, and hopefully sanest answer is to make ossl_sleep() a publicly exposed function, which requires a slight name change. Documentation and 'make update' result included. Reviewed-by: Paul Dale <pauli@openssl.org> Reviewed-by: Matt Caswell <matt@openssl.org> Reviewed-by: Tim Hudson <tjh@openssl.org> Reviewed-by: Dmitry Belyavskiy <beldmit@gmail.com> (Merged from https://github.com/openssl/openssl/pull/19330)
show more ...
|