[Bug 50586] NtQueryInformationFile returns STATUS_INVALID_INFO_CLASS on symlinks opened with FILE_OPEN_REPARSE_POINT

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=50586

--- Comment #12 from Erich E. Hoover <erich.e.hoover at gmail.com> ---
(In reply to Zebediah Figura from comment #11)
> (In reply to Erich E. Hoover from comment #10)
> > ...
> > Are you talking about applications that look for files based on inode?  We
> > could conceivably report the inode of the symlink in the case of a
> > transparent symlink like this (and this is a feature that wouldn't be too
> > hard to add in the future).
> 
> I'm not immediately sure it's the only problem, but it does come to mind as
> a concern. Note that the above solution won't work for directory symlinks.

Yeah, I'm not sure what we could possibly do to properly support a cross-device
directory unix symlink if someone's searching the disk by inode.  If we treated
them as NT symlinks then any application doing this is _supposed_ to use
GetVolumePathName to search the correct volume.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.