On Wed, 17 Jun 2009, Al Viro wrote: > 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. That's not the problem with O_NOFOLLOW. The problem is that if you want to actually open the symlink itself (say, you do some filesystem cleanup operation on it, like saying "drop the caches of this file"), you can't do it. O_NOFOLLOW won't open the symlink, it will just refuse to follow it, and return an error. Linus -- 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
