From: Ken Brown <kbrown@cornell.edu>
To: cygwin-devel <cygwin-developers@cygwin.com>
Subject: AF_UNIX status report
Date: Mon, 26 Oct 2020 18:04:31 -0400 [thread overview]
Message-ID: <1d0ea5dc-7e9b-d8fe-5f6e-da7a799a3b13@cornell.edu> (raw)
I've made at least rudimentary implementations of all the fhandler_socket_unix
functions (including those in select.cc) for which there were previously only
placeholders.
I've pushed everything to topic/af_unix, including a merge with master as of a
couple days ago.
I've cobbled together a few test programs and put them in
winsup/cygwin/socket_tests on the topic/af_unix branch. I haven't taken the
time to automate the tests, so they all have to be run interactively. There is
a Makefile to build the test programs and a README.txt that shows how to run them.
One thing I haven't yet done is to think about (or systematically test) datagram
sockets. I'm sure there's quite a bit of code that won't work for them.
Aside from datagram sockets, there are still a few things that I'm working on,
but I'm close to the point where I could use some input:
1. I've littered the code in fhandler_socket_unix.cc and select.cc with FIXME
comments on which I'd like advice.
2. I haven't given any thought at all as to how to implement SCM_RIGHTS
ancillary data. I could definitely use suggestions on that before I start
thrashing around.
Ken
next reply other threads:[~2020-10-26 22:04 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 22:04 Ken Brown [this message]
2020-10-27 9:43 ` Corinna Vinschen
2020-10-29 20:19 ` Ken Brown
2020-10-29 21:53 ` Joe Lowe
2020-10-30 9:20 ` Corinna Vinschen
2020-11-03 15:43 ` Ken Brown
2020-11-04 12:03 ` Corinna Vinschen
2020-11-05 14:23 ` Ken Brown
2020-11-05 17:21 ` Corinna Vinschen
2020-11-05 19:01 ` Ken Brown
2020-11-05 19:54 ` Joe Lowe
2020-11-06 4:02 ` Ken Brown
2020-11-05 23:41 ` Ken Brown
2020-11-06 9:12 ` Corinna Vinschen
2020-11-07 22:25 ` Ken Brown
2020-11-08 22:40 ` Ken Brown
2020-11-09 9:08 ` Corinna Vinschen
2020-11-17 19:57 ` Ken Brown
2020-11-18 8:34 ` Corinna Vinschen
2020-11-22 20:44 ` Ken Brown
2020-11-23 8:43 ` Corinna Vinschen
2020-11-26 17:06 ` Ken Brown
2020-12-15 17:33 ` Ken Brown
2020-12-16 9:29 ` Corinna Vinschen
2020-12-16 21:09 ` Ken Brown
2020-12-17 15:54 ` Ken Brown
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=1d0ea5dc-7e9b-d8fe-5f6e-da7a799a3b13@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin-developers@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).