From owner-freebsd-standards@FreeBSD.ORG  Mon Jul  7 17:11:06 2014
Return-Path: <owner-freebsd-standards@FreeBSD.ORG>
Delivered-To: freebsd-standards@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id D37396AB
 for <freebsd-standards@FreeBSD.org>; Mon,  7 Jul 2014 17:11:06 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id BAC322B1B
 for <freebsd-standards@FreeBSD.org>; Mon,  7 Jul 2014 17:11:06 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s67HB6I4034701
 for <freebsd-standards@FreeBSD.org>; Mon, 7 Jul 2014 18:11:06 +0100 (BST)
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-standards@FreeBSD.org
Subject: [Bug 191586] FreeBSD doesn't validate negative edgecases in
 bind(2)/connect(2)/listen(2) like POSIX requires
Date: Mon, 07 Jul 2014 17:11:06 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: standards
X-Bugzilla-Version: 11.0-CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: lambert.tr@gmail.com
X-Bugzilla-Status: In Discussion
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-standards@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-191586-15-afXe3vLdGJ@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-191586-15@https.bugs.freebsd.org/bugzilla/>
References: <bug-191586-15@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-standards@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: Standards compliance <freebsd-standards.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-standards>, 
 <mailto:freebsd-standards-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-standards/>
List-Post: <mailto:freebsd-standards@freebsd.org>
List-Help: <mailto:freebsd-standards-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-standards>, 
 <mailto:freebsd-standards-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jul 2014 17:11:06 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191586

--- Comment #8 from Terry Lambert <lambert.tr@gmail.com> ---
That's hard for me to answer without the VSX4 test sources in front of me.

I will say that Mac OS X passes the tests, and that Mac OS X comments the test
out, but without a lot of looking at upper level code, I'm still pretty sure
they don't do the meta check I described at a higher level.  Vincent Lubet
(still networking manager at Apple) and more likely, Laurent Dumont (currently
at Akamai) would be able to tell you for sure without groveling through code.

The current Apple code with it "#if 0"'ed is visible here, FWIW:

http://opensource.apple.com/source/xnu/xnu-2422.90.20/bsd/netinet/in_pcb.c

There was no TSD (Test Suite Deficiency) or PIN (Permanent Interpretation) in
this specific area during the Mac OS X UNIX certification process, so no test
failure.


I suspect that this is an area where the standard says what the people on the
Austin Group who are representing Linux via IBM want it to say, and that the
actual tests simply don't test it at all because it would conflict with
existing implementations grandfathered under SVR3/SVR4 derivation rules.

-- 
You are receiving this mail because:
You are the assignee for the bug.