Handle the case where the read buffer is empty but we have received FIN
authorMatt Caswell <matt@openssl.org>
Fri, 18 Aug 2023 14:57:41 +0000 (15:57 +0100)
committerTomas Mraz <tomas@openssl.org>
Sun, 20 Aug 2023 11:28:33 +0000 (13:28 +0200)
commit72622c0b9637667cfef3692e5a63b90d637f0c72
treea6fe2103c514f4dda6e915e15e327f299d4dcd0f
parentd561fe5a0aabb4d0a9400b5086441bb4f4b4dca4
Handle the case where the read buffer is empty but we have received FIN

In some cases where a FIN has been received but with no data quic_read_actual
was failing to raise SSL_ERROR_ZERO_RETURN. This meant that we could end up
blocking in SSL_read(_ex) for too long.

Reviewed-by: Hugo Landau <hlandau@openssl.org>
Reviewed-by: Tomas Mraz <tomas@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/21780)
ssl/quic/quic_impl.c