From owner-freebsd-current@FreeBSD.ORG  Wed Jun 20 11:22:35 2007
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: current@freebsd.org
Delivered-To: freebsd-current@FreeBSD.ORG
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id A2F7D16A469;
	Wed, 20 Jun 2007 11:22:35 +0000 (UTC)
	(envelope-from stefan@fafoe.narf.at)
Received: from viefep15-int.chello.at (viefep18-int.chello.at [213.46.255.22])
	by mx1.freebsd.org (Postfix) with ESMTP id B36DA13C46A;
	Wed, 20 Jun 2007 11:22:34 +0000 (UTC)
	(envelope-from stefan@fafoe.narf.at)
Received: from lizard.fafoe.narf.at ([213.47.85.26]) by viefep17-int.chello.at
	(InterMail vM.7.08.02.00 201-2186-121-20061213) with ESMTP id
	<20070620110710.DCTM8377.viefep17-int.chello.at@lizard.fafoe.narf.at>;
	Wed, 20 Jun 2007 13:07:10 +0200
Received: by lizard.fafoe.narf.at (Postfix, from userid 1001)
	id 78CF9B97A; Wed, 20 Jun 2007 13:07:10 +0200 (CEST)
Date: Wed, 20 Jun 2007 13:07:10 +0200
From: Stefan Farfeleder <stefan@fafoe.narf.at>
To: Daniel Eischen <deischen@freebsd.org>
Message-ID: <20070620110702.GB929@lizard.fafoe.narf.at>
Mail-Followup-To: Daniel Eischen <deischen@freebsd.org>,
	current@freebsd.org
References: <E1I0E3b-0000kk-Ky@clue.co.za> <46765CB9.9020105@incunabulum.net>
	<Pine.GSO.4.64.0706180833080.23884@sea.ntplx.net>
	<4676C30E.7040300@incunabulum.net>
	<Pine.GSO.4.64.0706181344060.24865@sea.ntplx.net>
	<4676C952.5000607@incunabulum.net>
	<4676D168.3050502@incunabulum.net>
	<4678529A.3080308@incunabulum.net>
	<Pine.GSO.4.64.0706191823040.1099@sea.ntplx.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.GSO.4.64.0706191823040.1099@sea.ntplx.net>
User-Agent: Mutt/1.5.15 (2007-04-06)
Cc: current@freebsd.org
Subject: Re: Multicast problems [PATCH]
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jun 2007 11:22:35 -0000

On Tue, Jun 19, 2007 at 06:36:39PM -0400, Daniel Eischen wrote:

>  POSIX states that:
> 
>    o The <sys/socket.h> header shall define the type socklen_t,
>      which is an integer type of width of at least 32 bits; see
>      APPLICATION USAGE.
> 
>  and goes on to state:
> 
>    o The <sys/socket.h> header shall define the unsigned integer
>      type sa_family_t.
> 
>  This seems to imply that our socklen_t should not be an unsigned
>  integer (uint32_t), but a signed integer.  In APPLICATION USAGE,
>  POSIX states:

I don't understand how you come to that conclusion.  Why does not
mentioning whether socklen_t is signed or unsigned imply it should be
signed?

> 
>    To forestall portability problems, it is recommended that
>    applications not use values larger than 23^1 -1 for the
>    socklen_t type.

That just means that those values will wrap to negative values if
socklen_t is a signed integer type.