From mboxrd@z Thu Jan 1 00:00:00 1970 From: Al Viro Subject: Re: [PATCHv10 man-pages 5/5] execveat.2: initial man page for execveat(2) Date: Fri, 9 Jan 2015 22:57:43 +0000 Message-ID: <20150109225743.GP22149@ZenIV.linux.org.uk> References: <20150109204815.GR4574@brightrain.aerifal.cx> <20150109205626.GK22149@ZenIV.linux.org.uk> <20150109205926.GT4574@brightrain.aerifal.cx> <20150109210941.GL22149@ZenIV.linux.org.uk> <20150109212852.GU4574@brightrain.aerifal.cx> <20150109215042.GM22149@ZenIV.linux.org.uk> <20150109221728.GW4574@brightrain.aerifal.cx> <20150109223300.GO22149@ZenIV.linux.org.uk> <20150109224252.GY4574@brightrain.aerifal.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20150109224252.GY4574-C3MtFaGISjmo6RMmaWD+6Sb1p8zYI1N1@public.gmane.org> Sender: linux-api-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Rich Felker Cc: David Drysdale , "Michael Kerrisk (man-pages)" , "Eric W. Biederman" , Andy Lutomirski , Meredydd Luff , "linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Andrew Morton , David Miller , Thomas Gleixner , Stephen Rothwell , Oleg Nesterov , Ingo Molnar , "H. Peter Anvin" , Kees Cook , Arnd Bergmann , Christoph Hellwig , X86 ML , linux-arch , Linux API , sparclinux-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-api@vger.kernel.org On Fri, Jan 09, 2015 at 05:42:52PM -0500, Rich Felker wrote: > Here's a very simple way it could work -- it could put the O_PATH fd > on a previously-unused fd number, and put a special flag on the fd, > like FD_CLOEXEC, but that causes the kernel to close it whenever it's > opened. The pathname passed could then simply be /dev/fd/%d or > /proc/self/fd/%d, and although this is presently dependent on /proc > being mounted, virtual /dev/fd/* could someday be something completely > independent of procfs. The kernel keeps all the freedom to choose how > to pass the name to the interpreter. I'm not proposing any kernel > API/ABI lock-in and I'm with you in opposing such lock-in. Huh? open() on procfs symlinks does *NOT* work the way - the symlink is traversed and after that point there is no information whatsoever how we got to that vfsmount/dentry pair. I can imagine several kludges that would work, but they are unspeakably ugly, and do_last() is already far too convoluted as it is.