-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
std.os.windows: add error.UnrecognizedVolume #18952
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For context, the dilemma is:
..
components..
components trivially (this is whatnormalizePath
/removeDotDirsSanitized
does)../../foo
, it needs to be resolved into an absolute path and given the NT namespace prefix (\??\
)RtlGetFullPathName_U
can handle the case when resolving a path like../../foo
against the cwd, but not against an arbitrary directory handleGetFinalPathNameByHandle
implementation in the case where we (1) can't trivially remove..
components and (2) need to resolve the path against a non-CWD dirEDIT: So one possibility here is that there's some way to handle a path like
../../foo
without needing to resolve it into an absolute path. The other is that this is a bug in ourGetFinalPathNameByHandle
implementation rather thanwToPrefixedFileW
(that is, we're not able to get a path of a handle that we should be able to get a path for).EDIT#2: Here's where the
GetFinalPathNameByHandle
call was introduced: #16783 and the bug it fixed: #16779There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Zig file system API should make this fail for all operating systems. You shouldn't be able to open a parent directory from an open directory handle.
The only exception is the current working directory, which is already an exception for other use cases.
This hack should have never been made, and by not making the hack it would have helped us reach that conclusion earlier.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fwiw, I believe it was me who reported ".. doesn’t work on windows” (#16779), and, for my use-case, it is indeed enough if that only works for cwd
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This might be a bit complicated due to things like #18452 and #7751. That is, resolving
..
before symlinks (the Windows way) would be a break from normal non-Windows behavior, and resolving symlinks before..
would require syscalls. Symlinks in general complicate things, too.There is a potentially relevant
RESOLVE_BENEATH
flag on Linux (andO_RESOLVE_BENEATH
on FreeBSD), though: https://man7.org/linux/man-pages/man2/openat2.2.html