From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: Release plans
Date: Sun, 20 Jan 2013 09:01:37 +0100 [thread overview]
Message-ID: <20130120080137.GF27914@port70.net> (raw)
In-Reply-To: <20130119061842.GA3410@brightrain.aerifal.cx>
* Rich Felker <dalias@aerifal.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
next prev parent reply other threads:[~2013-01-20 8:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-19 6:18 Rich Felker
2013-01-19 14:21 ` Strake
2013-01-20 8:01 ` Szabolcs Nagy [this message]
2013-01-25 1:02 ` John Spencer
2013-01-25 1:52 ` Justin Cormack
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130120080137.GF27914@port70.net \
--to=nsz@port70.net \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).