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

=head1 NAME

5 6 7
CRYPTO_THREADID_set_callback, CRYPTO_THREADID_get_callback,
CRYPTO_THREADID_current, CRYPTO_THREADID_cmp, CRYPTO_THREADID_cpy,
CRYPTO_THREADID_hash, CRYPTO_set_locking_callback, CRYPTO_num_locks,
8 9 10
CRYPTO_set_dynlock_create_callback, CRYPTO_set_dynlock_lock_callback,
CRYPTO_set_dynlock_destroy_callback, CRYPTO_get_new_dynlockid,
CRYPTO_destroy_dynlockid, CRYPTO_lock - OpenSSL thread support
U
Ulf Möller 已提交
11 12 13 14 15

=head1 SYNOPSIS

 #include <openssl/crypto.h>

16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
 /* Don't use this structure directly. */
 typedef struct crypto_threadid_st
         {
         void *ptr;
         unsigned long val;
         } CRYPTO_THREADID;
 /* Only use CRYPTO_THREADID_set_[numeric|pointer]() within callbacks */
 void CRYPTO_THREADID_set_numeric(CRYPTO_THREADID *id, unsigned long val);
 void CRYPTO_THREADID_set_pointer(CRYPTO_THREADID *id, void *ptr);
 int CRYPTO_THREADID_set_callback(void (*threadid_func)(CRYPTO_THREADID *));
 void (*CRYPTO_THREADID_get_callback(void))(CRYPTO_THREADID *);
 void CRYPTO_THREADID_current(CRYPTO_THREADID *id);
 int CRYPTO_THREADID_cmp(const CRYPTO_THREADID *a,
                         const CRYPTO_THREADID *b);
 void CRYPTO_THREADID_cpy(CRYPTO_THREADID *dest,
                          const CRYPTO_THREADID *src);
 unsigned long CRYPTO_THREADID_hash(const CRYPTO_THREADID *id);
33

U
Ulf Möller 已提交
34 35
 int CRYPTO_num_locks(void);

36
 /* struct CRYPTO_dynlock_value needs to be defined by the user */
37
 struct CRYPTO_dynlock_value;
38

39
 void CRYPTO_set_dynlock_create_callback(struct CRYPTO_dynlock_value *
40
	(*dyn_create_function)(const char *file, int line));
41
 void CRYPTO_set_dynlock_lock_callback(void (*dyn_lock_function)
42 43
	(int mode, struct CRYPTO_dynlock_value *l,
	const char *file, int line));
44
 void CRYPTO_set_dynlock_destroy_callback(void (*dyn_destroy_function)
45
	(struct CRYPTO_dynlock_value *l, const char *file, int line));
46 47 48 49 50 51 52

 int CRYPTO_get_new_dynlockid(void);

 void CRYPTO_destroy_dynlockid(int i);

 void CRYPTO_lock(int mode, int n, const char *file, int line);

53 54 55 56 57 58 59 60 61 62 63
 #define CRYPTO_w_lock(type)	\
	CRYPTO_lock(CRYPTO_LOCK|CRYPTO_WRITE,type,__FILE__,__LINE__)
 #define CRYPTO_w_unlock(type)	\
	CRYPTO_lock(CRYPTO_UNLOCK|CRYPTO_WRITE,type,__FILE__,__LINE__)
 #define CRYPTO_r_lock(type)	\
	CRYPTO_lock(CRYPTO_LOCK|CRYPTO_READ,type,__FILE__,__LINE__)
 #define CRYPTO_r_unlock(type)	\
	CRYPTO_lock(CRYPTO_UNLOCK|CRYPTO_READ,type,__FILE__,__LINE__)
 #define CRYPTO_add(addr,amount,type)	\
	CRYPTO_add_lock(addr,amount,type,__FILE__,__LINE__)

U
Ulf Möller 已提交
64 65 66
=head1 DESCRIPTION

OpenSSL can safely be used in multi-threaded applications provided
67 68
that at least two callback functions are set, locking_function and
threadid_func.
U
Ulf Möller 已提交
69

U
Ulf Möller 已提交
70
locking_function(int mode, int n, const char *file, int line) is
B
clarify  
Bodo Möller 已提交
71 72 73 74
needed to perform locking on shared data structures. 
(Note that OpenSSL uses a number of global data structures that
will be implicitly shared whenever multiple threads use OpenSSL.)
Multi-threaded applications will crash at random if it is not set.
U
Ulf Möller 已提交
75

U
Ulf Möller 已提交
76
locking_function() must be able to handle up to CRYPTO_num_locks()
U
Ulf Möller 已提交
77
different mutex locks. It sets the B<n>-th lock if B<mode> &
U
Ulf Möller 已提交
78 79 80 81 82
B<CRYPTO_LOCK>, and releases it otherwise.

B<file> and B<line> are the file number of the function setting the
lock. They can be useful for debugging.

