From owner-cvs-all Thu Sep 13 15:40:22 2001 Delivered-To: cvs-all@freebsd.org Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id 567D037B41C; Thu, 13 Sep 2001 15:40:10 -0700 (PDT) Received: from laptop.baldwin.cx (john@[147.11.46.201]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id PAA29587; Thu, 13 Sep 2001 15:40:09 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200109132233.f8DMXbC97744@freefall.freebsd.org> Date: Thu, 13 Sep 2001 15:40:03 -0700 (PDT) From: John Baldwin To: John Baldwin Subject: RE: cvs commit: src/sys/kern kern_lock.c kern_subr.c Cc: cvs-all@FreeBSD.org, cvs-committers@FreeBSD.org Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 13-Sep-01 John Baldwin wrote: > jhb 2001/09/13 15:33:37 PDT > > Modified files: > sys/kern kern_lock.c kern_subr.c > Log: > Fix locking on td_flags for TDF_DEADLKTREAT. If the comments in the code > are true that curthread can change during this function, then this flag > needs to become a KSE flag, not a thread flag. I don't think that the thread could go away just do to copyin/copyout though. If it does then we have much bigger problems I think: like breaking anything that holds a lockmgr or sx lock across copyin/copyout. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message