This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: timerfd deadlock

From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
To: cygwin at cygwin dot com, Ken Brown <kbrown at cornell dot edu>
Date: Tue, 11 Jun 2019 10:52:21 +0200
Subject: Re: timerfd deadlock
References: <17657e77-6d7c-7367-3e6f-54e2586ed40c@cornell.edu>
Reply-to: cygwin at cygwin dot com

On Jun  7 12:10, Ken Brown wrote:
> 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.

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

-- 
Corinna Vinschen
Cygwin Maintainer

Attachment: signature.asc
Description: PGP signature

Follow-Ups:
- Re: timerfd deadlock
  - From: Ken Brown
- Re: timerfd deadlock
  - From: Ken Brown

References:
- timerfd deadlock
  - From: Ken Brown

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]