83 84 85 86 87 88 89 90 91 92
threadid_func(CRYPTO_THREADID *id) is needed to record the currently-executing
thread's identifier into B<id>. The implementation of this callback should not
fill in B<id> directly, but should use CRYPTO_THREADID_set_numeric() if thread
IDs are numeric, or CRYPTO_THREADID_set_pointer() if they are pointer-based.
If the application does not register such a callback using
CRYPTO_THREADID_set_callback(), then a default implementation is used - on
Windows and BeOS this uses the system's default thread identifying APIs, and on
all other platforms it uses the address of B<errno>. The latter is satisfactory
for thread-safety if and only if the platform has a thread-local error number
facility.
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
Once threadid_func() is registered, or if the built-in default implementation is
to be used;

=over 4

=item *
CRYPTO_THREADID_current() records the currently-executing thread ID into the
given B<id> object.

=item *
CRYPTO_THREADID_cmp() compares two thread IDs (returning zero for equality, ie.
the same semantics as memcmp()).

=item *
CRYPTO_THREADID_cpy() duplicates a thread ID value,

=item *
CRYPTO_THREADID_hash() returns a numeric value usable as a hash-table key. This
is usually the exact numeric or pointer-based thread ID used internally, however
this also handles the unusual case where pointers are larger than 'long'
variables and the platform's thread IDs are pointer-based - in this case, mixing
is done to attempt to produce a unique numeric value even though it is not as
wide as the platform's true thread IDs.

=back
U
Ulf Möller 已提交
119

120 121 122 123
Additionally, OpenSSL supports dynamic locks, and sometimes, some parts
of OpenSSL need it for better performance.  To enable this, the following
is required:

124 125
=over 4

126 127 128 129 130 131 132
=item *
Three additional callback function, dyn_create_function, dyn_lock_function
and dyn_destroy_function.

=item *
A structure defined with the data that each lock needs to handle.

133 134
=back

135 136 137 138 139 140 141
struct CRYPTO_dynlock_value has to be defined to contain whatever structure
is needed to handle locks.

dyn_create_function(const char *file, int line) is needed to create a
lock.  Multi-threaded applications might crash at random if it is not set.

dyn_lock_function(int mode, CRYPTO_dynlock *l, const char *file, int line)
U
ispell.  
Ulf Möller 已提交
142
is needed to perform locking off dynamic lock numbered n. Multi-threaded
143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158
applications might crash at random if it is not set.

dyn_destroy_function(CRYPTO_dynlock *l, const char *file, int line) is
needed to destroy the lock l. Multi-threaded applications might crash at
random if it is not set.

CRYPTO_get_new_dynlockid() is used to create locks.  It will call
dyn_create_function for the actual creation.

CRYPTO_destroy_dynlockid() is used to destroy locks.  It will call
dyn_destroy_function for the actual destruction.

CRYPTO_lock() is used to lock and unlock the locks.  mode is a bitfield
describing what should be done with the lock.  n is the number of the
lock as returned from CRYPTO_get_new_dynlockid().  mode can be combined
from the following values.  These values are pairwise exclusive, with
159
undefined behaviour if misused (for example, CRYPTO_READ and CRYPTO_WRITE
160 161 162 163 164 165 166
should not be used together):

	CRYPTO_LOCK	0x01
	CRYPTO_UNLOCK	0x02
	CRYPTO_READ	0x04
	CRYPTO_WRITE	0x08

167
=head1 RETURN VALUES
U
Ulf Möller 已提交
168 169

CRYPTO_num_locks() returns the required number of locks.
170 171 172

CRYPTO_get_new_dynlockid() returns the index to the newly created lock.

U
Ulf Möller 已提交
173 174
The other functions return no values.

175
=head1 NOTES
U
Ulf Möller 已提交
176 177 178 179 180

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

 #define OPENSSL_THREAD_DEFINES
 #include <openssl/opensslconf.h>
181
 #if defined(OPENSSL_THREADS)
U
Ulf Möller 已提交
182 183 184 185 186
   // thread support enabled
 #else
   // no thread support
 #endif

187 188 189
Also, dynamic locks are currently not used internally by OpenSSL, but
may do so in the future.

U
Ulf Möller 已提交
190 191 192 193 194 195 196
=head1 EXAMPLES

B<crypto/threads/mttest.c> shows examples of the callback functions on
Solaris, Irix and Win32.

=head1 HISTORY

197
CRYPTO_set_locking_callback() is
U
Ulf Möller 已提交
198
available in all versions of SSLeay and OpenSSL.
U
Ulf Möller 已提交
199
CRYPTO_num_locks() was added in OpenSSL 0.9.4.
200
All functions dealing with dynamic locks were added in OpenSSL 0.9.5b-dev.
201
B<CRYPTO_THREADID> and associated functions were introduced in OpenSSL 1.0.0
202 203 204
to replace (actually, deprecate) the previous CRYPTO_set_id_callback(),
CRYPTO_get_id_callback(), and CRYPTO_thread_id() functions which assumed
thread IDs to always be represented by 'unsigned long'.
205

U
Ulf Möller 已提交
206 207 208 209 210
=head1 SEE ALSO

L<crypto(3)|crypto(3)>

=cut