From owner-freebsd-net@FreeBSD.ORG  Tue Jul 31 20:42:07 2007
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
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 7363016A417;
	Tue, 31 Jul 2007 20:42:07 +0000 (UTC)
	(envelope-from csjp@sub.vaned.net)
Received: from sub.vaned.net (sub.vaned.net [205.200.235.40])
	by mx1.freebsd.org (Postfix) with ESMTP id 3F67F13C45E;
	Tue, 31 Jul 2007 20:42:07 +0000 (UTC)
	(envelope-from csjp@sub.vaned.net)
Received: by sub.vaned.net (Postfix, from userid 1001)
	id 93FF15C3B; Tue, 31 Jul 2007 15:41:56 -0500 (CDT)
Date: Tue, 31 Jul 2007 15:41:56 -0500
From: "Christian S.J. Peron" <csjp@FreeBSD.org>
To: "Bruce M. Simpson" <bms@incunabulum.net>
Message-ID: <20070731204156.GA7614@sub>
References: <20070731162515.GA3684@sub> <46AF7E57.5020209@incunabulum.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <46AF7E57.5020209@incunabulum.net>
User-Agent: Mutt/1.4.2.2i
Cc: freebsd-net@freebsd.org, rwatson@freebsd.org,
	"Christian S.J. Peron" <csjp@FreeBSD.org>
Subject: Re: divert and deadlock issues
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Jul 2007 20:42:07 -0000

On Tue, Jul 31, 2007 at 07:24:23PM +0100, Bruce M. Simpson wrote:
[..]
> 
> The LOR is obviously being triggered by ip_output()'s acquisition of 
> in_multi_mtx, due to a datagram being sent to a multicast destination 
> and a subsequent lookup being required.
> 

This makes sense.

> I can't think of a reason why a user would wish to supply any multicast 
> socket options to a divert socket, other than the 'small' ones, i.e. 
> IP_MULTICAST_TTL/IF/LOOP/VIF.
> 

Why would these options ever be set on the divert socket itself though?
To me it would make sense if these options were set on the network
socket that originally sent the multicast packet itself.

-- 
Christian S.J. Peron
csjp@FreeBSD.ORG
FreeBSD Committer