From: Ken Brown <kbrown@cornell.edu>
To: cygwin-patches@cygwin.com
Subject: Re: [PATCH v2 0/6] Some AF_UNIX fixes
Date: Wed, 14 Oct 2020 12:39:00 -0400 [thread overview]
Message-ID: <ea3b1e6a-8857-cd1f-349d-6fc64c2d1b77@cornell.edu> (raw)
In-Reply-To: <20201013114933.GJ26704@calimero.vinschen.de>
On 10/13/2020 7:49 AM, Corinna Vinschen wrote:
> On Oct 8 17:36, Ken Brown via Cygwin-patches wrote:
>> On 10/4/2020 12:49 PM, Ken Brown via Cygwin-patches wrote:
>>> I'm about to push these. Corinna, please check them when you return.
>>> The only difference between v2 and v1 is that there are a few more
>>> fixes.
>>>
>>> I'm trying to help get the AF_UNIX development going again. I'm
>>> mostly working on the topic/af_unix branch. But when I find bugs that
>>> exist on master, I'll push those to master and then merge master to
>>> topic/af_unix.
>>
>> FYI to Corinna and anyone else interested in AF_UNIX development. After
>> pushing a few patches to the topic/af_unix branch I did some cleanup
>> (locally) and merged master into the topic branch. I don't want to do a
>> forced push and risk messing up the branch, so I've created a new branch,
>> topic/af_unix_new, and will do all further work there until Corinna returns
>> and decides how we should proceed.
>
> No, that's ok, just force push.
OK, I've done that now. The branch contains a few sendmsg fixes, a first cut of
a recvmsg implementation, and a merge from master. I've done some testing of
recvmsg, but many things are not yet tested. I'll work on continued testing next.
Are you aware of any test suite that I could run? I've been using examples from
Kerrisk's book, because that's what I read to learn the basics of sockets. But
those are just examples and are not meant to be comprehensive.
Ken
next prev parent reply other threads:[~2020-10-14 16:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-04 16:49 Ken Brown
2020-10-04 16:49 ` [PATCH v2 1/6] Cygwin: AF_UNIX: use FILE_OPEN_REPARSE_POINT when needed Ken Brown
2020-10-04 16:49 ` [PATCH v2 2/6] Cygwin: fix handling of known reparse points that are not symlinks Ken Brown
2020-10-04 16:49 ` [PATCH v2 3/6] Cygwin: always recognize AF_UNIX sockets as reparse points Ken Brown
2020-10-04 16:49 ` [PATCH v2 4/6] Cygwin: AF_UNIX: socket: set the O_RDWR flag Ken Brown
2020-10-04 16:49 ` [PATCH v2 5/6] Cygwin: AF_UNIX: listen_pipe: check for STATUS_SUCCESS Ken Brown
2020-10-13 11:28 ` Corinna Vinschen
2020-10-13 13:18 ` Ken Brown
2020-10-13 15:31 ` Corinna Vinschen
2020-10-04 16:49 ` [PATCH v2 6/6] Cygwin: AF_UNIX: open_pipe: call recv_peer_info Ken Brown
2020-10-08 21:36 ` [PATCH v2 0/6] Some AF_UNIX fixes Ken Brown
2020-10-13 11:49 ` Corinna Vinschen
2020-10-14 16:39 ` Ken Brown [this message]
2020-10-15 4:19 ` Mark Geisert
2020-10-15 5:48 ` Brian Inglis
2020-10-15 8:16 ` Corinna Vinschen
2020-10-13 11:02 ` 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=ea3b1e6a-8857-cd1f-349d-6fc64c2d1b77@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).