schedcpu() in /sys/kern/sched_4bsd.c calls thread_lock() on thread with un-initialized td_lock

[Svatopluk Kraus]

On Thu, Mar 31, 2011 at 4:10 PM, Andriy Gapon <avg at freebsd.org> wrote:
> on 31/03/2011 14:32 Svatopluk Kraus said the following:
>> Hi,
>>
>>   I've got a page fault (because of NULL td_lock) in
>> thread_lock_flags() called from schedcpu() in /sys/kern/sched_4bsd.c
>> file. During process fork, new thread is linked to new process which
>> is linked to allproc list and both allproc_lock and new process lock
>> are unlocked before sched_fork() is called, where new thread td_lock
>> is initialized. Only PRS_NEW process status is on sentry but not
>> checked in schedcpu().
>
> How recent is your current?
> This sounds like something that could have been recently fixed.
>

My current is from 20.3.2011 but I have looked at CVS on freebsd.org
just before my post. It didn't look to be solved.