From owner-freebsd-current Wed Feb 28 12:34:46 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 6C84D37B719 for ; Wed, 28 Feb 2001 12:34:41 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f1SKRNl23390; Wed, 28 Feb 2001 12:27:23 -0800 (PST) (envelope-from jhb@FreeBSD.org) 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: Date: Wed, 28 Feb 2001 12:30:56 -0800 (PST) From: John Baldwin To: Michael Reifenberger Subject: RE: lock order reversal under -current Cc: FreeBSD-Current Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28-Feb-01 Michael Reifenberger wrote: > Hi, > with -current sources (as of -now) I get during startup: > > lock order reversal > 1st vnode interlock last acquired @ ../../kern/vfs_vnops.c:625 > 2nd 0xc0306840 mntvnode @ ../../ufs/ffs/ffs_vfsops.c:940 > 3rd 0xcbd20a0c vnode interlock @ ../../ufs/ffs/ffs_vfsops.c:949 > 32 > > Is that bad? Yes and no. It's a bug yes, but it has probably been around since at least 4.4BSD, so you can ignore it for now. -- 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