summaryrefslogtreecommitdiffstats
path: root/sys/netinet/sctp_indata.c
Commit message (Collapse)AuthorAgeFilesLines
* MFC r292558:tuexen2016-01-171-0/+1
| | | | Stop processing of a SACK when the association has been aborted.
* MFC r291700:tuexen2016-01-171-0/+15
| | | | Ensure that outgoing streams get reset when they run dry.
* MFC r290468:tuexen2016-01-161-1/+1
| | | | Use the correct length. The wrong one was too large.
* MFC r290442:tuexen2016-01-161-8/+8
| | | | | | Fix typos in field names of struct sctp_extrcvinfo. Provide defines to allow applications to compile. Thanks to Jens Hoelscher for making me aware of the typos.
* MFC r287717:tuexen2016-01-161-39/+25
| | | | | | Cleanup the handling of error causes for ERROR chunks. This fixes an inconsistency of the padding handling. The final padding is now considered to be a chunk padding.
* MFC r287669:tuexen2016-01-161-5/+1
| | | | | | | Ensure that ERROR chunks are always padded by implementing this in the routine, which queues an ERROR chunk, instead on relyinh on the callers to do so. Since one caller missed this, this actially fixes a bug.
* MFC r286206:tuexen2016-01-161-19/+5
| | | | | Don't take the port numbers for packets containing ABORT chunks from a freed mbuf. Just use them from the stcb.
* MFC r285938:tuexen2016-01-161-1/+1
| | | | Fix a typo reported by Erik Cederstrand.
* MFC r285925:tuexen2016-01-161-1/+4
| | | | Provide consistent error causes whenever an ABORT chunk is sent.
* MFC r285887:tuexen2016-01-161-2/+25
| | | | | Improve locking on Mac OS X. This does not change the functionality on FreeBSD.
* MFC r285886:tuexen2016-01-161-4/+4
| | | | Fix and improve a debug message. The SID was reported as an SSN.
* MFC r285792:tuexen2016-01-161-0/+1
| | | | | | | | Fix several problems with Stream Reset. 1) We were not handling (or sending) the IN_PROGRESS case if the other side (or our side) was not able to reset (awaiting more data). 2) We would improperly send a stream-reset when we should not. Not waiting until the TSN had been assigned when data was inqueue.
* MFC r283650:tuexen2015-05-311-28/+34
| | | | | Fix and cleanup the debug information. This has no user-visible changes. Thanks to Irene Ruengeler for proving a patch.
* MFC r283648:tuexen2015-05-311-3/+9
| | | | Address some compiler warnings. No functional change.
* MFC r282042:tuexen2015-05-291-9/+2
| | | | | | Don't panic under INVARIANTS when receiving a SACK which cumacks a TSN never sent. While there, fix two typos.
* MFC r280440:tuexen2015-05-291-3/+5
| | | | | | Fix the bug in the handling of fragmented abandoned SCTP user messages reported in https://code.google.com/p/sctp-refimpl/issues/detail?id=11 Thanks to Lally Singh for reporting it.
* MFC r276914:tuexen2015-05-291-7/+1
| | | | | Minimize the usage of SCTP_BUF_IS_EXTENDED. This should help Robert...
* MFC r275358 r275483 r276982 - Removing M_FLOWID by hps@hiren2015-04-241-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | r275358: Start process of removing the use of the deprecated "M_FLOWID" flag from the FreeBSD network code. The flag is still kept around in the "sys/mbuf.h" header file, but does no longer have any users. Instead the "m_pkthdr.rsstype" field in the mbuf structure is now used to decide the meaning of the "m_pkthdr.flowid" field. To modify the "m_pkthdr.rsstype" field please use the existing "M_HASHTYPE_XXX" macros as defined in the "sys/mbuf.h" header file. This patch introduces new behaviour in the transmit direction. Previously network drivers checked if "M_FLOWID" was set in "m_flags" before using the "m_pkthdr.flowid" field. This check has now now been replaced by checking if "M_HASHTYPE_GET(m)" is different from "M_HASHTYPE_NONE". In the future more hashtypes will be added, for example hashtypes for hardware dedicated flows. "M_HASHTYPE_OPAQUE" indicates that the "m_pkthdr.flowid" value is valid and has no particular type. This change removes the need for an "if" statement in TCP transmit code checking for the presence of a valid flowid value. The "if" statement mentioned above is now a direct variable assignment which is then later checked by the respective network drivers like before. r275483: Remove M_FLOWID from SCTP code. r276982: Remove no longer used "M_FLOWID" flag from mbuf.h and update the netisr manpage. Note: The FreeBSD version has been bumped. Reviewed by: hps, tuexen Sponsored by: Limelight Networks
* MFC r269448:tuexen2014-08-221-7/+7
| | | | | | Add support for the SCTP_PR_SUPPORTED socket option as specified in http://tools.ietf.org/html/draft-ietf-tsvwg-sctp-prpolicies Add also a sysctl controlling the default of the end-points.
* MFC r269376:tuexen2014-08-221-1/+1
| | | | | Cleanup sctp_send_initiate() and sctp_send_initiate_ack() to be in sync as much as possible. This simplifies upcoming changes.
* Fix kernel memory disclosure in control message and SCTP notifications.delphij2014-07-081-0/+5
| | | | | Security: FreeBSD-SA-14:17.kmem Security: CVE-2014-3952, CVE-2014-3953
* MFC r264838:tuexen2014-06-221-1/+15
| | | | | | Don't free an mbuf twice. This only happens in very rare error cases where the peer sends illegal sequencing information in DATA chunks for an existing association.
* MFC r264704:tuexen2014-06-221-1/+36
| | | | | Add consistency checks to ensure that fragments of a user message have the same U-bit.
* MFC r264682:tuexen2014-06-221-1/+1
| | | | Use consistently debug output instead of an unconditional printf.
* MFC r264679:tuexen2014-06-221-1/+16
| | | | | Send the correct error cause, when a DATA chunk with no user data is received. This bug was reported by Irene Ruengeler.
* MFC r263237:tuexen2014-06-221-491/+153
| | | | | | | | | | * Provide information in error causes in ASCII instead of proprietary binary format. * Add support for a diagnostic information error cause. The code is sysctlable and the default is 0, which means it is not sent. This is joint work with rrs@.
* MFC r256556:tuexen2013-11-211-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Remove a buggy comparision when setting manually the path MTU. After fixing, the comparision would have become redundant. Thanks to Andrew Galante for reporting the issue. MFC r257272: Fix compilation if SCTP_DONT_DO_PRIVADDR_SCOPE is defined. The issue was reported by Andrew Galante. MFC r257274: Fix the value of *optlen when calling getsockopt() for SCTP_REMOTE_UDP_ENCAPS_PORT. This issue was reported by Andrew Galante. MFC r257359: Terminate a debug output with a \n. MFC r257555: Changes from upstream to improve compilation when INET or INET6 or none of them is defined. MFC r257574: Unlock the lock before destroying it. This issue was reported by Andrew Galante. MFC r257800: Use htons()/ntohs() appropriately. These issues were reported by Andrew Galante. MFC r257803: Make sure that we don't try to build an ASCONF-ACK chunk larger than what fits in the the mbuf cluster. This issue was reported by Andrew Galante. MFC r257804: Get rid of the artification limitation enforced by SCTP_AUTH_RANDOM_SIZE_MAX. This was suggested by Andrew Galante. MFC r258221: Cleanups which result in fixes which have been made upstream and where partially suggested by Andrew Galante. There is no functional change in FreeBSD. MFC r258224: When determining if an address belongs to an stcb, take the address family into account for wildcard bound endpoints. MFC r258228: Remove a stray write operation. MFC r258235: Use SCTP_PR_SCTP_TTL when the user provides a positive timetolive in sctp_sendmsg(). Approved by: re@
* When computing the partial delivery point, take thetuexen2013-09-071-3/+2
| | | | | | receiver socket buffer size correctly into account. MFC after: 1 week
* Remove redundant field pr_sctp_on.tuexen2013-09-031-1/+1
| | | | MFC after: 1 week
* Make the features a 64-bit value instead of 32-bit.tuexen2013-08-121-1/+0
| | | | | | | | This will allow an easier integration of the support for NDATA. While there, do also some minor cleanups. Obtained from: rrs@ MFC after: 2 weeks
* Code cleanups.tuexen2013-07-031-2/+0
| | | | MFC after: 3 days
* Don't send kernel provided information in the User Initiatedtuexen2013-02-111-12/+4
| | | | | | | | | | | ABORT cause, since the user can also provide this kind of information. So the receiver doesn't know who provided the information. While there: Fix a bug where the stack would send a malformed ABORT chunk when using a send() call with SCTP_ABORT|SCT_SENDALL flags. MFC after: 3 days
* Fix a bug where HEARTBEATs were still sent in SHUTDOWN_SENT ortuexen2013-02-091-17/+17
| | | | | | | SHUTDOWN_ACK_SENT state. While there, make the corresponding code consistent. MFC after: 1 week
* Mechanically substitute flags from historic mbuf allocator withglebius2012-12-051-29/+29
| | | | | | | | | malloc(9) flags within sys. Exceptions: - sys/contrib not touched - sys/mbuf.h edited manually
* Get the accounting working. We now have counters how manytuexen2012-11-161-11/+19
| | | | | | | | | chunks for each SCTP outgoing stream are in the send and sent queue. While there, improve the naming of NR-SACK related constants recently introduced. MFC after: 1 week
* Add per outgoing stream accounting for chunks in the sendtuexen2012-11-071-5/+17
| | | | | | | | and sent queue. This provides no functional change, but is a preparation for an upcoming stream reset improvement. Done with rrs@. MFC after: 1 week
* Add some missing changes missed in the last commit.tuexen2012-11-071-3/+5
| | | | | MFC after: 1 week X-MFC with: 242708
* Improve PR-SCTP if used in combination with NR-SACK.tuexen2012-11-071-2/+5
| | | | | | Based on work done by Mohammad Rajiullah. MFC after: 1 week
* Don't include a structure containing a flexible array in anothertuexen2012-09-071-1/+1
| | | | | | structure. MFC after: 10 days
* Using %p in a format string requires a void *.tuexen2012-09-051-1/+1
| | | | MFC after: 10 days
* Pass the src and dst address of a received packet explicitly around.tuexen2012-06-281-2/+4
| | | | MFC after: 3 days
* Whitespace cleanup.tuexen2012-06-251-8/+8
| | | | MFC after: 3 days
* Pass the packet length explicitly around.tuexen2012-06-241-1/+1
| | | | MFC after: 3 days
* Pass flowid explicitly through the stack instead of taking it fromtuexen2012-06-141-4/+12
| | | | | | | the mbuf chain at different places. While there: Fix several bugs related to VRFs. MFC after: 3 days
* Use consistent text at the begining of the files.tuexen2012-05-231-4/+2
| | | | MFC after: 3 days
* Provide in the SCTP_SEND_FAILED and SCTP_SEND_FAILED_EVENT notificationstuexen2012-05-131-6/+3
| | | | | | the correct ssf_error or ssfe_error as required by RFC 6458. MFC after: 3 days
* Provide the error code in SCTP_PEER_ADDR_CHANGE notifications astuexen2012-05-131-2/+2
| | | | | | specified in RFC 6458. MFC after: 3 days
* Provide in the association change notification the received ABORT chunktuexen2012-05-121-52/+23
| | | | | | if case of SCTP_COMM_LOST or SCTP_CANT_STR_ASSOC as required by RFC 6458. MFC after: 3 days
* Use SCTP_PRINTF() instead of printf() in all SCTP sources.tuexen2012-05-041-18/+18
| | | | MFC after: 3 days
* Fix a bug where we copy out more data from a mbuf chain that aretuexen2012-04-191-4/+6
| | | | | | | | | actually in it. This happens when SCTP receives an unknown chunk, which requires the sending of an ERROR chunk, and there is no final padding but the chunk is not 4-byte aligned. Reported by yueting via rwatson@ MFC after: 3 days
OpenPOWER on IntegriCloud