From: Geir Ola Vaagland <geirola@gmail.com>
To: netdev@vger.kernel.org
Cc: linux-sctp@vger.kernel.org
Subject: [PATCH net-next 0/6] A step closer to RFC 6458 compliancy
Date: Tue, 17 Jun 2014 17:01:30 +0200 [thread overview]
Message-ID: <1403017296-28469-1-git-send-email-geirola@gmail.com> (raw)
These patches are part of my master thesis project. I have been searching for discrepancies between
the socket API specificiation in RFC 6458 and the current Linux SCTP implementation. The following
patches are my humble attempts at getting somewhat closer to compliancy.
Geir Ola Vaagland (6):
Support for SCTP_RECVRCVINFO socket option
Support for SCTP_RCVINFO ancillary data
Support for SCTP_SNDINFO ancillary data
Support for SCTP_NXTINFO socket option
Support for receiving SCTP_NXTINFO ancillary data
Support for SCTP_DEFAULT_SNDINFO socket option
include/net/sctp/structs.h | 11 +-
include/net/sctp/ulpevent.h | 4 +
include/uapi/linux/sctp.h | 46 ++++++++
net/sctp/socket.c | 260 ++++++++++++++++++++++++++++++++++++++++++--
net/sctp/ulpevent.c | 158 +++++++++++++++++++++++++++
5 files changed, 470 insertions(+), 9 deletions(-)
next reply other threads:[~2014-06-17 15:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-17 15:01 Geir Ola Vaagland [this message]
2014-06-17 15:01 ` [PATCH net-next 1/6] Support for SCTP_RECVRCVINFO socket option Geir Ola Vaagland
2014-06-18 23:30 ` David Miller
2014-06-17 15:01 ` [PATCH net-next 2/6] Support for SCTP_RCVINFO ancillary data Geir Ola Vaagland
2014-06-18 23:30 ` David Miller
2014-06-17 15:01 ` [PATCH net-next 3/6] Support for SCTP_SNDINFO " Geir Ola Vaagland
2014-06-17 15:01 ` [PATCH net-next 4/6] Support for SCTP_NXTINFO socket option Geir Ola Vaagland
2014-06-17 15:01 ` [PATCH net-next 5/6] Support for receiving SCTP_NXTINFO ancillary data Geir Ola Vaagland
2014-06-17 15:01 ` [PATCH net-next 6/6] Support for SCTP_DEFAULT_SNDINFO socket option Geir Ola Vaagland
2014-06-18 23:33 ` David Miller
2014-06-17 15:14 ` [PATCH net-next 0/6] A step closer to RFC 6458 compliancy David Laight
2014-06-17 15:36 ` David Laight
2014-06-17 18:42 ` Vlad Yasevich
2014-06-18 8:42 ` David Laight
2014-06-18 12:43 ` Michael Tuexen
2014-06-18 13:16 ` David Laight
2014-06-18 13:24 ` Michael Tuexen
2014-06-18 13:25 ` Vlad Yasevich
2014-06-18 13:29 ` Michael Tuexen
2014-06-18 13:53 ` David Laight
-- strict thread matches above, loose matches on Subject: below --
2014-06-17 11:57 Geir Ola Vaagland
2014-06-17 12:32 ` David Laight
2014-06-17 13:40 ` 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=1403017296-28469-1-git-send-email-geirola@gmail.com \
--to=geirola@gmail.com \
--cc=linux-sctp@vger.kernel.org \
--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).