Date: Thu, 31 Mar 2011 17:10:50 +0300 From: Andriy Gapon <avg@FreeBSD.org> To: Svatopluk Kraus <onwahe@gmail.com> 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: <4D948B6A.6000906@FreeBSD.org> In-Reply-To: <AANLkTimEiOW%2BkSZD6n1MHiRou3UWibU6Oy3fr9RO4_O4@mail.gmail.com> References: <AANLkTimEiOW%2BkSZD6n1MHiRou3UWibU6Oy3fr9RO4_O4@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D948B6A.6000906>