Messages in this thread | | | From | <> | Subject | RE: clone() and CLONE_PID | Date | Mon, 13 Sep 1999 15:57:31 +0200 |
| |
> > You have this the wrong way round. The CLONE_PID option is one > > approach to implementing signals according to the POSIX threads > > spec. But it is not the only approach, and since it would require a > > separate notion of thread id to be added to the kernel, it might not > > be the simplest approach (as far as the kernel is concerned). > > CLONE_PID causes enough potential security hazards it is > going away in > 2.2.13 and some point in 2.3.x. It was never intended to be > user accessible > its a hack for the boot up code What kind of security hole could give PID ack ? Does it mean the whole thread library falls under 2.2.13 ?
Fabian
- 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/
| |