lkml.org 
[lkml]   [2010]   [Jun]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [autofs] [PATCH 04/38] autofs4: Save autofs trigger's vfsmount in super block info
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@suse.de>
> >
> > 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.

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?

Thanks,

-VAL


\
 
 \ /
  Last update: 2010-06-17 01:17    [from the cache]
©2003-2011 Jasper Spaans