On Wed, 2010-06-16 at 19:14 -0400, Valerie Aurora wrote: > On Wed, Jun 16, 2010 at 12:04:03PM +0800, Ian Kent wrote: > > On Tue, 2010-06-15 at 11:39 -0700, Valerie Aurora wrote: > > > From: Jan Blunck <jblunck@xxxxxxx> > > > > > > XXX - This is broken and included just to make union mounts work. See > > > discussion at: > > > > > > http://kerneltrap.org/mailarchive/linux-fsdevel/2010/1/15/6708053/thread > > > > Instead of saving the vfsmount we could save a pointer to the dentry of > > the mount point in the autofs super block info struct. I think that's > > the bit I don't have so it would be sufficient for a lookup_mnt() for > > the needed vfsmount in ->follow_mount(). > > > > Objections? > > Suggestions? > > I'm not sure... it seems like it would have the same problem that Al > described with pinning the vfsmount forever. But I don't know autofs > at all. That's why I asked. But I don't see how the dentry can go away since it's covered by the mount for the life of the mount. > > Could you run through a quick example of the case that triggers this > problem in the first place? The problem is when you have a symlink > that triggers an automount, and you are trying to get from the target > of the symlink to the vfsmount of the file system containing the > symlink in the first place? Or do I have that wrong? Ha! Yes, you would think we were talking about a symlink but this dentry is a directory, a trigger for a mount that uses ->follow_mount() to do the mount, similar to the way the NFS client mounts nohide mounts when they crossed. In the autofs case we have: <path in fs>/dir <autofs fs (with type direct or offset) mounted on>/dir When ->follow_link() is called the nameidata has the vfsmount of the once removed mount because it hasn't yet been updated in (say) link_path_walk(), but the dentry passed to ->follow_link() is the global root of the autofs fs so we have no way of discovering the vfsmount or the dentry upon which the autofs trigger mount is mounted. Which of course prevents us from mounting and following the trigger. The example is rather poor, sorry, hope it is sufficient. -- 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
