From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#22789: 25.1.50; In last master build https connections stop working Date: Tue, 01 Mar 2016 19:00:23 +0200 Message-ID: <83fuwa6sm0.fsf@gnu.org> References: <864mcyo14y.fsf@Lenovo-PC.i-did-not-set--mail-host-address--so-tickle-me> <871t81wtyt.fsf@gnus.org> <87r3g1veqc.fsf@gnus.org> <86si0euizj.fsf@realize.ch> <871t7xhj7t.fsf@gnus.org> <86oab1vjm9.fsf@realize.ch> <86d1rhpvcq.fsf@realize.ch> <834mctbitq.fsf@gnu.org> <868u25p3m2.fsf@realize.ch> <83io18ahya.fsf@gnu.org> <86y4a3on6f.fsf@realize.ch> <87oaazg7fv.fsf@gnus.org> <86twkro0vr.fsf@realize.ch> <83d1rf8ifj.fsf@gnu.org> <86povfnm9r.fsf@realize.ch> <8337sa9865.fsf@gnu.org> <87io16x1k5.fsf@gnus.org> <87d1recmnu.fsf@gnus.org> <86fuwanuku.fsf@realize.ch> <83wppm6vfb.fsf@gnu.org> <8637sanpcb.fsf@realize.ch> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1456851720 15117 80.91.229.3 (1 Mar 2016 17:02:00 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 1 Mar 2016 17:02:00 +0000 (UTC) Cc: schwab@suse.de, larsi@gnus.org, j_l_domenech@yahoo.com, 22789@debbugs.gnu.org To: Alain Schneble Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Tue Mar 01 18:01:48 2016 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aang8-00028k-R9 for geb-bug-gnu-emacs@m.gmane.org; Tue, 01 Mar 2016 18:01:44 +0100 Original-Received: from localhost ([::1]:51129 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aang8-0003R0-7p for geb-bug-gnu-emacs@m.gmane.org; Tue, 01 Mar 2016 12:01:44 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:39160) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aanfX-0002NH-TD for bug-gnu-emacs@gnu.org; Tue, 01 Mar 2016 12:01:11 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aanfS-00029i-6F for bug-gnu-emacs@gnu.org; Tue, 01 Mar 2016 12:01:07 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:59415) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aanfS-00029d-3x for bug-gnu-emacs@gnu.org; Tue, 01 Mar 2016 12:01:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84) (envelope-from ) id 1aanfR-000865-S5 for bug-gnu-emacs@gnu.org; Tue, 01 Mar 2016 12:01:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 01 Mar 2016 17:01:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 22789 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 22789-submit@debbugs.gnu.org id=B22789.145685164831099 (code B ref 22789); Tue, 01 Mar 2016 17:01:01 +0000 Original-Received: (at 22789) by debbugs.gnu.org; 1 Mar 2016 17:00:48 +0000 Original-Received: from localhost ([127.0.0.1]:56542 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84) (envelope-from ) id 1aanfE-00085X-05 for submit@debbugs.gnu.org; Tue, 01 Mar 2016 12:00:48 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:47923) by debbugs.gnu.org with esmtp (Exim 4.84) (envelope-from ) id 1aanf9-00085H-H3 for 22789@debbugs.gnu.org; Tue, 01 Mar 2016 12:00:46 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aanf0-00020d-T6 for 22789@debbugs.gnu.org; Tue, 01 Mar 2016 12:00:38 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:35996) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aanf0-00020Z-Qt; Tue, 01 Mar 2016 12:00:34 -0500 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:2257 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1aanf0-0004Zl-12; Tue, 01 Mar 2016 12:00:34 -0500 In-reply-to: <8637sanpcb.fsf@realize.ch> (message from Alain Schneble on Tue, 1 Mar 2016 17:19:00 +0100) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:114257 Archived-At: > From: Alain Schneble > CC: , , , > <22789@debbugs.gnu.org> > Date: Tue, 1 Mar 2016 17:19:00 +0100 > > >> But we could probably make use of it and it would not require the timer > >> at least for the async DNS resolution. It would not solve the TLS issue > >> though. But maybe there is a similar notification for async sockets > >> when they get connected? > > > > How do you envision we should make use of these notifications through > > signals? We try very hard not to do anything non-trivial in a signal > > handler, except setting a flag that is then tested in due time. If > > that is what you had in mind, then you will face the same problems > > with testing the flag as we face now: if the loop in > > wait_reading_process_output is stuck in a call to 'pselect' with a > > large timeout, Emacs might not be able to test the flag until the > > timeout ends. > > What you describe above is what I had thought of. Regarding large > timeout in pselect: isn't that what the sigmask to pselect is for? To > wait for a signal in addition to a file descriptor? Or am I > misunderstanding something? No, it's me: I forgot that a signal will interrupt 'pselect', which will return with EINTR, and that is already handled. So yes, if we have a signal that is delivered from one of these handshakes, it will cause the loop to run again.