OpenVZ Forum


Home » Mailing lists » Devel » Containers don't handle keys, but should they?
Re: Containers don't handle keys, but should they? [message #28349 is a reply to message #28345] Fri, 14 March 2008 15:49 Go to previous messageGo to previous message
David Howells is currently offline  David Howells
Messages: 44
Registered: October 2006
Member
Serge E. Hallyn <serue@us.ibm.com> wrote:

> It looks like maybe just adding a struct user_namespace * to a struct key
> should suffice.

That's not quite sufficient.  The per-UID key_user structs also need to be
differentiated.  Unfortunately, I can't just merge it into user_struct as I
then end up with a reference loop user_struct -> uid_keyring -> user_struct.

Rooting the key_user trees in user_namespace will probably do the trick.

A couple of questions:

 (1) A process may inherit a session keyring over clone().  Should this be
     discarded if CLONE_NEWUSER is set?  Or would I need to copy it?

 (2) In a recent patch, I've given the root user its own quota limits.  Is UID
     0 always the root user in any container?  Or would it make more sense
     just to scrap the per-root quota limits?

David
_______________________________________________
Containers mailing list
Containers@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/containers
 
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: [PATCH 0/3] Implement triggers for control groups.
Next Topic: [PATCH -mm] cgroup: fix boot option parsing
Goto Forum:
  


Current Time: Sun Oct 12 14:08:02 GMT 2025

Total time taken to generate the page: 0.16293 seconds