Subject: Re: lib/30664: realpath and magic symlinks
To: Jason Thorpe <firstname.lastname@example.org>
From: Chuck Silvers <email@example.com>
Date: 07/08/2005 10:23:30
On Fri, Jul 08, 2005 at 09:02:19AM -0700, Jason Thorpe wrote:
> On Jul 4, 2005, at 4:26 PM, firstname.lastname@example.org wrote:
> > realpath(3) (or, more generally, userland code which resolves
> > symlinks by itsself using readlink(2)) doesn't handle
> > magic symlinks and can cause problems.
> > it's subtle because it isn't obvious which of userland or kernel
> > resolves a symlink for a given application.
> Perhaps readlink(2) should translate the magic symlink? But that
> would break ls(1). Perhaps we could add a readlink2(2) that takes a
> flags argument, allowing us to specify "raw" or "translated".
> readlink(2) would default to "translated", and ls(1) would be changed
> to use "raw".
I think that the real problem is having the path interpretation be different
for symlinks vs. other path lookups done in the kernel. it would make
a lot more sense to have the tranlation done for all pathname lookups
or none, and not this awkward halfway thing that "magic symlinks" provides.
then readlink() would be fine as it is.