public inbox for
 help / color / mirror / Atom feed
From: Ken Brown <>
Subject: [PATCH 1/1] Cygwin: recognize native Windows AF_UNIX sockets as reparse points
Date: Sat, 30 Jan 2021 11:34:36 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Allow check_reparse_point_target to recognize reparse points with
reparse tag IO_REPARSE_TAG_AF_UNIX.  These are used in recent versions
of Windows 10 to represent AF_UNIX sockets.

check_reparse_point_target now returns PATH_REP on files of this type,
so that they are treated as known reparse points (but not as sockets).
This allows tools like 'rm', 'ls', etc. to operate on these files.

 winsup/cygwin/ | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/winsup/cygwin/ b/winsup/cygwin/
index 6dc162806..9d2184d6a 100644
--- a/winsup/cygwin/
+++ b/winsup/cygwin/
@@ -2640,6 +2640,10 @@ check_reparse_point_target (HANDLE h, bool remote, PREPARSE_DATA_BUFFER rp,
         return PATH_REP | PATH_REP_NOAPI;
+  else if (rp->ReparseTag == IO_REPARSE_TAG_AF_UNIX)
+    /* Native Windows AF_UNIX socket; recognize this as a reparse
+       point but not as a socket. */
+    return PATH_REP;
   return 0;

  reply	other threads:[~2021-01-30 16:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-30 16:34 [PATCH 0/1] Recognizing native Windows AF_UNIX sockets Ken Brown
2021-01-30 16:34 ` Ken Brown [this message]
2021-01-30 20:58 ` Ken Brown
2021-02-01  9:54 ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).