From owner-freebsd-current@FreeBSD.ORG  Thu Aug  7 21:08:27 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 768A537B41F
	for <current@FreeBSD.org>; Thu,  7 Aug 2003 21:08:25 -0700 (PDT)
Received: from mail26d.sbc-webhosting.com (mail26d.sbc-webhosting.com
	[216.173.237.167])
	by mx1.FreeBSD.org (Postfix) with SMTP id 55B3A43FA3
	for <current@FreeBSD.org>; Thu,  7 Aug 2003 21:08:24 -0700 (PDT)
	(envelope-from alc@imimic.com)
Received: from www.imimic.com (64.143.12.21)4-0189685684;
	Fri,  8 Aug 2003 00:08:08 -0400 (EDT)
Sender: alc@FreeBSD.ORG
Message-ID: <3F332226.B9C7EE2@imimic.com>
Date: Thu, 07 Aug 2003 23:08:06 -0500
From: "Alan L. Cox" <alc@imimic.com>
Organization: iMimic Networking, Inc.
X-Mailer: Mozilla 4.8 [en] (X11; U; Linux 2.4.2 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Kris Kennaway <kris@obsecurity.org>
References: <20030807204641.GC76161@rot13.obsecurity.org>
Content-Type: text/plain; charset=x-user-defined
Content-Transfer-Encoding: 7bit
X-Loop-Detect: 1
cc: alc@FreeBSD.org
cc: current@FreeBSD.org
Subject: Re: LOR (vm_fault.c:286 and vm_kern.c:323)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Aug 2003 04:08:28 -0000

Kris Kennaway wrote:
> 
> I don't think I've seen this i386 traceback before.  Is it harmless as
> well?
> 

Yes.  In general, any LOR involving a system map mutex and a vm object
mutex that has a stack trace looking like

_mtx_lock_flags()
_vm_map_lock()
kmem_malloc()
page_alloc()
slab_zalloc()
uma_zone_slab()
uma_zalloc_internal()
uma_zfree_arg()
...

is not a problem.

Regards,
Alan