linux-kernel - Re: [PATCH 1/1] user namespaces: document CFS behavior

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 12 Dec 2008 12:06:45 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	"Serge E. Hallyn" <serue@...ibm.com>
Cc:	James Morris <jmorris@...ei.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	lkml <linux-kernel@...r.kernel.org>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Michael Kerrisk <mtk.manpages@...il.com>,
	Dhaval Giani <dhaval@...ux.vnet.ibm.com>
Subject: Re: [PATCH 1/1] user namespaces: document CFS behavior


* Serge E. Hallyn <serue@...ibm.com> wrote:

> Quoting James Morris (jmorris@...ei.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/