From: "PAULUS, Raimund, TI-ABN" <Raimund.Paulus@dillinger.biz>
To: "'cygwin@cygwin.com'" <cygwin@cygwin.com>
Subject: Re: RPC clnt_create() adress already in use
Date: Tue, 06 Feb 2018 11:29:00 -0000 [thread overview]
Message-ID: <59D90AF8D70E9740907BACDE2BCB520836E4AA63@RESW102.resdom01.local> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 3326 bytes --]
Hello Corinna,
with the snapshot of cygwin1.dll and using bindresvport() from Cygwin for libtirpc (instead of the original bindresvport() from libtirpc) all my testcases work without error.
Many thanks
Raimund
-----Ursprüngliche Nachricht-----
Von: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com] Im Auftrag von Corinna Vinschen
Gesendet: Montag, 5. Februar 2018 21:15
An: cygwin@cygwin.com
Betreff: Re: RPC clnt_create() adress already in use
On Feb 5 15:06, Corinna Vinschen wrote:
> On Feb 5 14:34, Corinna Vinschen wrote:
> > On Feb 5 12:26, Corinna Vinschen wrote:
> > > To reiterate the problem we observe:
> > >
> > > - socket()
> > > - setsockopt (SO_REUSEADDR)
> > > - bind() succeeds
> > > - connect() fails with EADDRINUSE while socket is still in
> > > TIME_WAIT
> > >
> > > using bindresvport in place of bind only marginally changes the
> > > situation, in particular if the second parameter is set and
> > > requests a port number != 0. What happens in that case is that
> > > bindresvport calls bind with this port number and checks if bind returns EADDRINUSE.
> > >
> > > Only then it tries to bind other port numbers in the reserved range.
> > > But we now know that bind will never return EADDINUSE if the
> > > SO_REUSEADDR socket option has been set.
> > >
> > > Even assuming the process calls bindresvport(sock, NULL) we may
> > > end up returning a port number already in use if the process is
> > > the only Cygwin process on the system. The reason is that Cygwin
> > > uses a round robin approach which relies on having a globally
> > > shared value called last_used_bindresvport. If the process is the
> > > only Cygwin process on the system, this information is lost after
> > > exiting the process, so the next process will start with the same
> > > start port number and bind will again fail to notice the client with EADDRINUSE.
> > >
> > > What potential solutions to this problem do we have?
> > >
> > > - bindresvport could enforce SO_EXCLUSIVEADDRUSE temporarily to make
> > > sure bind fails.
> >
> > Nope, no way. Even enforcing SO_EXCLUSIVEADDRUSE results in the
> > second bind succeeding and the subsequent connect failing. The
> > entire SO_REUSEADDR/SO_EXCLUSIVEADDRUSE semantics only works as
> > desired on the server side apparently
> >
> > > - bindresvport could check every local address for being free prior
> > > to calling bind. However, there's a potential race here.
> > >
> > > - DisconnectEx? Never tried this Winsock extension but it might be
> > > worth a shot.
>
> I think I have a very simple solution for the scenario which calls
> bindresvport with port number. Still looking for a solution for the
> second problem...
I've pushed a few patches and uploaded new developer snapshots to https://cygwin.com/snapshots. Please give them a try.
Thanks,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
\x03BKCB\x1cØ\x19[H\x1c\^[Ü\x1cÎ\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0eËØÞYÝÚ[ÛÛKÜ\x1cØ\x19[\Ë\x1d^[[\x03BTN\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0eËØÞYÝÚ[ÛÛKÙ\KÃB^[ØÝ[Y[\x18]\x1a[Û\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0eËØÞYÝÚ[ÛÛKÙ^[ØÜË\x1d^[[\x03B[ÝXØÜXH\x1a[Î\b\b\b\b\b\x1a\x1d\x1d\x1c\x0eËØÞYÝÚ[ÛÛKÛ[\vÈÝ[ÝXØÜXK\Ú[\^[\x19CBB
next reply other threads:[~2018-02-06 11:29 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 11:29 PAULUS, Raimund, TI-ABN [this message]
2018-02-06 14:20 ` Corinna Vinschen
2018-02-07 6:54 ` Mark Geisert
-- strict thread matches above, loose matches on Subject: below --
2018-03-08 11:44 PAULUS, Raimund, TI-ABN
2018-03-08 15:24 ` Corinna Vinschen
2018-03-08 23:00 ` Mark Geisert
2018-03-02 10:39 PAULUS, Raimund, TI-ABN
2018-02-27 9:54 PAULUS, Raimund, TI-ABN
2018-02-27 10:37 ` Corinna Vinschen
2018-02-28 6:00 ` Mark Geisert
2018-02-05 14:58 PAULUS, Raimund, TI-ABN
2018-02-05 8:19 PAULUS, Raimund, TI-ABN
2018-02-05 10:29 ` Mark Geisert
2018-02-05 11:26 ` Corinna Vinschen
2018-02-05 13:34 ` Corinna Vinschen
2018-02-05 14:06 ` Corinna Vinschen
2018-02-05 20:15 ` Corinna Vinschen
2018-02-02 12:58 PAULUS, Raimund, TI-ABN
2018-01-30 10:07 PAULUS, Raimund, TI-ABN
2018-01-31 8:15 ` Mark Geisert
2018-01-31 9:11 ` Corinna Vinschen
2018-01-31 9:35 ` Mark Geisert
2018-02-02 8:11 ` Mark Geisert
2018-01-30 7:01 PAULUS, Raimund, TI-ABN
2018-01-30 9:05 ` Mark Geisert
2017-12-19 16:13 PAULUS, Raimund, TI-ABN
2017-12-28 0:03 ` Mark Geisert
2017-09-29 9:52 PAULUS, Raimund, TI-ABN
2017-09-29 17:36 ` Mark Geisert
2017-09-27 12:51 PAULUS, Raimund, TI-ABN
2017-09-25 6:44 PAULUS, Raimund, TI-ABN
2017-09-27 9:50 ` Mark Geisert
2017-09-22 7:22 PAULUS, Raimund, TI-ABN
2017-09-24 9:49 ` Mark Geisert
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=59D90AF8D70E9740907BACDE2BCB520836E4AA63@RESW102.resdom01.local \
--to=raimund.paulus@dillinger.biz \
--cc=cygwin@cygwin.com \
/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.
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).