On Wed, Jun 17, 2009 at 09:09:47AM -0700, Linus Torvalds wrote: > We've traditionally had that magic "open with flag=3" to do a magic open > of device files without waiting, and we have O_NOFOLLOW to open symlinks > without following them (sadly, it just errors out, rather than opening the > symlink, but that's another detail). > > So I think it should be solvable some way, but not by trying to find the > mount point. O_NOFOLLOW *will* open their mountpoints just fine, without triggering automount. Of course, if something's already mounted there, it will get you the covering object. Which is a feature, as far as I'm concerned, since "I've overmounted that to have it unreachable" shouldn't be breakable regardless of the syscall we are using - be it open() or pioctl(). FWIW, count me strongly opposed to that shit; it's too damn ugly to live, has interesting security implications and we'll get stuck with it forever. And we *really* don't need another multiplexor from hell, without anything resembling well-defined semantics. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
