From owner-freebsd-current Tue Oct 1 2:40:17 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DC5D437B401; Tue, 1 Oct 2002 02:40:16 -0700 (PDT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 528D843E42; Tue, 1 Oct 2002 02:40:15 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Received: from mousie.catspoiler.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.5/8.12.5) with ESMTP id g919e7vU012557; Tue, 1 Oct 2002 02:40:11 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Message-Id: <200210010940.g919e7vU012557@gw.catspoiler.org> Date: Tue, 1 Oct 2002 02:40:07 -0700 (PDT) From: Don Lewis Subject: Re: World broken at libkvm To: jmallett@FreeBSD.ORG Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <20020930224942.A73940@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 30 Sep, Juli Mallett wrote: > No locks except for the lock of the process being signalled should be > held when sending signals, IMHO, though I am mostly ignorant of the SIGIO > locking. BTW, kill() wants to hold the allproc_lock or a process group lock while iterating over the list of processes to send signals to. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message