From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 124557 invoked by alias); 11 Jun 2019 08:52:34 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 124457 invoked by uid 89); 11 Jun 2019 08:52:34 -0000 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 Received: from mout.kundenserver.de (HELO mout.kundenserver.de) (212.227.17.24) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 11 Jun 2019 08:52:33 +0000 Received: from calimero.vinschen.de ([24.134.7.25]) by mrelayeu.kundenserver.de (mreue108 [212.227.15.183]) with ESMTPSA (Nemesis) id 1MN5aF-1hHa3n0QOD-00IykZ; Tue, 11 Jun 2019 10:52:22 +0200 Received: by calimero.vinschen.de (Postfix, from userid 500) id 2C0B8A8071D; Tue, 11 Jun 2019 10:52:21 +0200 (CEST) Date: Tue, 11 Jun 2019 08:52:00 -0000 From: Corinna Vinschen To: cygwin@cygwin.com, Ken Brown Subject: Re: timerfd deadlock Message-ID: <20190611085221.GC3520@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com, Ken Brown References: <17657e77-6d7c-7367-3e6f-54e2586ed40c@cornell.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) X-SW-Source: 2019-06/txt/msg00123.txt.bz2 --tsOsTdHNUZQcU9Ye Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-length: 567 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" Content-length: 833 -----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--