Messages in this thread | | | Subject | Re: sysctls inside containers | From | Dave Hansen <> | Date | Fri, 10 Mar 2006 10:58:33 -0800 |
| |
On Fri, 2006-03-10 at 13:19 +0300, Kirill Korotaev wrote: > > On another note, after messing with putting data in the init_task for > > these things, I'm a little more convinced that we aren't going to want > > to clutter up the task_struct with all kinds of containerized resources, > > _plus_ make all of the interfaces to share or unshare each of those. > > That global 'struct container' is looking a bit more attractive. > > have you noticed that ipc/mqueue.c uses netlink to send messages? > This essentially means that they are tied as well...
Nope, I missed that.
But, netlink is probably a completely separate issue, at least for now. I'm sure we're going to have "container leaks" and boundary violations for a long time, but I'll add netlink to the list.
-- Dave
- 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/
| |