From: Bill Zissimopoulos <billziss@navimatics.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: FUSE, symbolic links and special files
Date: Fri, 26 Aug 2016 14:35:00 -0000 [thread overview]
Message-ID: <D3E62581.AFDD%billziss@navimatics.com> (raw)
In-Reply-To: <20160826080551.GA23935@calimero.vinschen.de>
On 8/26/16, 11:05 AM, Corinna Vinschen wrote:
>On Aug 25 19:04, Bill Zissimopoulos wrote:
>>- The first case is during the processing of NtCreateFile (without the
>> FILE_OPEN_REPARSE_POINT flag set).
>
>This case doesn't matter to us. Cygwin always opens the file with
>FILE_OPEN_REPARSE_POINT set...
>
>> - The second case is through direct manipulation of the reparse point
>> using FSCTL_GET_REPARSE_POINT, FSCTL_SET_REPARSE_POINT and
>> FSCTL_DELETE_REPARSE_POINT.
>>
>> Let us consider the expected behavior of an NFS_SPECFILE_LNK reparse
>>point
>> (this is speculation) during NtCreateFile:
>>
>> - On NTFS prior to Win8:
>> - STATUS_IO_REPARSE_TAG_NOT_HANDLED
>
>...so this shouldn't happen to us, right?
I think so.
I will continue with the implementation/testing of reparse points and
report back when I have more.
Bill
next prev parent reply other threads:[~2016-08-26 13:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 12:49 Bill Zissimopoulos
2016-08-25 13:04 ` Corinna Vinschen
2016-08-25 13:38 ` Jeffrey Altman
2016-08-25 13:54 ` Corinna Vinschen
2016-08-25 14:52 ` Jeffrey Altman
2016-08-25 15:59 ` Corinna Vinschen
2016-08-25 19:04 ` Jeffrey Altman
2016-08-25 19:41 ` Bill Zissimopoulos
2016-08-25 21:15 ` Bill Zissimopoulos
2016-08-25 19:15 ` Bill Zissimopoulos
2016-08-26 10:25 ` Corinna Vinschen
2016-08-26 14:35 ` Bill Zissimopoulos [this message]
2016-09-20 22:02 ` Bill Zissimopoulos
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=D3E62581.AFDD%billziss@navimatics.com \
--to=billziss@navimatics.com \
--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).