On Fri, Jan 09, 2015 at 03:48:15PM -0500, Rich Felker wrote: > I think this is a case that needs to be fixed, though it's hard. The > normal correct usage for fexecve is to always pass an O_CLOEXEC file > descriptor, and the caller can't really be expected to know whether > the file is a script or not. We discussed workarounds before and one > idea I proposed was having fexecve provide a "one open only" magic > symlink in /proc/self/ to pass to the interpreter. It would behave > like an O_PATH file descriptor magic symlink in /proc/self/fd, but > would automatically cease to exist on the first open (at which point > the interpreter would have a real O_RDONLY file descriptor for the > underlying file). For fsck sake, folks, if you have bloody /proc, you don't need that shite at all! Just do execve on /proc/self/fd/n, and be done with that. The sole excuse for merging that thing in the first place had been "would anybody think of children^Wsclerotic^Whardened environments where they have no /proc at all". Sheesh... -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
