From owner-freebsd-arch@FreeBSD.ORG Thu Jan 26 02:38:47 2006 Return-Path: X-Original-To: arch@freebsd.org Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B1EEF16A422; Thu, 26 Jan 2006 02:38:47 +0000 (GMT) (envelope-from davidxu@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7304C43D46; Thu, 26 Jan 2006 02:38:47 +0000 (GMT) (envelope-from davidxu@freebsd.org) Received: from [127.0.0.1] (root@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k0Q2ci6l061298; Thu, 26 Jan 2006 02:38:45 GMT (envelope-from davidxu@freebsd.org) Message-ID: <43D8363F.3090104@freebsd.org> Date: Thu, 26 Jan 2006 10:38:55 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20050928 X-Accept-Language: en-us, en MIME-Version: 1.0 To: David Xu References: <43D6C3A5.4060100@freebsd.org> <86k6coodch.fsf@xps.des.no> <43D812F7.50808@freebsd.org> <43D825C2.4000004@elischer.org> <43D832F1.6040602@freebsd.org> In-Reply-To: <43D832F1.6040602@freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: =?ISO-8859-1?Q?Dag-Erling_Sm?=, =?ISO-8859-1?Q?=F8rgrav?= , Julian Elischer , arch@freebsd.org Subject: Re: vfs_aio.c is still not safe X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jan 2006 02:38:47 -0000 David Xu wrote: > If a user process got a signal which will bring it down, thread_single() > call in exit1() should cause the kthreads to exit, this can be done. > This also reminds me another problem, if all user threads exited by > calling e.g: thr_exit or kse_exit, now, these kthreads should exit too, > so the code should be adjusted,not only ptrace code. > > I have rechecked thr_exit(), there is a band-aid, the lastest thread can not exit via thr_exit(), so thr_exit and kse_exit need not be worried.