diff options
author | Stef Walter <stefw@gnome.org> | 2012-01-23 09:09:31 +0100 |
---|---|---|
committer | Stef Walter <stefw@gnome.org> | 2012-01-23 18:04:58 +0100 |
commit | 53c34e8ff80500d6ef9366453e88c27a3a52ee46 (patch) | |
tree | 7db7175d5c0a302c751c937483acefd033e0757d /NEWS | |
parent | 001d59596a37369d094edcace455f611d9f55908 (diff) |
Remove automatic reinitialization of PKCS#11 after fork
* First of all one should only call async-signal-safe functions
from the callbacks of pthread_atfork(), and so we cannot
reinitialize directly.
* Some modules use pthread_atfork() to detect forking and setup
their internal state. If we call into them in our pthread_atfork()
callback then this is inherently racy.
* There was danger of endless loops and deadlocks which are caused
by handlers which fork in their C_Initialize
* Many processes do fork/exec, reinitializing PKCS#11 for these
forks is quite resourc intensive when the child process won't use
PKCS#11 at all.
Diffstat (limited to 'NEWS')
0 files changed, 0 insertions, 0 deletions