On Mon, Dec 12, 2005 at 09:09:24AM -0800, Chuck Silvers wrote:
> > If PTHREAD_CONCURRENCY > 1 can cause kernel panics, just removing it from
> > libpthread isn't enouth. The kernel has to be patched as well, otherwise a
> > local user could start an application linked with a bad libpthread and
> > cause a local DOS.
> 
> I was more worried about us advertising a feature that crashes the system
> than a malicious user.  but disabling the sa_setconcurrency() syscall
> as well is easy enough, I'll add that to the patch.

Maybe not disable it (possible backward compat issues ?) but return error
if the value is not 1.

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la difference
--