From: "Serge E. Hallyn" <serge@hallyn.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: "Serge E. Hallyn" <serue@us.ibm.com>,
Linux Containers <containers@lists.osdl.org>,
mingo@elte.hu, Bharata B Rao <bharata@linux.vnet.ibm.com>,
lkml <linux-kernel@vger.kernel.org>,
Dhaval Giani <dhaval@linux.vnet.ibm.com>
Subject: Re: [PATCH 1/1] introduce user_ns inheritance in user-sched
Date: Fri, 20 Mar 2009 21:46:39 -0500 [thread overview]
Message-ID: <20090321024639.GB21064@hallyn.com> (raw)
In-Reply-To: <1237537460.24626.32.camel@twins>
Quoting Peter Zijlstra (peterz@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.
-serge
next prev parent reply other threads:[~2009-03-21 2:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-19 21:16 Serge E. Hallyn
2009-03-19 23:55 ` Matt Helsley
2009-03-20 0:07 ` Serge E. Hallyn
2009-03-20 0:23 ` Serge E. Hallyn
2009-03-20 8:24 ` Peter Zijlstra
2009-03-21 2:46 ` Serge E. Hallyn [this message]
2009-03-21 11:36 ` Peter Zijlstra
2009-03-22 8:00 ` Dhaval Giani
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090321024639.GB21064@hallyn.com \
--to=serge@hallyn.com \
--cc=bharata@linux.vnet.ibm.com \
--cc=containers@lists.osdl.org \
--cc=dhaval@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=serue@us.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®