From owner-freebsd-current Tue Sep 18 15: 3:12 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id 7DD0C37B40E for ; Tue, 18 Sep 2001 15:03:10 -0700 (PDT) Received: from laptop.baldwin.cx ([147.11.46.201]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id PAA05967; Tue, 18 Sep 2001 15:01:40 -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: <200109181753.f8IHrqb52417@khavrinen.lcs.mit.edu> Date: Tue, 18 Sep 2001 15:01:25 -0700 (PDT) From: John Baldwin To: Garrett Wollman Subject: RE: Seen this lock order reversal? Cc: current@FreeBSD.org 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 18-Sep-01 Garrett Wollman wrote: > lock order reversal > 1st 0xd3a5c11c process lock @ ../../../vm/vm_glue.c:469 > 2nd 0xc0e3fe30 lockmgr interlock @ ../../../kern/kern_lock.c:239 > > This is on relatively old (~ three months) sources. The first lock is > from swapout_procs(); I assume the second lock actually refers to the > call to lockmgr(&vm->vm_map.lock, ...) further down in the same > function. If this has been fixed already, let me know. (It doesn't > seem to have hurt anything.) It is old, but I think it has been fixed recently as a side effect of the KSE commit. (In terms of the pre-KSE kernel, the P_DEADLKTREAT flag moved from p_flag to p_sflag which changed its locking semantics.) > -GAWollman -- 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 freebsd-current" in the body of the message