DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=EWGxO08hQeLL8IRbw8pkvE92Mbc/TuXTQrn+tzg44rRBp945tu3cp
	tcYjTxVOqt6s+FHBbBV2GE7s/n+sH7YREK6fxjnGvDSc8+bp9Zxj5fXE9SjLRG6P
	A0l+cqk1+U+2mwn8grP6tD6+I31OeDyj4RwzT3diQI00ZsZvEm0BI4=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Wed, 4 Apr 2018 11:25:30 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: accept: Bad address
Message-ID: <20180404092530.GM2833@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <1342436895 DOT 1365392 DOT 1522798965341 DOT ref AT mail DOT yahoo DOT com> <1342436895 DOT 1365392 DOT 1522798965341 AT mail DOT yahoo DOT com> <641856e3-338d-72b7-194b-da6073bf2c5f AT maxrnd DOT com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="4Epv4kl9IRBfg3rk"
Content-Disposition: inline
In-Reply-To: <641856e3-338d-72b7-194b-da6073bf2c5f@maxrnd.com>
User-Agent: Mutt/1.9.2 (2017-12-15)

--4Epv4kl9IRBfg3rk
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Apr  3 22:59, Mark Geisert wrote:
> Ilguiz Latypov via cygwin wrote:
> > Hello,
> >=20
> > The latest Cygwin 64-bit release with the snapshot cygwin1.dll copied o=
n top of it shows an "accept: Bad address error" in 3 reproducible cases:
> >=20
> > (a) The sshd daemon on receiving a connection request.
> > (b) The XWin server on receiving a connection request from an X11 clien=
t such as xterm.
> > (c) The Python server receiving a TCP connection in the socket's accept=
().
>=20
> That is likely a different problem with similar symptoms.
>=20
> > A StackOverflow question 41018644 from December 2016 showed an example =
of the bug with the Python server (c).
>=20
> There seems to have been a brief period of time in March where accept() w=
as
> 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, o=
n 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

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

--4Epv4kl9IRBfg3rk
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEoVYPmneWZnwT6kwF9TYGna5ET6AFAlrEmgoACgkQ9TYGna5E
T6BDYxAAmEcbjGIQ+/3gYf+5QQ1/L3lsfMCcU29bg52vXmIx3PNalXwrowbl59xd
yoPKCBj1/qsS0et5fMG/jywY/5pl12pCimtAF43iMKY+I+0SrPQ0F0EOQHUeVzo1
6kOIHrykxkssCFnewdJ0C1nQxlOY2ly1tZiU7hDfm6kFWIRmWzesjWS8Kw5uOAFA
plwIl5/7EFs4jiVgnfyLptIyFT4YHn146oWOWIk2f4ON1zFtwFmGaBjX9PJ3b8PB
JQlbtI4cpPBPowGU83/QERI+5pBPawTYNTiDU8//yeHSwvBr6eNKucnjxvMgA45V
DqiN9yabmjoFeDvST1fe8VYjYIDHCUVLmWWYc9FKMMvdzU6x8+WkUyLT2bGyQL+u
g7KlRCPZCOVpQE9mg1MxM0P+/14M8NI9yxezLct/TYKV6l9SZ+ijK0dxVA1KsLvE
7XBUDWwJcePa0/jnTsnDKfpagSVmpcz/3WkRa8c3xvMF7w84be2oVPwvenggJLAk
SX3KzCOSQtHwklkVUN6IJUaXOF9US07izMymSTUw0gS9eo28PlEYoFSXi9dLHq1P
NBP7dXEsjjLaegYBOaiBtrgoq79+ojfk2/xjc/3EF6IKe3O6ph6GJ7U7cTlYePr5
tLyYMnp76JjDKr69gnglcJE1z+TCviPXIl4EqDQBx+kf66Z9Nbo=
=ysU2
-----END PGP SIGNATURE-----

--4Epv4kl9IRBfg3rk--