General support for reparse points which are not named surrogates #5565
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
According to the docs[1], and given our experience with reparse point
resolution for
realpath()
, it seems to be safe to assume that allreparse points, which are not named surrogates, are not aliased, so
their absolute paths are their real paths. By doing so, we support
arbitrary third party on-demand file systems out of the box, without
the need to eventually add support for individual reparse tags.
[1] https://docs.microsoft.com/en-us/windows/win32/api/winnt/nf-winnt-isreparsetagnamesurrogate