Re: [Libevent-users] Re: Avoid potential SSL read spinlocks

[Mark Ellzey <mthomas@xxxxxxxxxx>]

On Tue, Nov 15, 2011 at 10:48:10AM -0600, Mark Ellzey wrote:
> On Mon, Nov 14, 2011 at 07:21:00PM -0600, Mark Ellzey wrote:
> > On Mon, Nov 14, 2011 at 07:13:39PM -0600, Mark Ellzey wrote:
> > > 
> > > We cannot schedule or call the readcb UNTIL SSL_read() returns > 0 OR an
> > > error occurs on the socket.
> > 
> > I definitely feel confident this is the issue, going into that loop
> > provided ample time for SSL_read() to process an entire record.  
> 
> 
> 
> I retract this. After looking at it more, it does the right thing. And
> bevssl does work without deferred. I use it all the time. Is your
> application threaded?


Also, would be nice to have some code that reproduces the issue you are
having.
***********************************************************************
To unsubscribe, send an e-mail to majordomo@xxxxxxxxxxxxx with
unsubscribe libevent-users    in the body.