On Mon, Feb 24, 2020 at 4:49 PM Thomas Munro <thomas.munro@gmail.com> wrote:
> While working on a patch to reuse a common WaitEventSet for latch
> waits, I noticed that be-secure-gssapi.c and be-secure-openssl.c don't
> use FeBeWaitSet. They probably should, for consistency with
> be-secure.c, because that surely holds the socket they want, no?
Hmm. Perhaps it's like that because they're ignoring their latch
(though they pass it in just because that interface requires it). So
then why not reset it and process read interrupts, like be-secure.c?
