Re: [RCF] [PATCH] unprivileged mount/umount

From: Ram (linuxram_at_us.ibm.com)
Date: 05/11/05

  • Next message: Bruce Guenter: "Re: How to diagnose a kernel memory leak" 
    To: Miklos Szeredi <miklos@szeredi.hu>
Date:	Wed, 11 May 2005 12:35:39 -0700

    On Wed, 2005-05-11 at 11:49, Miklos Szeredi wrote:
    > > > > How about a new clone option "CLONE_NOSUID"?
    > > >
    > > > IMO, the clone call ist the wrong place to create namespaces. It should be
    > > > deprecated by a mkdir/chdir-like interface.
    > >
    > > And the mkdir/chdir interface already exists, see "cd /proc/NNN/root".
    >
    > That's the chdir part.

    What if proc filesystem is removed from the kernel?

    Ability to access some other namespace through the proc filesystem does
    not look clean. I think it should be cleanly supported through VFS.

    Also cd'ing into a new namespace just allows you to browse through
    the other namespace. But it does not effectively change the process's
    namespace. Things like mount in the other namespace will be failed
    by check_mount() anyway.

    I think, we need sys calls like sys_cdnamespace() which switches to a
    new namespace.

    Effectively the process's current->namespace has to be modified,
    for the process to be effectively work in the new namespace.

    >
    > The mkdir part is clone() or unshare().

     clone/unshare will give you the ability to share/unshare a know
    namespace. But to share some arbitrary namespace to which a process
    has access rights to.

    > How else do you propose to create new namespaces?
    >

    RP

    > Miklos
    > -
    > To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
    > the body of a message to majordomo@vger.kernel.org
    > More majordomo info at http://vger.kernel.org/majordomo-info.html

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  • Next message: Bruce Guenter: "Re: How to diagnose a kernel memory leak"

    Relevant Pages

    • Re: [PATCH] private mounts
      ... What if some filesystem allowed access to vfsmount in other namespace? ... Just like the proc filesystem having the ability to do so, ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: TIP 278: does it cause any breakage?
      ... namespace, and it should work the same as it does for procedures. ... we bring them into our current scope. ... never found a use for 's ability to set the value, ... I'd love to see [upvar] get the ability to take a namespace instead of ...
      (comp.lang.tcl)
    • Re: [RCF] [PATCH] unprivileged mount/umount
      ... >> Ability to access some other namespace through the proc filesystem does ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [RCF] [PATCH] unprivileged mount/umount
      ... > Ability to access some other namespace through the proc filesystem does ... Jamie's proposal was to make chroot() swich namespace. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [RCF] [PATCH] unprivileged mount/umount
      ... > Ability to access some other namespace through the proc filesystem does ... But it does not effectively change the process's ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    Loading