On Tuesday 16 February 2010 18:29:00 Ian Kent wrote: > On 02/16/2010 09:20 PM, Stef Bon wrote: > > On Tuesday 16 February 2010 04:04:17 Ian Kent wrote: > >> On 02/16/2010 05:53 AM, Stef Bon wrote: > >>> Hello, > >> > >> Yes, checking /proc/mounts is slow but is the only way when using older > >> versions of the kernel module. > >> > >> In a recent source tree, have a look at lib/mounts.c:is_mounted() and > >> lib/dev-ioctl-lib.c, and in particular dev_ioctl_ismountpoint(). > >> > >> Ian > > > > Thanks for you fast answer. > > > > I've checked the code and found the functions you're pointed, they are > > indeed what I'm looking for. > > > > The function is_mounted looks like an internal function. It makes use of > > a struct ioctl_ops, which is initialised with get_ioctl_ops. I do not > > understand this, cause this function does not use any parameter (like > > path!) so how does this function determine it's a mountpoint? > > Read lib/dev-ioctl-lib.c, that's why I mentioned it, it's not that long. > > It implements a set of functions for autofs control operations. > > Many of them can't be called by just any process but the > dev_ioctl_ismountpoint() function can. It may not look that simple but > if you take some time to understand what it is doing you can take the > bits you need and that will end up being fairly simple. > > The one problem you do have is that if the kernel doesn't have the new > device ioctl interface you will need to scan /proc/mounts, the same as > is done by the is_mounted() function if it sees the new functionality > isn't available.
Ok, but some helpe here is welcome. I've learned C just some months ago, and programming devices is new to me. Look at dev_ioctl_ismountpoint. The parameters it's using are logopt, ioctlfd, path and mountpoint. logopt has something to do with logging, and is important, but not the topic. ioctlfd is the filedescriptor for the fifo(?) in /var/run: /var/run/autofs.fifo-mnt-mount.md5key-sbon-mount in /proc/1705/fd : 9 -> /var/run/autofs.fifo-mnt-mount.md5key-sbon-mount and 15 -> /var/run/autofs.fifo-mnt-mount.md5key-root-mount futher path is of course the path to be examined. Is it absolute or relative and mountpoint is the value which is combination of DEV_IOCTL_IS_MOUNTED, DEV_IOCTL_IS_AUTOFS and DEV_IOCTL_IS_OTHER. Is my analysis good??? To be sure, the value's I'm looking for are autofs managed mountpoints (DEV_IOCTL_IS_AUTOFS is 1) and the path is a mountpoint, which means a resource is actually mounted here. (DEV_IOCTL_IS_OTHER). I'm using a setup where the autofs managed directories are one level deep, nothing more. But does this function really return a path is a mountpoint. In my module, it's already clear that it is an autofs managed dir. In my module autofs managed dirs are of the form /mnt/mount.md5key/%USERID%/mount/%md5key% where %md5key% is the md5sum of the resource record. My fuse module checks the dirname of the path is equal to /mnt/mount.md5key/%USERID%, and the basename is 32 long, and exists. Resource records, containing all the information about a resource (local like USB and remote like SMB and FTP) necessary to mount it. Now I want to add a test in my fusemodule fuse-workspace-union about this autofsmanaged directory is a an active mountpoint, or not active (expired/not activated...). It's not that important, but I want extra cosmetics. When mounted, I want the module to show another icon than when not mounted. Stef > > Ian _______________________________________________ autofs mailing list [email protected] http://linux.kernel.org/mailman/listinfo/autofs
