From: Ken Brown <kbrown@cornell.edu>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: timerfd deadlock
Date: Mon, 24 Jun 2019 20:16:00 -0000 [thread overview]
Message-ID: <c4d32d35-a668-bca9-f783-bc5ee09ba4ff@cornell.edu> (raw)
In-Reply-To: <20190611085221.GC3520@calimero.vinschen.de>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1240 bytes --]
On 6/11/2019 4:52 AM, Corinna Vinschen wrote:
> 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?
I haven't been able to create an STC. The deadlock seems to depend on a rare
timing fluke, and I've only seen it when running a parallel make on a clean
emacs tree, with my new pipe code installed.
On the other hand, I think I have a simple fix, which I'll send to
cygwin-patches. With this patch, I ran the parallel make 15 times without
getting the deadlock. After reverting the patch, I got the deadlock on the 4th run.
Ken
\0ТÒÐÐ¥\a&ö&ÆVÒ\a&W\x06÷'G3¢\x02\x02\x02\x02\x02\x02\x06GG\x03¢òö7wvâæ6öÒ÷\a&ö&ÆV×2æFÖÀФd\x15\x13¢\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x06GG\x03¢òö7wvâæ6öÒöf\x17\x12ðФFö7VÖVçF\x17Föã¢\x02\x02\x02\x02\x02\x02\x02\x02\x06GG\x03¢òö7wvâæ6öÒöFö72æFÖÀÐ¥Vç7V'67&&R\x06æfó¢\x02\x02\x02\x02\x02\x06GG\x03¢òö7wvâæ6öÒöÖÂò7Vç7V'67&&R×6×\x06ÆPÐ Ð
prev parent reply other threads:[~2019-06-24 20:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-07 12:10 Ken Brown
2019-06-11 8:52 ` Corinna Vinschen
2019-06-11 13:18 ` Ken Brown
2019-06-24 20:16 ` Ken Brown [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c4d32d35-a668-bca9-f783-bc5ee09ba4ff@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).