linux-kernel - Re: [patch] PID namespace design bug, workaround

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <20071102010419.23f3db5c.akpm@linux-foundation.org>
Date:	Fri, 2 Nov 2007 01:04:19 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Pavel Emelyanov <xemul@...nvz.org>
Cc:	Ulrich Drepper <drepper@...hat.com>, Ingo Molnar <mingo@...e.hu>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [patch] PID namespace design bug, workaround

On Fri, 02 Nov 2007 10:55:02 +0300 Pavel Emelyanov <xemul@...nvz.org> wrote:

> Ulrich Drepper wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> > 
> > Pavel Emelyanov wrote:
> >> The "fix" I mention is just returning -EINVAL in case user orders 
> >> CLONE_NEWPIDS
> > 
> > That is the "fix" you were referring to?  I was hoping you have a sketch
> > for a real solution.  If nobody can think of a way to fix this PID
> 
> Looks like we misunderstood each other. Can you please elaborate on 
> what exactly is broken in pid namespaces?

Isn't it this?

http://lkml.org/lkml/2007/11/1/141

-
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/