X-Recipient: archive-cygwin AT delorie DOT com
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=aEUASDjPz3Sl2Smscv9sFzgF5c5md147k28n+eENnEE6z4egcaAY+
	gr0CUwm3C4J+oVJ0msV581E1bxtxjLE1t95WufTRhR34ehGhU0HOU9S7HYsMfLDj
	a2CIvpyCfaA4EObDg5vILEMlWNoGGkgyHxUclIhIAXficBk5Lwi1ho=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; 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; s=default;
	 bh=9VG9D5QNP+IF4w2wh5jxfkQpyt4=; b=vdw7qzLk/4J7ZTnPXeMdTOLW5IcJ
	dh+uwa2Jtk6ZrvJ+OqrlfA5HRDp0Xm338kcfw/h33I+DoJav8N04FymEpgQ3NAG/
	st97RWTPObNX9FGJ9VhC4hWy4uF6xZU+HkqkR4PKjmWpIRf477EZunK24ZV+hHlS
	szHjDeTuAWda8pI=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-5.4 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2
X-HELO: calimero.vinschen.de
Date: Sat, 28 Nov 2015 16:54:52 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: 64bit cygwin 2.4.0-0.4 hangs when pinging unresponsive host
Message-ID: <20151128155452.GY2755@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <01f501d12701$d5af6fb0$810e4f10$@vianet.ca> <5654E4E3 DOT 8050605 AT gmail DOT com> <56555DF4 DOT 9090804 AT towo DOT net> <56559566 DOT 7070808 AT gmail DOT com> <565621A3 DOT 3090706 AT gmail DOT com> <20151126201546 DOT GQ2755 AT calimero DOT vinschen DOT de> <20151127150737 DOT GA15906 AT calimero DOT vinschen DOT de> <56587B21 DOT 50002 AT gmail DOT com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="yypaS3FvPkEUiGyo"
Content-Disposition: inline
In-Reply-To: <56587B21.50002@gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)

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

On Nov 27 16:47, Marco Atzeri wrote:
> On 27/11/2015 16:07, Corinna Vinschen wrote:
> >>>>  64 $ ping 2.2.2.2
> >>>>PING 2.2.2.2 (2.2.2.2): 56 data bytes
> >>>>
> >>>>----2.2.2.2 PING Statistics----
> >>>>2 packets transmitted, 0 packets received, 100.0% packet loss
> >>>
> >>>
> >>>the problem seems restricted to the 64bit test version of cygwin.
> >>
> >>I think this is pure coincidence.  After some hours debugging this
> >>problem it seems it's a race condition, architecture-independent and
> >>present since quite a while in Cygwin.  In case of ping the race leads
> >>to a blocking socket function missing a signal arrived, thus the
> >>signal is never handled.  This in turn blocks the next signal from being
> >>delivered.
> >>
> >>I have a potential fix, but I have to test it a bit.  The signal code
> >>is pretty complicated...
> >
> >I created a new developer snapshot (https://cygwin.com/snapshots/) and
> >I'm just about writing the release message for the next test release
> >2.4.0-0.5 which both contain a patch for this problem.  Please give
> >any of them a try.
> >
> >
> >Thanks,
> >Corinna
> >
>=20
>=20
> It works fine for me

Good start.  Thanks for your feedback.


Corinna

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

--yypaS3FvPkEUiGyo
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJWWc5MAAoJEPU2Bp2uRE+gX9cQAJlQx5eIg3YpxoBRZdCusw/K
9JO2WphbClp9JmgXSJbDCyaRbdcDdDT1mAxVkzBrB6Tbw9JOriJ5K51uTygM3FsM
gviUKgxnjzJnkpDd+YEVkkmGmbocyX5zGBPbocf4nLY4h8H8tSDPssRPsuy3TT7a
5Uc2k+cvA1m6X60CAg1wIFFuROlH/5gYZezPjvpuTxyIsO7/1M+VRM/NRfX4MREs
S0FB0RIIA9rCS2ykKWUcjoAXxJnijwS32Up1DUeuIacqDPnNSMFQ9wClMs/eELkr
8YvGcaFWXAF2/F1xpKLX3oFbVBAxg2s5aPWHAgwNqwgzIcEHmldVtbiPjU3nulpU
jqAsC9T7eLO6IbL16xhnynKTTwDTn/8pzaquw+mze9eiL/o4/kDSKxMLKeHKy2ij
T285CEWN+uTMWhUwp6jWtSemuzvia4lQ2ipcAy6Aepca/W9+aNGbjmz1uOR7LUQD
zNOOFEkzDGcudsyR3OpUrvL/utapaUHZOoNgeH3RSiDpVScCJ4vCey9UndIjO5Cz
HKVjatiq73TivNQnVOIxBrp5UZ52WgP/Yg/SJ9IIOqL3Oe96ny3k1nxGmbd5dFII
13tyTpoiGOec+ObmoOnIYb0MMzKraW1WfAjGel6rNJOPo5d0lioOStGQQxU3VAg0
OpnvHTD1euTiPVtVLNGf
=fjhn
-----END PGP SIGNATURE-----

--yypaS3FvPkEUiGyo--