Issue #18747: Fix spelling errors in my commit message and comments,

thanks to Vajrasky Kok for proof-reading.
This commit is contained in:
Christian Heimes 2013-08-25 14:19:16 +02:00
parent f869a9484a
commit 8ee5ffddf5
2 changed files with 3 additions and 3 deletions

View File

@ -44,7 +44,7 @@ Library
module will be called in a deterministic order. module will be called in a deterministic order.
- Issue #18747: Re-seed OpenSSL's pseudo-random number generator after fork. - Issue #18747: Re-seed OpenSSL's pseudo-random number generator after fork.
A pthread_atfork() parent handler is used to seeded the PRNG with pid, time A pthread_atfork() parent handler is used to seed the PRNG with pid, time
and some stack data. and some stack data.
- Issue #8865: Concurrent invocation of select.poll.poll() now raises a - Issue #8865: Concurrent invocation of select.poll.poll() now raises a

View File

@ -1629,7 +1629,7 @@ fails or if it does not provide enough data to seed PRNG.");
/* Seed OpenSSL's PRNG at fork(), http://bugs.python.org/issue18747 /* Seed OpenSSL's PRNG at fork(), http://bugs.python.org/issue18747
* *
* The parent handler seeds the PRNG from pseudo-random data like pid, the * The parent handler seeds the PRNG from pseudo-random data like pid, the
* current time (miliseconds or seconds) and an uninitialized arry. * current time (miliseconds or seconds) and an uninitialized array.
* The array contains stack variables that are impossible to predict * The array contains stack variables that are impossible to predict
* on most systems, e.g. function return address (subject to ASLR), the * on most systems, e.g. function return address (subject to ASLR), the
* stack protection canary and automatic variables. * stack protection canary and automatic variables.
@ -1638,7 +1638,7 @@ fails or if it does not provide enough data to seed PRNG.");
* Note: * Note:
* The code uses pthread_atfork() until Python has a proper atfork API. The * The code uses pthread_atfork() until Python has a proper atfork API. The
* handlers are not removed from the child process. A parent handler is used * handlers are not removed from the child process. A parent handler is used
* instead of a child handler because fork() is suppose to be async-signal * instead of a child handler because fork() is supposed to be async-signal
* safe but the handler calls unsafe functions. * safe but the handler calls unsafe functions.
*/ */