threads.pod 4.2 KB
Newer Older
U
Ulf Möller 已提交
1 2 3 4
=pod

=head1 NAME

5
CRYPTO_THREAD_run_once,
6 7
CRYPTO_THREAD_lock_new, CRYPTO_THREAD_read_lock, CRYPTO_THREAD_write_lock,
CRYPTO_THREAD_unlock, CRYPTO_THREAD_lock_free, CRYPTO_atomic_add - OpenSSL thread support
U
Ulf Möller 已提交
8 9 10 11 12

=head1 SYNOPSIS

 #include <openssl/crypto.h>

13 14 15
 CRYPTO_ONCE CRYPTO_ONCE_STATIC_INIT;
 int CRYPTO_THREAD_run_once(CRYPTO_ONCE *once, void (*init)(void));

16 17 18 19 20 21 22
 CRYPTO_RWLOCK *CRYPTO_THREAD_lock_new(void);
 int CRYPTO_THREAD_read_lock(CRYPTO_RWLOCK *lock);
 int CRYPTO_THREAD_write_lock(CRYPTO_RWLOCK *lock);
 int CRYPTO_THREAD_unlock(CRYPTO_RWLOCK *lock);
 void CRYPTO_THREAD_lock_free(CRYPTO_RWLOCK *lock);

 int CRYPTO_atomic_add(int *val, int amount, int *ret, CRYPTO_RWLOCK *lock);
23

U
Ulf Möller 已提交
24 25
=head1 DESCRIPTION

26 27 28 29 30 31 32 33
OpenSSL can be safely used in multi-threaded applications provided that
support for the underlying OS threading API is built-in. Currently, OpenSSL
supports the pthread and Windows APIs. OpenSSL can also be built without
any multi-threading support, for example on platforms that don't provide
any threading support or that provide a threading API that is not yet
supported by OpenSSL.

The following multi-threading function are provided:
34 35 36

=over 4

37 38 39 40 41 42 43 44 45 46
=item *
CRYPTO_THREAD_run_once() can be used to perform one-time initialization.
The B<once> argument must be a pointer to a static object of type
B<CRYPTO_ONCE> that was statically initialized to the value
B<CRYPTO_ONCE_STATIC_INIT>.
The B<init> argument is a pointer to a function that performs the desired
exactly once initialization.
In particular, this can be used to allocate locks in a thread-safe manner,
which can then be used with the locking functions below.

47
=item *
48 49
CRYPTO_THREAD_lock_new() allocates, initializes and returns a new read/write
lock.
50 51

=item *
52
CRYPTO_THREAD_read_lock() locks the provided B<lock> for reading.
53 54

=item *
55
CRYPTO_THREAD_write_lock() locks the provided B<lock> for writing.
56 57

=item *
58
CRYPTO_THREAD_unlock() unlocks the previously locked B<lock>.
59

60
=item *
61
CRYPTO_THREAD_lock_frees() frees the provided B<lock>.
62 63

=item *
64 65 66 67 68
CRYPTO_atomic_add() atomically adds B<amount> to B<val> and returns the
result of the operation in B<ret>. B<lock> will be locked, unless atomic
operations are supported on the specific platform. Because of this, if a
variable is modified by CRYPTO_atomic_add() then CRYPTO_atomic_add() must
be the only way that the variable is modified.
69

70 71
=back

72
=head1 RETURN VALUES
U
Ulf Möller 已提交
73

74 75
CRYPTO_THREAD_run_once() returns 1 on success, or 0 on error.

76
CRYPTO_THREAD_lock_new() returns the allocated lock, or NULL on error.
77

78
CRYPTO_THREAD_lock_frees() returns no value.
79

80
The other functions return 1 on success or 0 on error.
U
Ulf Möller 已提交
81

82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125
=head1 EXAMPLE

This example safely initializes and uses a lock.

  #include <openssl/crypto.h>
  
  static CRYPTO_ONCE once = CRYPTO_ONCE_STATIC_INIT;
  static CRYPTO_RWLOCK *lock;
  
  static void myinit(void)
  {
      lock = CRYPTO_THREAD_lock_new();
  }
  
  static int mylock(void)
  {
      if (!CRYPTO_THREAD_run_once(&once, void init) || lock == NULL)
          return 0;
      return CRYPTO_THREAD_write_lock(lock);
  }
  
  static int myunlock(void)
  {
      return CRYPTO_THREAD_unlock(lock);
  }
  
  int serialized(void)
  {
      int ret = 0;
  
      if (mylock()) {
          /* Your code here, do not return without releasing the lock! */
          ret = ... ;
      }
      myunlock();
      return ret;
  }

Finalization of locks is an advanced topic, not covered in this example.
This can only be done at process exit or when a dynamically loaded library is
no longer in use and is unloaded.
The simplest solution is to just "leak" the lock in applications and not
repeatedly load/unload shared libraries that allocate locks.

126
=head1 NOTES
U
Ulf Möller 已提交
127 128 129 130

You can find out if OpenSSL was configured with thread support:

 #include <openssl/opensslconf.h>
131
 #if defined(OPENSSL_THREADS)
U
Ulf Möller 已提交
132 133 134 135 136 137 138
   // thread support enabled
 #else
   // no thread support
 #endif

=head1 SEE ALSO

R
Rich Salz 已提交
139
L<crypto(3)>
U
Ulf Möller 已提交
140 141

=cut
R
Rich Salz 已提交
142 143 144 145 146 147 148 149 150 151 152

=head1 COPYRIGHT

Copyright 2000-2016 The OpenSSL Project Authors. All Rights Reserved.

Licensed under the OpenSSL license (the "License").  You may not use
this file except in compliance with the License.  You can obtain a copy
in the file LICENSE in the source distribution or at
L<https://www.openssl.org/source/license.html>.

=cut