panic: vm_thread_new: kstack allocation failed

[Julian Elischer]

Kip Macy wrote:

> I've seen this when running stress2 with a large number of
> incarnations. Why don't we return an error to the user?


programmer ENOTIME

patch welcome!

>
>                 -Kip
>
> On 9/1/06, Julian Elischer <julian at elischer.org> wrote:
>
>> Vyacheslav Vovk wrote:
>>
>> can you see how many threads thre are in the system?
>> I think you will have to extract this information frome the zone 
>> allocator.
>>
>> I just realised there is no effective limit on kernel threads in the 
>> system.
>> probably one could cause this with a fork bomb appoach using forks and
>> thread creation.
>>
>> >Unread portion of the kernel message buffer:
>> >panic: vm_thread_new: kstack allocation failed
>> >cpuid = 3
>> >Uptime: 7d4h30m58s
>> >
>> >
>> >
>> _______________________________________________
>> freebsd-stable at freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
>> To unsubscribe, send any mail to 
>> "freebsd-stable-unsubscribe at freebsd.org"
>>
> _______________________________________________
> freebsd-threads at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-threads
> To unsubscribe, send any mail to 
> "freebsd-threads-unsubscribe at freebsd.org"