From owner-freebsd-current@FreeBSD.ORG Mon Mar 8 17:23:43 2004 Return-Path: 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 056B616A4CE; Mon, 8 Mar 2004 17:23:42 -0800 (PST) Received: from mtaw4.prodigy.net (mtaw4.prodigy.net [64.164.98.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id A541243D39; Mon, 8 Mar 2004 17:23:42 -0800 (PST) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (4f3c00040d76b15203e4fb87a4e828e9@adsl-67-119-53-203.dsl.lsan03.pacbell.net [67.119.53.203]) by mtaw4.prodigy.net (8.12.10/8.12.10) with ESMTP id i291New8012910; Mon, 8 Mar 2004 17:23:40 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 94F095139C; Mon, 8 Mar 2004 17:23:40 -0800 (PST) Date: Mon, 8 Mar 2004 17:23:40 -0800 From: Kris Kennaway To: Peter Wemm Message-ID: <20040309012340.GB17083@xor.obsecurity.org> References: <20040307184421.GA18871@tin.it> <200403081210.40697.peter@wemm.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mxv5cy4qt+RJ9ypb" Content-Disposition: inline In-Reply-To: <200403081210.40697.peter@wemm.org> User-Agent: Mutt/1.4.2.1i cc: Paolo Pisati cc: freebsd-current@freebsd.org cc: current@freebsd.org Subject: Re: LOR in yesterday CURRENT: system map vs Giant X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Mar 2004 01:23:43 -0000 --mxv5cy4qt+RJ9ypb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Mar 08, 2004 at 12:10:40PM -0800, Peter Wemm wrote: > > I wish it helps... >=20 > This particular one was my fault, I believe it's been fixed. However, I= =20 > also believe this particular LOR happens via other code paths that were= =20 > not my fault. I updated my kernel last night to what I was sure was sources dated after your fix, but I was still seeing it. The system would lock up shortly thereafter, so I had to revert to 5.2.1-R. lock order reversal 1st 0xc103b060 system map (system map) @ vm/vm_map.c:2210 2nd 0xc0725500 Giant (Giant) @ vm/vm_fault.c:1084 Stack backtrace: backtrace(0,ffffffff,c0733520,c0733868,c06fa21c) at backtrace+0x12 witness_checkorder(c0725500,9,c06d2cd4,43c) at witness_checkorder+0x593 _mtx_lock_flags(c0725500,0,c06d2ccb,43c,c1039744) at _mtx_lock_flags+0x67 vm_fault_unwire(c103b000,e86b9000,e86ba000,c103b000,e855dc28) at vm_fault_u= nwire+0x25 vm_map_entry_unwire(c103b000,c1039744) at vm_map_entry_unwire+0x15 vm_map_delete(c103b000,e86b9000,e86ba000,c958bec0,c99fa4ec) at vm_map_delet= e+0x118 vm_map_remove(c103b000,e86b9000,e86ba000,e855dc8c,c067491d) at vm_map_remov= e+0x42 kmem_free(c103b000,e86b9000,1000,c07254c0,0) at kmem_free+0x25 user_ldt_free(c99fc540) at user_ldt_free+0xbd cpu_exit(c99fc540,c99fa3dc,0,c06bda4f,1f8) at cpu_exit+0x2f exit1(c99fc540,0,e855dd40,c0675b13,c99fc540) at exit1+0xd38 exit1(c99fc540,e855dd14,1,9,286) at exit1 syscall(2f,2f,2f,bfbfe89c,bfbfe8ac) at syscall+0x217 Xint0x80_syscall() at Xint0x80_syscall+0x1d --- syscall (1), eip =3D 0x28245163, esp =3D 0xbfbfe848, ebp =3D 0xbfbfe864= --- Kris --mxv5cy4qt+RJ9ypb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFATRycWry0BWjoQKURAocRAKC7NP0uUO9qdZnU9nGkhQoUTHD7agCfbycH M07ZNo5podQEY8qqY6Fsh1s= =i74F -----END PGP SIGNATURE----- --mxv5cy4qt+RJ9ypb--