X-Recipient: archive-cygwin@delorie.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:from:to:subject:date:message-id:content-type
	:content-id:content-transfer-encoding:mime-version; q=dns; s=
	default; b=nn6LyWMtB7hVYvlwCgSf0Y3Gbz4+8UnhG+Q0Fsa/v30p1hnppcs+3
	ElqWvSDe59E1+jSNlQe4KNtGV6JbeV/lFO9MW16zoWFvf7BkHvZdTPDtWjhcKYlC
	sk6ffZ2z2BwtGK3Ua6wGruyRUd9Nt+bGIG1TQZ03TS/rI0z8INHyP0=
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:from:to:subject:date:message-id:content-type
	:content-id:content-transfer-encoding:mime-version; s=default;
	 bh=DsdSfMNnVHQI7Htrs60w2ZelLbM=; b=T4BgKsgUi/UEOfHbBkDLg1Bxw8hk
	ZUvKHKCYGZBOwBCZdUrsE6jiX2bu0vPKdVPRAGSD0gO/dF4onEyeiLg/mmSo0tSG
	FdnO3SYlsYA0QE4KaKc3jhCJpv55DaOppUoJvE3OO6W66Y8V4oWFCrfFzSWZ1FkQ
	tsUF7nDejl6kBLU=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-10.3 required=5.0 tests=AWL,BAYES_00,MIME_BASE64_BLANKS,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.1 spammy=HX-Languages-Length:588, held
X-HELO: NAM02-SN1-obe.outbound.protection.outlook.com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cornell.edu; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=iaurGW4bukUyjIpHsubdyLiiuRDxChKz6EfbuvFAiEU=; b=gHcTKCErLOFP6Doq0OcddtYTi7iQGVm0D6QYDRve1vh/achtzVk5U7QUmQlKeMyTfUGxsMormZrI50KhAlvTAoA6A8w/BCPzDgJXviRazALWq0asTwOOI/aPEQ2EECC3hGbK2ev4V4jmRILILEZYiArhG1/G2066ub48tEH1wdI=
From: Ken Brown <kbrown@cornell.edu>
To: cygwin <cygwin@cygwin.com>
Subject: timerfd deadlock
Date: Fri, 7 Jun 2019 12:10:17 +0000
Message-ID: <17657e77-6d7c-7367-3e6f-54e2586ed40c@cornell.edu>
user-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0
authentication-results: spf=none (sender IP is ) smtp.mailfrom=kbrown@cornell.edu;
x-ms-oob-tlc-oobclassifiers: OLM:8882;
received-spf: None (protection.outlook.com: cornell.edu does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
Content-Type: text/plain; charset="utf-8"
Content-ID: <768F357F139A254B836D3C7AFCAA1202@namprd04.prod.outlook.com>
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: ksb2@cornell.edu
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id x57CAuwJ021907

While testing some new pipe code, I'm occasionally seeing a timerfd deadlock: 
The main thread is stuck in timerfd_tracker::dtor at timerfd.cc:354, waiting for 
the timerfd thread to close; and the timerfd thread is stuck at timerfd.cc:140, 
waiting to acquire a mutex that's held by timerfd_tracker::dtor.

I see this maybe 1 out of 4 times that I run 'make -j13' on a clean emacs source 
tree, and I see it only when my new pipe code is installed.  So I don't know if 
this is a bug in my code or if it's just coincidence that my code happens to 
trigger a timerfd bug.

Ken

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple


