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=oHhmfXeK5u8H7VWv3RMEib36UsKWK/MuUUHQcj1O2al9U7d71junx
	Ym0YjlokKnG/M7QKfDKpsEO9nuZxuKh03ORnTHiXhmv7/9XbYcfXYGPv3hXrsZXE
	a/WYNCcVMN/idCxfiSlz8OlOcEfQrr21ZPBEDA8rNflhdmBbdoppvs=
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=o2JfpyrnD0fjZ6fqB0lBaMeEScI=; b=kGBOZF8de/pNB/oiKIohgoqTVMjX
	iO/czEtgFO/EC7pKVbYTx2I+APEN5ocnJPz0Jywz1n9SOjtiw1Km5IPMbXKLon9B
	vooJucX7D6c486StfcCiyK9h5A4XiDQ53Fu3j9czHmvhdWlIBDOoAZrJUIMy2R/C
	Y4rvHKw5fyfGcfs=
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-Spam-SWARE-Status: No, score=-102.6 required=5.0 tests=AWL,BAYES_00,GOOD_FROM_CORINNA_CYGWIN,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 spammy=HX-Languages-Length:569, H*F:D*cygwin.com, held
X-HELO: mout.kundenserver.de
Date: Tue, 11 Jun 2019 10:52:21 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com, Ken Brown <kbrown AT cornell DOT edu>
Subject: Re: timerfd deadlock
Message-ID: <20190611085221.GC3520@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com, Ken Brown <kbrown AT cornell DOT edu>
References: <17657e77-6d7c-7367-3e6f-54e2586ed40c AT cornell DOT edu>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="tsOsTdHNUZQcU9Ye"
Content-Disposition: inline
In-Reply-To: <17657e77-6d7c-7367-3e6f-54e2586ed40c@cornell.edu>
User-Agent: Mutt/1.11.3 (2019-02-01)

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

On Jun  7 12:10, Ken Brown wrote:
> While testing some new pipe code, I'm occasionally seeing a timerfd deadl=
ock:=20
> The main thread is stuck in timerfd_tracker::dtor at timerfd.cc:354, wait=
ing for=20
> the timerfd thread to close; and the timerfd thread is stuck at timerfd.c=
c:140,=20
> waiting to acquire a mutex that's held by timerfd_tracker::dtor.

Hmm, I had hoped my current code does not have a deadlock situation
anymore, but I was wrong, apparently.

Is there any chance to create an STC?


Thanks,
Corinna

--=20
Corinna Vinschen
Cygwin Maintainer

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

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

iQIzBAEBCAAdFiEEoVYPmneWZnwT6kwF9TYGna5ET6AFAlz/a8UACgkQ9TYGna5E
T6DGjhAAiE6ETL4LiUjOlRvUfJuSNgMlN19eXTZZKbyz+nBqbNYw2K4xra5p1JP5
7VIpLZMU34sFQkVCGW54wEQsr6bsd1KiXcPOV53ZD9H7Kqr/x/db0Ix1JJ0J2UEU
Wfs+t4D/vpInAp9N8D7PeFgbWkyXARQ4S66NL9q0304951WFK1tAdSLk7IJ/TCja
Vq+RhAcEWpDA55H7NSJADhDG/zEvesnuRSnm5J78LyuIOlG9mIG6nQqZ32Xc0/4M
XiAoBdJtk1imiHh1ie/ijThsKOn/ohUqUlFjJjFuF36tgRSIqy2RxKtHchMorTSP
lBXyhGEm2mV4BqJS/yWNr09/Buj1A1Y2ApE9qkgLVyMRkG8CJ9N3QL3DtZ5BPJ5h
ba9paSkBXR1VaolpfQt3nXsLPN8YaWxGZ7tQWNRm3caVf77wiBs5Ev0Td5Au3mmW
nipbjidSeEQHslpGwQN/VokiQDmWxaYxQngCZfrWNHDmf54J0OZte2Pk4ih40nMR
sKj5MQ0jJh8XPAmSWme+fY/RvA0DdnAUyskD+yBEiDka7qQo48aAVDDnkeRrnmIu
GC7zmHlTVbcc88DbUqElXpdyKBL1mGMTqcf7BzMeYa5mz1s04HtNyMu1SnXu/OZS
8pTFKE+80+zlTSKMSE26Y2mUTUxWmgPEiHiYowzsLlQuftoB+TQ=
=uBM5
-----END PGP SIGNATURE-----

--tsOsTdHNUZQcU9Ye--