Re: How to unmount mounts corresponding to super_block structure?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi

On Tue, Feb 26, 2013 at 10:56 PM, Al Viro <viro@xxxxxxxxxxxxxxxxxx> wrote:
> Simple: don't.  This is fundamentally wrong thing to do.  Not to mention
> anything else, there may be more than one namespace out there.  This
> operation makes no sense.

Yes I understand that there can be multiple namespaces. And I am fine
with unmounting only in the current namespace. It is actually how
libfuse currently implemented - it calls umount() on the mount point
path, so it leaves 1) bind mounts 2) mounts in other namespaces
untouched.

Another ugly-but-working solution for fuse would be pass mountpoint
path as a mount option and store it to super_block. Then in
fuse_dev_release() call sys_umount(). But I am looking if there are
any cleaner solutions.
--
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


[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux