From owner-freebsd-current  Tue Sep 18 10:53:56 2001
Delivered-To: freebsd-current@freebsd.org
Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193])
	by hub.freebsd.org (Postfix) with ESMTP id 9B4CC37B419
	for <current@FreeBSD.org>; Tue, 18 Sep 2001 10:53:53 -0700 (PDT)
Received: (from wollman@localhost)
	by khavrinen.lcs.mit.edu (8.11.4/8.11.4) id f8IHrqb52417;
	Tue, 18 Sep 2001 13:53:52 -0400 (EDT)
	(envelope-from wollman)
Date: Tue, 18 Sep 2001 13:53:52 -0400 (EDT)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <200109181753.f8IHrqb52417@khavrinen.lcs.mit.edu>
To: current@FreeBSD.org
Subject: Seen this lock order reversal?
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

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.)

-GAWollman


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message