[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [Libevent-users] SSL problems after update to libeven 2.1.8
- To: libevent-users@xxxxxxxxxxxxx
- Subject: Re: [Libevent-users] SSL problems after update to libeven 2.1.8
- From: Azat Khuzhin <a3at.mail@xxxxxxxxx>
- Date: Wed, 3 Oct 2018 08:38:20 +0300
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: libevent-users-outgoing@xxxxxxxx
- Delivered-to: libevent-users@xxxxxxxx
- Delivery-date: Wed, 03 Oct 2018 01:38:26 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=9mRECtFyW3IH2o1nTDpaVzbmIcqaPhi5rYkj5MsCGo4=; b=ncsz22YvsGUfRHOjkTvn5o/ZQ2BhJoMV/PLMkAeEyDkjfnuEKgZEVpn16oBCPjRwZ8 kQh35/noJ0O9SEc63DHy2cRS/UcW/mAKkEzhBT3qcE39fuL0Ekd79xmXIkMiFWigYxOF d6ib2B3QnppQMM8uNokVOKfM8Zdws2sLEy41YfoxyEja+l4qqysTV+ZKnBQsEHGRLIWt XvyOlGFAPTJc0skvQj60XVNoPM1RQ/4fs3P0t4F+M+kREe5s2BdBAxzS+s1brIzhtu03 L7WOmOfD6iKQMF4ncp2iH4pS9m0Dg5fnARI946a7dC/obkD6mAfHWcB1IHbV4efsablb v9qw==
- In-reply-to: <2C8B365E-EC1B-493D-9B2C-CBE7982C3CC0@mesosphere.io>
- References: <7549CDE3-675F-4EC0-8D7E-051ED2FCEB63@mesosphere.io> <20180909231314.jeeunh6q3jcauaqf@carbon.azat.localdomain> <04EC0810-99DC-4FB5-9335-230F132FC5EC@mesosphere.io> <F9C52CF1-1F73-42B9-829A-67A95A4AB9F6@mesosphere.io> <20180910100222.hbga3e3ete4fq7vd@carbon.azat.localdomain> <85F8645F-6176-4A09-9A0A-E49F32963E00@mesosphere.io> <20180930215205.rjhn3eulodgev4vl@macbook-pro.sq.azat.localdomain> <61760B94-46F0-456E-B766-07DE14F2EB33@mesosphere.io> <20181002215404.4nv243lmachlyi3u@carbon.azat.localdomain> <2C8B365E-EC1B-493D-9B2C-CBE7982C3CC0@mesosphere.io>
- Reply-to: libevent-users@xxxxxxxxxxxxx
- Sender: owner-libevent-users@xxxxxxxxxxxxx
- User-agent: NeoMutt/20180716
> Note that I moved the setup of EV_READ | EV_WRITE setup a bit further up on the connect part. I was worried that without doing so, we could possibly run into races caused by data being available early. This would be matching our callback setup timing.
Does event_base_loop() and
bufferevent_socket_connect()/bufferevent_enable() runs in different
threads? If so this can be true.
But this will not break anything, since they will be read after, that's
it. IOW both patches is fine.
--
Azat.
***********************************************************************
To unsubscribe, send an e-mail to majordomo@xxxxxxxxxxxxx with
unsubscribe libevent-users in the body.