From: David Woodhouse <dwmw2@infradead.org>
To: netdev@oss.sgi.com, marcelo.tosatti@cyclades.com
Cc: lksctp-developers@lists.sourceforge.net
Subject: SCTP sockopt discrepancy between 2.4 and 2.6.
Date: Mon, 02 Feb 2004 18:43:03 +0000 [thread overview]
Message-ID: <1075747382.786.366.camel@hades.cambridge.redhat.com> (raw)
The 2.4 and 2.6 SCTP code have _different_ values for the SCTP_*
sockopts. The 2.4 version claims to implement
draft-ietf-tsvwg-sctpsocket-04.txt while the 2.6 version implements
draft-ietf-tsvwg-sctpsocket-07.txt.
This means that tools compiled with the current libraries and header
files cannot work on the 2.4 kernel.
Am I missing something -- like perhaps the existence of a patch to
update the 2.4 kernel -- or is the SCTP implementation in 2.4 no longer
being maintained, and no longer compatible with 2.6 and its userspace?
--
dwmw2
next reply other threads:[~2004-02-02 18:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-02 18:43 David Woodhouse [this message]
2004-02-02 19:03 ` SCTP sockopt discrepancy between 2.4 and 2.6 David S. Miller
2004-02-02 19:09 ` Sridhar Samudrala
2004-02-02 19:21 ` David S. Miller
2004-02-03 18:13 ` Sridhar Samudrala
2004-02-03 18:19 ` David S. Miller
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=1075747382.786.366.camel@hades.cambridge.redhat.com \
--to=dwmw2@infradead.org \
--cc=lksctp-developers@lists.sourceforge.net \
--cc=marcelo.tosatti@cyclades.com \
--cc=netdev@oss.sgi.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.
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).