kernel/git/stable/linux.git/include/net/sctp, branch linux-2.6.22.y

[SCTP] Flag a pmtu change request

2007-06-13T20:44:42+00:00

Currently, if the socket is owned by the user, we drop the ICMP message. As a result SCTP forgets that path MTU changed and never adjusting it's estimate. This causes all subsequent packets to be fragmented. With this patch, we'll flag the association that it needs to udpate it's estimate based on the already updated routing information. Signed-off-by: Vlad Yasevich Acked-by: Sridhar Samudrala

[SCTP] Update pmtu handling to be similar to tcp

2007-06-13T20:44:42+00:00

Introduce new function sctp_transport_update_pmtu that updates the transports and destination caches view of the path mtu. Signed-off-by: Vlad Yasevich Acked-by: Sridhar Samudrala

[SCTP]: Set assoc_id correctly during INIT collision.

2007-05-04T20:55:27+00:00

During the INIT/COOKIE-ACK collision cases, it's possible to get into a situation where the association id is not yet set at the time of the user event generation. As a result, user events have an association id set to 0 which will confuse applications. This happens if we hit case B of duplicate cookie processing. In the particular example found and provided by Oscar Isaula , flow looks like this: A B ---- INIT-------> (lost) <---------INIT------ ---- INIT-ACK---> <------ Cookie ECHO When the Cookie Echo is received, we end up trying to update the association that was created on A as a result of the (lost) INIT, but that association doesn't have the ID set yet. Signed-off-by: Vlad Yasevich Signed-off-by: David S. Miller

[SCTP]: Re-order SCTP initializations to avoid race with sctp_rcv()

2007-05-04T20:36:30+00:00

Signed-off-by: Sridhar Samudrala Signed-off-by: Vlad Yasevich Signed-off-by: David S. Miller

[SCTP]: Implement SCTP_MAX_BURST socket option.

2007-04-26T05:28:04+00:00

Signed-off-by: Vlad Yasevich Signed-off-by: David S. Miller

[SCTP]: Implement sac_info field in SCTP_ASSOC_CHANGE notification.

2007-04-26T05:28:03+00:00

As stated in the sctp socket api draft: sac_info: variable If the sac_state is SCTP_COMM_LOST and an ABORT chunk was received for this association, sac_info[] contains the complete ABORT chunk as defined in the SCTP specification RFC2960 [RFC2960] section 3.3.7. We now save received ABORT chunks into the sac_info field and pass that to the user. Signed-off-by: Vlad Yasevich Signed-off-by: David S. Miller

[SCTP]: Honor flags when setting peer address parameters

2007-04-26T05:28:02+00:00

Parameters only take effect when a corresponding flag bit is set and a value is specified. This means we need to check the flags in addition to checking for non-zero value. Signed-off-by: Vlad Yasevich Signed-off-by: David S. Miller

[SCTP]: Implement SCTP_ADDR_CONFIRMED state for ADDR_CHNAGE event

2007-04-26T05:28:01+00:00

Signed-off-by: Vlad Yasevich Signed-off-by: David S. Miller

[SCTP]: Implement SCTP_PARTIAL_DELIVERY_POINT option.

2007-04-26T05:28:00+00:00

This option induces partial delivery to run as soon as the specified amount of data has been accumulated on the association. However, we give preference to fully reassembled messages over PD messages. In any case, window and buffer is freed up. Signed-off-by: Vlad Yasevich Signed-off-by: David S. Miller

[SCTP]: Implement SCTP_FRAGMENT_INTERLEAVE socket option

2007-04-26T05:27:59+00:00

This option was introduced in draft-ietf-tsvwg-sctpsocket-13. It prevents head-of-line blocking in the case of one-to-many endpoint. Applications enabling this option really must enable SCTP_SNDRCV event so that they would know where the data belongs. Based on an earlier patch by Ivan Skytte Jørgensen. Additionally, this functionality now permits multiple associations on the same endpoint to enter Partial Delivery. Applications should be extra careful, when using this functionality, to track EOR indicators. Signed-off-by: Vlad Yasevich Signed-off-by: David S. Miller