From: Eli Zaretskii <eliz@gnu.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: 49449@debbugs.gnu.org, larsi@gnus.org
Subject: bug#49449: 28: TLS connection never gets to "open" stage
Date: Sun, 11 Jul 2021 13:14:16 +0300 [thread overview]
Message-ID: <83eec5b1jb.fsf@gnu.org> (raw)
In-Reply-To: <23DD5CB6-5035-4C19-91B8-548F0B47E9FC@acm.org> (message from Mattias Engdegård on Sun, 11 Jul 2021 09:42:34 +0200)
> Feedback-ID:mattiase@acm.or
> From: Mattias Engdegård <mattiase@acm.org>
> Date: Sun, 11 Jul 2021 09:42:34 +0200
> Cc: larsi@gnus.org, 49449@debbugs.gnu.org
>
> 11 juli 2021 kl. 08.49 skrev Eli Zaretskii <eliz@gnu.org>:
>
> > why not reset the
> > NON_BLOCKING_CONNECT_FD bit before we call finish_after_tls_connection
> > from that place?
>
> That's tantamount to jamming a metal screwdriver into the condition on line 3277, which was indeed the first thing I tried. Unfortunately it doesn't work -- after the sentinel is called, no further progress is made, probably because we (by lying) haven't set up the connection properly.
Did you succeed in understanding what else has to happen before that
flag could be safely reset?
And anyway, if those conditions are not yet set, I wonder why are we
calling finish_after_tls_connection at that place?
next prev parent reply other threads:[~2021-07-11 10:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-06 19:12 bug#49449: 28: TLS connection never gets to "open" stage Mattias Engdegård
2021-07-07 19:57 ` Lars Ingebrigtsen
2021-07-08 7:59 ` Mattias Engdegård
2021-07-08 12:54 ` Lars Ingebrigtsen
2021-07-08 16:47 ` Mattias Engdegård
2021-07-10 16:27 ` Lars Ingebrigtsen
2021-07-10 16:51 ` Mattias Engdegård
2021-07-10 16:57 ` Lars Ingebrigtsen
2021-07-10 17:07 ` Mattias Engdegård
2021-07-10 18:23 ` Mattias Engdegård
2021-07-10 18:54 ` Eli Zaretskii
2021-07-10 19:22 ` Mattias Engdegård
2021-07-10 19:31 ` Eli Zaretskii
2021-07-10 19:44 ` Mattias Engdegård
2021-07-11 6:49 ` Eli Zaretskii
2021-07-11 7:42 ` Mattias Engdegård
2021-07-11 10:14 ` Eli Zaretskii [this message]
2021-07-11 14:26 ` Mattias Engdegård
2021-07-11 15:01 ` Eli Zaretskii
2021-07-12 14:57 ` Mattias Engdegård
2021-07-12 15:02 ` Lars Ingebrigtsen
2021-07-13 17:08 ` Mattias Engdegård
2021-07-10 20:05 ` Mattias Engdegård
2021-07-11 11:31 ` Lars Ingebrigtsen
2021-07-11 11:29 ` Lars Ingebrigtsen
2021-07-11 14:28 ` Mattias Engdegård
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83eec5b1jb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=49449@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=mattiase@acm.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).