lkml.org 
[lkml]   [1999]   [Sep]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: clone() and CLONE_PID
From
Date
Matthew Kirkwood <weejock@ferret.lmh.ox.ac.uk> writes:
> On Tue, 7 Sep 1999, Lorenzo Allegrucci wrote:
>
> > This is from the LinuxThreads README file:
>
> > One thing that they do not share
> > is their pid's and parent pid's. According to the standard, they
> > should have the same, but that's one thing we cannot achieve
> > in this implementation (until the CLONE_PID flag to clone() becomes
> > usable).
> >
> > When does the CLONE_PID flag to clone() becomes usable? 2.4.x? 2.5.x?
>
> 2.3 has the facility to share parent process ids.

Unfortunately that addition was half-baked, and introduced security
holes. Linus has been sent patches to fix this; it's probably time to
pester him again.

> [snip]
>
> Does the pthread standard really require the pid sharing semantics?
> That will break quite a bit of the kernel, and an awful lot of userspace.

POSIX is just an API; it doesn't tell you how to design a
kernel. Generally Linux directly implements POSIX features because
that is simpler, but for POSIX threads it's worth stepping back and
asking what it really needs from the kernel. My opinion is that doesn't
include pid sharing and tids.


David Wragg


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:53    [W:0.063 / U:0.108 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site