public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: accept: Bad address
Date: Wed, 04 Apr 2018 09:25:00 -0000	[thread overview]
Message-ID: <20180404092530.GM2833@calimero.vinschen.de> (raw)
In-Reply-To: <641856e3-338d-72b7-194b-da6073bf2c5f@maxrnd.com>

[-- Attachment #1: Type: text/plain, Size: 1582 bytes --]

On Apr  3 22:59, Mark Geisert wrote:
> Ilguiz Latypov via cygwin wrote:
> > Hello,
> > 
> > The latest Cygwin 64-bit release with the snapshot cygwin1.dll copied on top of it shows an "accept: Bad address error" in 3 reproducible cases:
> > 
> > (a) The sshd daemon on receiving a connection request.
> > (b) The XWin server on receiving a connection request from an X11 client such as xterm.
> > (c) The Python server receiving a TCP connection in the socket's accept().
> 
> That is likely a different problem with similar symptoms.
> 
> > A StackOverflow question 41018644 from December 2016 showed an example of the bug with the Python server (c).
> 
> There seems to have been a brief period of time in March where accept() was
> not working properly.  There was one report on the list (from Denis
> Excoffier) and at the same time it wasn't working for me, also using X, on a
> personal build of the Cygwin DLL from git source.  Denis later reported it
> working again, and I can confirm it is working again for me.

I reshuffled lots of socket code to make room for a new AF_UNIX
implementation.  While at it, I screwed up in a few places, so
socket code was broken for a bit.  The OpenSSH testsuite helped
a lot to find the bugs, btw :}

> Corinna or somebody else with the chops/access, could we get a new Cygwin
> DLL snapshot built when you have a chance?

New snapshots are up.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2018-04-04  9:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1342436895.1365392.1522798965341.ref@mail.yahoo.com>
2018-04-03 23:42 ` Ilguiz Latypov via cygwin
2018-04-04  5:59   ` Mark Geisert
2018-04-04  6:36     ` Mark Geisert
2018-04-04  9:25     ` Corinna Vinschen [this message]
2018-04-05  0:52       ` Ilguiz Latypov via cygwin

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=20180404092530.GM2833@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --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).