From owner-freebsd-current  Fri May 25 19:22:13 2001
Delivered-To: freebsd-current@freebsd.org
Received: from bazooka.unixfreak.org (bazooka.unixfreak.org [63.198.170.138])
	by hub.freebsd.org (Postfix) with ESMTP
	id A976537B424; Fri, 25 May 2001 19:22:10 -0700 (PDT)
	(envelope-from dima@unixfreak.org)
Received: from hornet.unixfreak.org (hornet [63.198.170.140])
	by bazooka.unixfreak.org (Postfix) with ESMTP
	id CA0203E2F; Fri, 25 May 2001 19:22:09 -0700 (PDT)
To: current@freebsd.org
Cc: alfred@freebsd.org
Subject: vm_pager_(de)allocate and vm_mtx
Date: Fri, 25 May 2001 19:22:09 -0700
From: Dima Dorfman <dima@unixfreak.org>
Message-Id: <20010526022209.CA0203E2F@bazooka.unixfreak.org>
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?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

Is there a reason vm_pager_allocate acquires vm_mtx itself if
necessary but vm_pager_deallocate does not?  At the moment, detaching
an md(4) disk will panic the system with a failed mtx_assert in
vm_pager_deallocate.  This can be fixed one of two ways:
vm_pager_deallocate could be made to deal with vm_mtx itself like
vm_pager_allocate does, or md(4) and any other drivers which call
vm_pager_deallocate can be fixed to acquire vm_mtx.  So which will it
be?  I'll supply patches for either case.

Thanks,

					Dima Dorfman
					dima@unixfreak.org


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