From: Ken Brown <kbrown@cornell.edu>
To: cygwin-patches@cygwin.com
Subject: [PATCH 0/8] FIFO: bug fixes and small improvements
Date: Tue, 4 Aug 2020 08:54:59 -0400 [thread overview]
Message-ID: <20200804125507.8842-1-kbrown@cornell.edu> (raw)
The second patch in this series fixes a serious bug that has resulted
in observable hangs. The other patches are minor bug fixes or minor
performance improvements.
Ken Brown (8):
Cygwin: FIFO: lock fixes
Cygwin: FIFO: fix timing issue with owner change
Cygwin: FIFO: add a timeout to take_ownership
Cygwin: FIFO: reorganize some fifo_client_handler methods
Cygwin: FIFO: don't read from pipes that are closing
Cygwin: FIFO: synchronize the fifo_reader and fifosel threads
Cygwin: FIFO: fix indentation
Cygwin: FIFO: add a third pass to raw_read
winsup/cygwin/fhandler.h | 24 +--
winsup/cygwin/fhandler_fifo.cc | 358 ++++++++++++++++++++++-----------
winsup/cygwin/select.cc | 38 ++--
3 files changed, 268 insertions(+), 152 deletions(-)
--
2.28.0
next reply other threads:[~2020-08-04 12:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-04 12:54 Ken Brown [this message]
2020-08-04 12:55 ` [PATCH 1/8] Cygwin: FIFO: lock fixes Ken Brown
2020-08-04 12:55 ` [PATCH 2/8] Cygwin: FIFO: fix timing issue with owner change Ken Brown
2020-08-04 12:55 ` [PATCH 3/8] Cygwin: FIFO: add a timeout to take_ownership Ken Brown
2020-08-04 12:55 ` [PATCH 4/8] Cygwin: FIFO: reorganize some fifo_client_handler methods Ken Brown
2020-08-04 12:55 ` [PATCH 5/8] Cygwin: FIFO: don't read from pipes that are closing Ken Brown
2020-08-04 12:55 ` [PATCH 6/8] Cygwin: FIFO: synchronize the fifo_reader and fifosel threads Ken Brown
2020-08-04 12:55 ` [PATCH 7/8] Cygwin: FIFO: fix indentation Ken Brown
2020-08-04 12:55 ` [PATCH 8/8] Cygwin: FIFO: add a third pass to raw_read Ken Brown
2020-08-04 15:04 ` [PATCH 0/8] FIFO: bug fixes and small improvements Corinna Vinschen
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=20200804125507.8842-1-kbrown@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin-patches@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).