From owner-freebsd-stable@FreeBSD.ORG Tue Aug 29 07:50:43 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6EB5816A4DF for ; Tue, 29 Aug 2006 07:50:43 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail29.syd.optusnet.com.au (mail29.syd.optusnet.com.au [211.29.132.171]) by mx1.FreeBSD.org (Postfix) with ESMTP id B262043D46 for ; Tue, 29 Aug 2006 07:50:42 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail29.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k7T7oZ6S004545 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 29 Aug 2006 17:50:36 +1000 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.6/8.13.6) with ESMTP id k7T7oZfM000983; Tue, 29 Aug 2006 17:50:35 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.6/8.13.6/Submit) id k7T7oYfX000982; Tue, 29 Aug 2006 17:50:34 +1000 (EST) (envelope-from peter) Date: Tue, 29 Aug 2006 17:50:34 +1000 From: Peter Jeremy To: Michael Abbott Message-ID: <20060829075034.GA727@turion.vk2pj.dyndns.org> References: <200608281220.k7SCKoJW054182@lurza.secnetix.de> <20060828124935.G62656@saturn.araneidae.co.uk> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="tThc/1wpZn/ma/RB" Content-Disposition: inline In-Reply-To: <20060828124935.G62656@saturn.araneidae.co.uk> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.12-2006-07-14 Cc: freebsd-stable@freebsd.org Subject: Re: NFS locking: lockf freezes (rpc.lockd problem?) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Aug 2006 07:50:43 -0000 --tThc/1wpZn/ma/RB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, 2006-Aug-28 13:23:30 +0000, Michael Abbott wrote: >I think there is a case to be made for special casing SIGKILL, but in a=20 >sense it's not so much the fate of the process receiving the SIGKILL that= =20 >counts: after all, having sent -9 I know that it will never process again. Currently, if you send SIGKILL, the process will never enter userland again. Going further, so that if you send a process SIGKILL, it will always terminate immediately is significantly more difficult. In the normal case, a process is sleeping on some condition with PCATCH specified. If the process receives a signal, sleep(9) will return ERESTART or EINTR and the code has to then arrange to return back to userland (which will cause the signal to be handled as per sigaction(2) and the processes signal handlers). In some cases, it may be inconvenient to unwind back to userland from a particular point so PCATCH isn't specified on the sleep. --=20 Peter Jeremy --tThc/1wpZn/ma/RB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFE8/HK/opHv/APuIcRAhQEAKCWv2sentHLbSPJ9oW8AJ8Y6Y+HdACeIaAD /NHhnK8Bh+2/Jj1tfk5AJbw= =8D3p -----END PGP SIGNATURE----- --tThc/1wpZn/ma/RB--