Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 07 Jul 2014 17:11:06 +0000
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
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/>

next in thread | previous in thread | raw e-mail | index | archive | help
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.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-191586-15-afXe3vLdGJ>