A reparse point that is an IO_REPARSE_TAG_MOUNT_POINT could be a junction or an actual filesystem mount point. (Who knew?) If it's the latter, its reparse point will report the actual volume information \??\Volume{GUID}\ and we should not attempt to dereference that further, instead readlink should report EINVAL since it's not a symlink / junction and its original path was canonical. Yes, really.
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
dir.c | Loading commit data... | |
dir.h | Loading commit data... | |
error.c | Loading commit data... | |
error.h | Loading commit data... | |
findfile.c | Loading commit data... | |
findfile.h | Loading commit data... | |
git2.rc | Loading commit data... | |
map.c | Loading commit data... | |
mingw-compat.h | Loading commit data... | |
msvc-compat.h | Loading commit data... | |
posix.h | Loading commit data... | |
posix_w32.c | Loading commit data... | |
precompiled.c | Loading commit data... | |
precompiled.h | Loading commit data... | |
pthread.c | Loading commit data... | |
pthread.h | Loading commit data... | |
reparse.h | Loading commit data... | |
utf-conv.c | Loading commit data... | |
utf-conv.h | Loading commit data... | |
version.h | Loading commit data... | |
w32_util.c | Loading commit data... | |
w32_util.h | Loading commit data... |