AT_EXECFN not useful

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Linux Kernel <linux-kernel@...>, John Reiser <jreiser@...>
Cc: Linus Torvalds <torvalds@...>, Andrew Morton <akpm@...>
Date: Thursday, August 14, 2008 - 1:15 pm

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I've just removed the support for AT_EXECFN again from glibc.  The
information isn't useful because the path name isn't normalized.  I.e.,
it's not the actual binary path if symlinks are followed during the
resolution.  This makes it unusable for the $ORIGIN handling.  This is
on top of the problem with relative paths.

Unless somebody has another use case where this is useful I suggest
removing AT_EXECFN support again.  It's just superfluous work and memory
use.

Of course I wouldn't object to a real implementation which always gives
me the full, normalized path name of the executable...

- --
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkikaDEACgkQ2ijCOnn/RHSFvACgoWYhqrfJZfRe4ypFUQQR9soJ
km8AnRchCWP+irhGcgoSzd2S8iYQi7zm
=E4tz
-----END PGP SIGNATURE-----
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
AT_EXECFN not useful, Ulrich Drepper, (Thu Aug 14, 1:15 pm)
Re: AT_EXECFN not useful, John Reiser, (Fri Aug 15, 1:10 am)
Re: AT_EXECFN not useful, Ulrich Drepper, (Fri Aug 15, 7:59 pm)
Re: AT_EXECFN not useful, John Reiser, (Mon Aug 18, 11:04 am)