From: Ingo Molnar <mingo@elte.hu>
To: "Serge E. Hallyn" <serue@us.ibm.com>
Cc: James Morris <jmorris@namei.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
lkml <linux-kernel@vger.kernel.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Michael Kerrisk <mtk.manpages@gmail.com>,
Dhaval Giani <dhaval@linux.vnet.ibm.com>
Subject: Re: [PATCH 1/1] user namespaces: document CFS behavior
Date: Fri, 12 Dec 2008 12:06:45 +0100 [thread overview]
Message-ID: <20081212110645.GE32640@elte.hu> (raw)
In-Reply-To: <20081209161620.GC9487@us.ibm.com>
* Serge E. Hallyn <serue@us.ibm.com> wrote:
> Quoting James Morris (jmorris@namei.org):
> > On Tue, 9 Dec 2008, Ingo Molnar wrote:
> >
> > > > They're already published in my tree. Do you want me to revert them?
> > >
> > > I've also got it published :-/ If it's at the tail of your commits, can
> > > you reset it?
> >
> > There have been commits since, and people are using the tree in any case.
>
> Yikes. Maybe it's best (henceforth) to keep user namespaces patches in
> their own tree toward the end of linux-next? There certainly are
> security implications with all of them, but other things (filesystem,
> sched) will be impacted as well...
i'm fine with having this in James's tree - i didnt realize that you had
another commit that created dependencies.
(if such situations ever cause real damage then we can always create a
separate branch to track it cleanly. That's not needed now.)
Ingo
prev parent reply other threads:[~2008-12-12 11:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-08 21:52 [PATCH 1/1] user namespaces: document CFS behavior Serge E. Hallyn
2008-12-08 22:27 ` James Morris
2008-12-08 22:44 ` Serge E. Hallyn
2008-12-09 2:45 ` Ingo Molnar
2008-12-09 9:05 ` James Morris
2008-12-09 10:08 ` Ingo Molnar
2008-12-09 10:15 ` James Morris
2008-12-09 16:16 ` Serge E. Hallyn
2008-12-12 11:06 ` Ingo Molnar [this message]
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=20081212110645.GE32640@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=dhaval@linux.vnet.ibm.com \
--cc=ebiederm@xmission.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--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