Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sun, 20 Jan 2013 09:01:37 +0100
From: Szabolcs Nagy <nsz@...t70.net>
To: musl@...ts.openwall.com
Subject: Re: Release plans

* Rich Felker <dalias@...ifal.cx> [2013-01-19 01:18:43 -0500]:
> The remaining agenda items from the previous thread about this release
> cycle are:
> 
> - strverscmp
> - zoneinfo
> - inet_makeaddr
> - scanf %m modifier
> - getifaddrs
> - cpuset/affinity interfaces
> - ether.h interfaces

there is a remaining netinet/tcp.h issue:

SOL_TCP is neither posix, nor bsd, but linux has it
and glibc has it under bsd||svid

opensolaris is supposed to be based on svr4 and it does not
have it either and win sockets use IPPROTO_TCP as well

SOL_TCP well might be a linux accident:
old kernels seem to made a distinction between the socket
level argument of setsockopt and the protocol id in the ip
header, then following bsd the two were made equal, but the
semantic distinction was kept in kernel code
(SOL_SOCKET is an exception, it collides with IPPROTO_ICMP)

http://kernelhistory.sourcentral.org/linux-0.99.14n/S/27.html#L51
vs
http://kernelhistory.sourcentral.org/linux-0.99.14u/S/27.html#L51

thus many linux networking code uses SOL_TCP as setsockopt
argument and that's what strace prints

SO* is reserved for sys/socket.h by posix so we can put SOL_*
there or use feature test macros in tcp.h

Powered by blists - more mailing lists

Your e-mail address:

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.