From: Rick Jones <rick.jones2@hp.com>
To: Linux Network Development list <netdev@vger.kernel.org>
Subject: getaddrinfo - should accept IPPROTO_SCTP no?
Date: Fri, 13 Oct 2006 14:30:12 -0700 [thread overview]
Message-ID: <45300564.2050504@hp.com> (raw)
I made some recent changes to netperf to workaround what is IMO a bug in the
Solaris getaddrinfo() where it will clear the ai_protocol field even when one
gives it a protocol in the hints.
[If you happen to be trying to use the test-specific -D to set TCP_NODELAY in
netperf on Solaris, you might want to grab netperf TOT to get this workaround as
it relates to issues with setting TCP_NODELAY - modulo what it will do to being
able to run the netperf SCTP tests on Linux...]
In the process though I have stumbled across what appears to be a bug (?) in
"Linux" getaddrinfo() - returning a -7 EAI_SOCKTYPE if given as hints
SOCK_STREAM and IPPROTO_SCTP - this on a system that ostensibly supports SCTP.
I've seen this on RHAS4U4 as well as another less well known distro.
I'm about to see about concocting an additional workaround in netperf for this,
but thought I'd ask if my assumption - that getaddrinfo() returning -7 when
given IPPROTO_SCTP - is indeed a bug in getaddrinfo(). Or am I just woefully
behind in patches or completely offbase on what is correct behaviour for
getaddrinfo and hints?
FWIW, which may not be much, Solaris 10 06/06 seems content to accept
IPPROTO_SCTP in the hints.
thanks,
rick jones
http://www.netperf.org/svn/netperf2/trunk/
next reply other threads:[~2006-10-13 21:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-13 21:30 Rick Jones [this message]
2006-10-13 22:09 ` getaddrinfo - should accept IPPROTO_SCTP no? David Miller
2006-10-14 0:00 ` Sridhar Samudrala
2006-10-13 22:59 ` Ian McDonald
2006-10-13 23:48 ` Rick Jones
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=45300564.2050504@hp.com \
--to=rick.jones2@hp.com \
--cc=netdev@vger.kernel.org \
/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.
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).