RFC: Reparse Point/NT Symlink Support [3]

Zebediah Figura (she/her) zfigura at codeweavers.com
Tue Aug 31 12:11:40 CDT 2021

On 8/31/21 12:00 PM, Erich E. Hoover wrote:
> On Tue, Aug 31, 2021 at 10:52 AM Zebediah Figura (she/her)
> <zfigura at codeweavers.com> wrote:
>> ...
>> Is there a problem with collapse_path(), or is it just a matter of
>> asking for the parent of the current directory? If the latter, wouldn't
>> it just be a matter of storing the unresolved path in the TEB?
> That's necessary but not sufficient, you also need to change the path
> resolution.  It's completely valid (and common) to pass a relative
> path that does something "stupid".  An extension of the Linux example:
> ===
> ~/tmplnk$ cd link/..
> ~/tmplnk$ ls
> link  test
> ~/tmplnk$ ls link/..
> target
> ===

Doesn't this end up being a problem regardless of how we store symlinks 
internally, though? As far as I can tell, all of this logic should 
happen on the PE side.

More information about the wine-devel mailing list