Re: BUG: /proc/self/exe reports relative paths, should always return absolute paths?

[Svante Signell]

On Mon, 2017-09-18 at 20:56 +0200, Samuel Thibault wrote:
> Svante Signell, on lun. 18 sept. 2017 19:45:39 +0200, wrote:
> > lrwxr-xr-x 1 root root 26 Aug 17 07:38 /usr/sbin/update-fmtutil -> update-
> > tl-
> > stacked-conffile
> > 
> > In this case the link name should not be resolved. Any ideas?
> 
> Well, it should, but just not the symlink parts, only the cwd part.
> 
> Perhaps we could simply to check whether the file_name begins with a
> '/', in case we can keep as it is, or not, in which case we can just
> prepend the getcwd().

I changed the patch for __execve() to keep file_name if the path is absolute and
call realpath() for relative paths. Seems to work fine now, new patch attached.
(I did also a cetcwd() version, but that does not seem to be needed, and using
realpath() is simpler.)

submitted-exec_filename.diff
Description: Text Data