> | can you explain why realpath should be a system call?
> 
> Because it is quite pointless to do string gymnastics in userland
> where the kernel has all the code to do this. Our code has been
> historically broken:
> 
> - we had bugs where we forgot to NUL terminate

such mistakes can happen in kernel as well.
and their implications can be much worse in kernel.

> - we had bugs where the code was not thread-safe
> 
> And still:
> 
> - it does not handle magiclinks (your PR 30664)

they are newer than realpath.

> I am looking for something like solaris' resolvepath(2) which can be
> used to implement the rest of realpath(3) in userland.
> 
> christos

it isn't necessary to solve these PRs, right?

YAMAMOTO Takashi