Date: Thu, 31 Mar 2011 16:35:06 +0200 From: Svatopluk Kraus <onwahe@gmail.com> To: Andriy Gapon <avg@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: schedcpu() in /sys/kern/sched_4bsd.c calls thread_lock() on thread with un-initialized td_lock Message-ID: <AANLkTi=v9D26EdjHabWtJHGY_Ls85s7ejKY7KjKMj1cq@mail.gmail.com> In-Reply-To: <4D948B6A.6000906@FreeBSD.org> References: <AANLkTimEiOW%2BkSZD6n1MHiRou3UWibU6Oy3fr9RO4_O4@mail.gmail.com> <4D948B6A.6000906@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Mar 31, 2011 at 4:10 PM, Andriy Gapon <avg@freebsd.org> wrote: > on 31/03/2011 14:32 Svatopluk Kraus said the following: >> Hi, >> >> =A0 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTi=v9D26EdjHabWtJHGY_Ls85s7ejKY7KjKMj1cq>