On Sun, Dec 11, 2005 at 01:22:02PM +0100, Manuel Bouyer wrote:
> On Sat, Dec 10, 2005 at 04:41:29PM -0800, Chuck Silvers wrote:
> > since the code triggered by setting PTHREAD_CONCURRENCY causes
> > library aborts and kernel panics, I'd like to disable it for 3.0
> > since it doesn't appear that it can be fixed in time.
> > 
> > any objections to the attached patch?  I'll just ask for it to be
> 
> 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.

-Chuck