From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: linux-sctp@vger.kernel.org
Subject: Re: [Lksctp-developers] [RFC PATCH] [SCTP]: Support the new specification
Date: Tue, 01 Apr 2008 21:46:54 +0000 [thread overview]
Message-ID: <47F2AD4E.8000203@hp.com> (raw)
Ivan Skytte Jørgensen wrote:
> On Friday 28 March 2008 20:54:38 Vlad Yasevich wrote:
>> The specification of sctp_connectx() has been changed to return
>> an association id. Sence it is guaranteed the association id will
>> be a positive 32 bit integer, we can simply return that from our
>> setsockopt() in the case of success. The library that implements
>> sctp_connectx() will re-interpret the call.
>
> Partial NAK.
>
> It breaks old versions of lksctp. I am not aware that we previously have
> required lksctp to match the kernel exactly unless there was no other way.
>
> A new sockopt is safer.
>
> /isj
In what way? The only possible problem is that sctp_connectx()
can return a positive value on success in addition to 0, depending
on which kernel is used.
How much of a problem is this really?
A new socket option is actually problematic as well, because the
behavior will depend on the system that lksctp libraries are built
on.
So, I am not sure which tradeoff is better...
-vlad
next reply other threads:[~2008-04-01 21:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-01 21:46 Vlad Yasevich [this message]
2008-04-01 22:42 ` [Lksctp-developers] [RFC PATCH] [SCTP]: Support the new specification of sctp Ivan Skytte Jørgensen
2008-04-02 15:50 ` [Lksctp-developers] [RFC PATCH] [SCTP]: Support the new specification Vlad Yasevich
2008-04-11 19:56 ` Vlad Yasevich
2008-04-12 11:11 ` [Lksctp-developers] [RFC PATCH] [SCTP]: Support the new specification of sctp_connectx() Ivan Skytte Jørgensen
2008-04-14 1:13 ` [Lksctp-developers] [RFC PATCH] [SCTP]: Support the new specification Vlad Yasevich
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=47F2AD4E.8000203@hp.com \
--to=vladislav.yasevich@hp.com \
--cc=linux-sctp@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.