> This is not a proposal - I'm not saying it's pretty - but a suggestion
> that you can use today.
>
> Use clone(), and then have the child task open "/" and pass that file
> descriptor back to the parent process using a unix socket. The child
> can exit and the parent can use the new namespace how it likes. Short
> and sweet, and you can create as many namespaces as you like :)
>
> That's mkdir done.
Right.
> You can't do a lot with the new namespace, because of the security
> restrictions on mount() on a foreign namespace. That's what I meant
> about the "small fixes" - get rid of the current->namespace checks and
> it'll be usable.
>
> I don't see the purpose of current->namespace and the associated mount
> restrictions at all. I asked Al Viro what it's for, but haven't seen
> a reply :( IMHO current->namespace should simply be removed, because the
> "current namespace" is represented just fine by
> current->fs->rootmnt->mnt_namespace.
I'll look at what it would take to remove current->namespace.
Miklos
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
