From owner-freebsd-current  Tue Jan 30 13:12: 3 2001
Delivered-To: freebsd-current@freebsd.org
Received: from magnesium.net (toxic.magnesium.net [207.154.84.15])
	by hub.freebsd.org (Postfix) with SMTP id 5652337B6A4
	for <current@FreeBSD.org>; Tue, 30 Jan 2001 13:11:20 -0800 (PST)
Received: (qmail 41454 invoked by uid 1142); 30 Jan 2001 21:11:19 -0000
Date: 30 Jan 2001 13:11:19 -0800
Date: Tue, 30 Jan 2001 09:42:07 -0800
From: Jason Evans <jasone@canonware.com>
To: John Hay <jhay@icomtek.csir.co.za>
Cc: current@FreeBSD.org
Subject: Re: lock order reversal message
Message-ID: <20010130094207.E17900@canonware.com>
References: <200101301156.f0UBuQw75143@zibbi.icomtek.csir.co.za>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <200101301156.f0UBuQw75143@zibbi.icomtek.csir.co.za>; from jhay@icomtek.csir.co.za on Tue, Jan 30, 2001 at 01:56:26PM +0200
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Tue, Jan 30, 2001 at 01:56:26PM +0200, John Hay wrote:
> Booting with a kernel built from today's source (with devfs also in),
> I see this lock order reversal message:
> 
> ###################################
> Routing daemons:.
> Doing IPv6 network setup:add net ::ffff:0.0.0.0: gateway ::1
> add net ::0.0.0.0: gateway ::1
> net.inet6.ip6.forwarding: 0 -> 0
> net.inet6.ip6.accept_rtadv: 0 -> 0
> net.inet6.ip6.accept_rtadv: 0 -> 1
> lock order reversal
>  1st vnode interlock last acquired @ ../../kern/vfs_vnops.c:644
>  2nd 0xc02d5280 mntvnode @ ../../ufs/ffs/ffs_vfsops.c:940
>  3rd 0xc85d314c vnode interlock @ ../../ufs/ffs/ffs_vfsops.c:949
> add net fe80::: gateway ::1
> add net ff02::: gateway fe80::2a0:c9ff:fe8d:7c5f%fxp0
> ND default interface = fxp0
>  IPv4 mapped IPv6 address support=YES.
> Additional daemons: syslogd.
> ###################################
> 
> The machine is a SMP box, if that makes a difference. It does not seem
> to cause harm because it continue booting and I can log in.

This shouldn't be a problem.  The lock order reversal has been there for a
long time and hasn't caused any problems, but since simplelocks were used
before, we didn't have any diagnostics to tell us it was there.

Jason


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