[PATCH 1/1] introduce user_ns inheritance in user-sched

Serge E. Hallyn serge at hallyn.com
Fri Mar 20 19:46:39 PDT 2009

Quoting Peter Zijlstra (peterz at infradead.org):
> On Thu, 2009-03-19 at 16:16 -0500, Serge E. Hallyn wrote:
> > In a kernel compiled with CONFIG_USER_SCHED=y, cpu shares are
> > allocated according to uid.  Shares are specifiable under
> > /sys/kernel/uids/<uid>/
> > 
> > In a kernel compiled with CONFIG_USER_NS=y, clone(2) with the
> > CLONE_NEWUSER flag creates a new user namespace, and the newly
> > cloned task will belong to uid 0 in the new user namespace.
> We seem to be adding more and more stuff for USER_SCHED, is anybody
> actually using that cruft?
> How far along with cgroups are we to fully simulate that behaviour?
> I think if we have a capable cgroup based replacement for USER_SCHED we
> should axe it from the kernel, would save lots of code...

I didn't realize that was the plan.  Using PAM to move users
around cgroups?  If so, then yeah that would simplify quite a bit
of code.   Won't catch all setuid()s of course - I don't know
who uses USER_SCHED and if that would matter.


More information about the Containers mailing list