Date: Wed, 28 Feb 2001 12:30:56 -0800 (PST) From: John Baldwin <jhb@FreeBSD.org> To: Michael Reifenberger <root@nihil.plaut.de> Cc: FreeBSD-Current <current@FreeBSD.org> Subject: RE: lock order reversal under -current Message-ID: <XFMail.010228123056.jhb@FreeBSD.org> In-Reply-To: <Pine.BSF.4.31.0102281011360.365-100000@nihil>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <jhb@FreeBSD.org> -- 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.010228123056.jhb>