From owner-freebsd-net@FreeBSD.ORG Thu Jul 30 01:26:16 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 089BB106564A for ; Thu, 30 Jul 2009 01:26:16 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id CE5758FC14 for ; Thu, 30 Jul 2009 01:26:15 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from compute2.internal (compute2.internal [10.202.2.42]) by out1.messagingengine.com (Postfix) with ESMTP id 307393BCEF3; Wed, 29 Jul 2009 21:26:15 -0400 (EDT) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute2.internal (MEProxy); Wed, 29 Jul 2009 21:26:15 -0400 X-Sasl-enc: SabJIqKddWXCX1v6f7w3AnL3MhGxFi3bKM0WvlBLq23q 1248917164 Received: from anglepoise.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTPSA id DD27F20FD1; Wed, 29 Jul 2009 21:26:03 -0400 (EDT) Message-ID: <4A70F65D.1040201@incunabulum.net> Date: Thu, 30 Jul 2009 02:24:45 +0100 From: Bruce Simpson User-Agent: Thunderbird 2.0.0.22 (X11/20090725) MIME-Version: 1.0 To: Michael Tuexen References: <30F5F8DF-111B-4931-8AA3-DDD18B3A5AB9@freebsd.org> In-Reply-To: <30F5F8DF-111B-4931-8AA3-DDD18B3A5AB9@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD net mailing list Subject: Re: mld_mtx lock order reversal X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jul 2009 01:26:16 -0000 Michael Tuexen wrote: > Dear all, > > when doing a > ifconfig gif0 down > ifconfig gif0 -tunnel > ifconfig gif0 destroy > I got a the following message on the last command. > Is this a false positive? See comments in mld6.c. Some LOR warnings are unavoidable at the moment because of INET6 locking; the worst culprit is the SCOPE6 lock. Unfortunately I can't do anything about this right now. The LORs themselves should be pretty benign.