hall and autofs

[Danny Kukawka]

On Friday 28 April 2006 15:25, Ian Kent wrote:
[...]
> > We do something like this already on SUSE. We skip check e.g. NFS mounts
> > because this can freeze the hole hal and applications using HAL freeze or
> > fail, if you have NFS stale mountpoints in the system and because we
> > never provide infos in HAL about NFS mounts (hence, we don't need to stat
> > them).
> >
> > I attach the patch from SUSE against 0.5.6. If okay, I commit the patch
> > to CVS.
>
> I think that's only part of the difficulty.
>
> It's likely needed to skip anything under a filesystem type of "autofs"
> because within the autofs filesystem there can be cifs, NFS, bind mounts
> or whatever. These can be nested under certain circumstances.
>
> I think the current reported problem is where there is an automount
> trigger as an intermediate directory to the mount point being stat()ed.
> In this case the kernel module will see the LOOKUP_CONTINUE flag during
> the path walk and quite rightly mount the intervening filesystem.

What is the output of 'cat /proc/mounts' in this case? What is the listed 
filesystem in this case? autofs or the real filesystem? IMO there is the real 
fs listed, but not sure. Could you paste the output?

Cheers,

Danny