diff options
| author | Matt Caswell <matt@openssl.org> | 2016-10-21 13:25:19 +0100 |
|---|---|---|
| committer | Matt Caswell <matt@openssl.org> | 2016-10-28 09:13:49 +0100 |
| commit | 4880672a9b41a09a0984b55e219f02a2de7ab75e (patch) | |
| tree | 57ef382cbff79376ffee653ed75c2417a8dbfafc /test/asynciotest.c | |
| parent | 875e3f934e8586039e79efb6ed1262c80803aa42 (diff) | |
| download | openssl-4880672a9b41a09a0984b55e219f02a2de7ab75e.zip openssl-4880672a9b41a09a0984b55e219f02a2de7ab75e.tar.gz openssl-4880672a9b41a09a0984b55e219f02a2de7ab75e.tar.bz2 | |
A zero return from BIO_read()/BIO_write() could be retryable
A zero return from BIO_read()/BIO_write() could mean that an IO operation
is retryable. A zero return from SSL_read()/SSL_write() means that the
connection has been closed down (either cleanly or not). Therefore we
should not propagate a zero return value from BIO_read()/BIO_write() back
up the stack to SSL_read()/SSL_write(). This could result in a retryable
failure being treated as fatal.
Reviewed-by: Richard Levitte <levitte@openssl.org>
Diffstat (limited to 'test/asynciotest.c')
0 files changed, 0 insertions, 0 deletions