sctp: update from rfc7829
Subsystems (3)
Xin Long
maintainerv3 cover sctp: update from rfc7829
SCTP-PF was implemented based on a Internet-Draft in 2012:
https://tools.ietf.org/html/draft-nishida-tsvwg-sctp-failover-05
It's been updated quite a few by rfc7829 in 2016.
This patchset adds the following features:
1. add SCTP_ADDR_POTENTIALLY_FAILED notification
2. add pf_expose per netns/sock/asoc
3. add SCTP_EXPOSE_POTENTIALLY_FAILED_STATE sockopt
4. add ps_retrans per netns/sock/asoc/transport (Primary Path Switchover)
5. add spt_pathcpthld for SCTP_PEER_ADDR_THLDS sockopt
v1->v2:
- See Patch 2/5 and Patch 5/5.v2->v3:
- See Patch 1/5, 2/5 and 3/5.
Xin Long (5):
sctp: add SCTP_ADDR_POTENTIALLY_FAILED notification
sctp: add pf_expose per netns and sock and asoc
sctp: add SCTP_EXPOSE_POTENTIALLY_FAILED_STATE sockopt
sctp: add support for Primary Path Switchover
sctp: add SCTP_PEER_ADDR_THLDS_V2 sockopt
include/net/netns/sctp.h | 14 +++++ include/net/sctp/constants.h | 10 +++ include/net/sctp/structs.h | 13 +++- include/uapi/linux/sctp.h | 15 +++++ net/sctp/associola.c | 31 ++++----- net/sctp/protocol.c | 6 ++ net/sctp/sm_sideeffect.c | 5 ++ net/sctp/socket.c | 147 ++++++++++++++++++++++++++++++++++++++----- net/sctp/sysctl.c | 19 ++++++ 9 files changed, 226 insertions(+), 34 deletions(-)
Signature · 1 line
2.1.0
Xin Long
maintainerPATCH v3 1/5 sctp: add SCTP_ADDR_POTENTIALLY_FAILED notification
SCTP Quick failover draft section 5.1, point 5 has been removed from rfc7829. Instead, "the sender SHOULD (i) notify the Upper Layer Protocol (ULP) about this state transition", as said in section 3.2, point 8.
So this patch is to add SCTP_ADDR_POTENTIALLY_FAILED, defined in section 7.1, "which is reported if the affected address becomes PF". Also remove transport cwnd's update when moving from PF back to ACTIVE , which is no longer in rfc7829 either.
v1->v2:
- no changev2->v3:
- define SCTP_ADDR_PF SCTP_ADDR_POTENTIALLY_FAILED
--- include/uapi/linux/sctp.h | 2 ++ net/sctp/associola.c | 17 ++++------------- 2 files changed, 6 insertions(+), 13 deletions(-)
include/uapi/linux/sctp.h +2 -0
@@ -410,6 +410,8 @@ enum sctp_spc_state {SCTP_ADDR_ADDED ,SCTP_ADDR_MADE_PRIM ,SCTP_ADDR_CONFIRMED , +SCTP_ADDR_POTENTIALLY_FAILED , +#define SCTP_ADDR_PF SCTP_ADDR_POTENTIALLY_FAILED };
net/sctp/associola.c +4 -13
@@ -801,14 +801,6 @@ void sctp_assoc_control_transport(struct sctp_association *asoc, spc_state =SCTP_ADDR_CONFIRMED ; else spc_state =SCTP_ADDR_AVAILABLE ; -/* Don't inform ULP about transition from PF to -* active state and set cwnd to 1 MTU, see SCTP -* Quick failover draft section 5.1, point 5 -*/ -if (transport->state =SCTP_PF ) { - ulp_notify = false; - transport->cwnd = asoc->pathmtu; - } transport->state =SCTP_ACTIVE ;break ;
@@ -817,19 +809,18 @@ void sctp_assoc_control_transport(struct sctp_association *asoc,* to inactive state. Also, release the cached route since * there may be a better route next time. */ -if (transport->state !=SCTP_UNCONFIRMED ) +if (transport->state !=SCTP_UNCONFIRMED ) { transport->state =SCTP_INACTIVE ; -else { + spc_state =SCTP_ADDR_UNREACHABLE ; + }else {sctp_transport_dst_release (transport); ulp_notify = false; } - - spc_state =SCTP_ADDR_UNREACHABLE ;break ;case SCTP_TRANSPORT_PF : transport->state =SCTP_PF ; - ulp_notify = false; + spc_state =SCTP_ADDR_POTENTIALLY_FAILED ;break ;default :
Signature · 1 line
2.1.0
Xin Long
maintainerPATCH v3 2/5 sctp: add pf_expose per netns and sock and asoc
As said in rfc7829, section 3, point 12:
The SCTP stack SHOULD expose the PF state of its destination addresses to the ULP as well as provide the means to notify the ULP of state transitions of its destination addresses from active to PF, and vice versa. However, it is recommended that an SCTP stack implementing SCTP-PF also allows for the ULP to be kept ignorant of the PF state of its destinations and the associated state transitions, thus allowing for retention of the simpler state transition model of [RFC4960] in the ULP.
Not only does it allow to expose the PF state to ULP, but also allow to ignore sctp-pf to ULP.
So this patch is to add pf_expose per netns, sock and asoc. And in sctp_assoc_control_transport(), ulp_notify will be set to false if asoc->expose is not set.
It also allows a user to change pf_expose per netns by sysctl, and pf_expose per sock and asoc will be initialized with it.
Note that pf_expose also works for SCTP_GET_PEER_ADDR_INFO sockopt, to not allow a user to query the state of a sctp-pf peer address when pf_expose is not enabled, as said in section 7.3.
v1->v2:
- Fix a build warning noticed by Nathan Chancellor.v2->v3:
- set pf_expose to UNUSED by default to keep compatible with old applications.
--- include/net/netns/sctp.h | 8 ++++++++ include/net/sctp/constants.h | 10 ++++++++++ include/net/sctp/structs.h | 2 ++ include/uapi/linux/sctp.h | 1 + net/sctp/associola.c | 13 ++++++++++--- net/sctp/protocol.c | 3 +++ net/sctp/socket.c | 13 +++++++++++-- net/sctp/sysctl.c | 10 ++++++++++ 8 files changed, 55 insertions(+), 5 deletions(-)
include/net/netns/sctp.h +8 -0
@@ -97,6 +97,14 @@ struct netns_sctp {int pf_enable;/* +* Disable Potentially-Failed state exposure, ignored by default +* pf_expose - 0 : disable pf state exposure +* - 1 : enable pf state exposure +* - 2 : compatible with old applications (by default) +*/ +int pf_expose; + +/* * Policy for preforming sctp/socket accounting * 0 - do socket level accounting, all assocs share sk_sndbuf * 1 - do sctp accounting, each asoc may use sk_sndbuf bytes
include/net/sctp/constants.h +10 -0
@@ -286,6 +286,16 @@ enum { SCTP_MAX_GABS = 16 };* functions simpler to write. */ +/* These are the values for pf exposure, UNUSED is to keep compatible with old +* applications by default. +*/ +enum { +SCTP_PF_EXPOSE_DISABLE , +SCTP_PF_EXPOSE_ENABLE , +SCTP_PF_EXPOSE_UNUSED , +}; +#define SCTP_PF_EXPOSE_MAX SCTP_PF_EXPOSE_UNUSED +/* These return values describe the success or failure of a number of * routines which form the lower interface to SCTP_outqueue. */
include/net/sctp/structs.h +2 -0
@@ -215,6 +215,7 @@ struct sctp_sock {__u32 adaptation_ind;__u32 pd_point; __u16 nodelay:1, + pf_expose:2, reuse:1, disable_fragments:1, v4mapped:1,
@@ -2053,6 +2054,7 @@ struct sctp_association { __u8 need_ecne:1, /* Need to send an ECNE Chunk? */ temp:1, /* Is it a temporary association? */ + pf_expose:2, /* Expose pf state? */ force_delay:1;__u8 strreset_enable;
include/uapi/linux/sctp.h +1 -0
@@ -935,6 +935,7 @@ struct sctp_paddrinfo {enum sctp_spinfo_state {SCTP_INACTIVE ,SCTP_PF , +#define SCTP_POTENTIALLY_FAILED SCTP_PF SCTP_ACTIVE,SCTP_UNCONFIRMED ,SCTP_UNKNOWN =0xffff /* Value used for transport state unknown */
net/sctp/associola.c +10 -3
@@ -86,6 +86,7 @@ static struct sctp_association *sctp_association_init(*/ asoc->max_retrans = sp->assocparams.sasoc_asocmaxrxt; asoc->pf_retrans = sp->pf_retrans; + asoc->pf_expose = sp->pf_expose; asoc->rto_initial =msecs_to_jiffies (sp->rtoinfo.srto_initial); asoc->rto_max =msecs_to_jiffies (sp->rtoinfo.srto_max);
@@ -796,8 +797,11 @@ void sctp_assoc_control_transport(struct sctp_association *asoc,* to heartbeat success, report the SCTP_ADDR_CONFIRMED * state to the user, otherwise report SCTP_ADDR_AVAILABLE. */ -if (SCTP_UNCONFIRMED = transport->state && -SCTP_HEARTBEAT_SUCCESS = error) +if (transport->state =SCTP_PF && + asoc->pf_expose !=SCTP_PF_EXPOSE_ENABLE ) + ulp_notify = false; +else if (transport->state =SCTP_UNCONFIRMED && + error =SCTP_HEARTBEAT_SUCCESS ) spc_state =SCTP_ADDR_CONFIRMED ;else spc_state =SCTP_ADDR_AVAILABLE ;
@@ -820,7 +824,10 @@ void sctp_assoc_control_transport(struct sctp_association *asoc,case SCTP_TRANSPORT_PF : transport->state =SCTP_PF ; - spc_state =SCTP_ADDR_POTENTIALLY_FAILED ; +if (asoc->pf_expose !=SCTP_PF_EXPOSE_ENABLE ) + ulp_notify = false; +else + spc_state =SCTP_ADDR_POTENTIALLY_FAILED ;break ;default :
net/sctp/protocol.c +3 -0
@@ -1220,6 +1220,9 @@ static int __net_init sctp_defaults_init(struct net *net)/* Enable pf state by default */ net->sctp.pf_enable =1 ; +/* Ignore pf exposure feature by default */ + net->sctp.pf_expose =SCTP_PF_EXPOSE_UNUSED ; +/* Association.Max.Retrans - 10 attempts * Path.Max.Retrans - 5 attempts (per destination address) * Max.Init.Retransmits - 8 attempts
net/sctp/socket.c +11 -2
@@ -5041,6 +5041,7 @@ static int sctp_init_sock(struct sock *sk) sp->hbinterval = net->sctp.hb_interval; sp->pathmaxrxt = net->sctp.max_retrans_path; sp->pf_retrans = net->sctp.pf_retrans; + sp->pf_expose = net->sctp.pf_expose; sp->pathmtu =0 ;/* allow default discovery */ sp->sackdelay = net->sctp.sack_timeout; sp->sackfreq =2 ;
@@ -5521,8 +5522,16 @@ static int sctp_getsockopt_peer_addr_info(struct sock *sk, int len, transport =sctp_addr_id2transport (sk, &pinfo.spinfo_address, pinfo.spinfo_assoc_id); -if (!transport) -return -EINVAL ; +if (!transport) { + retval = -EINVAL ; + goto out; + } + +if (transport->state =SCTP_PF && + transport->asoc->pf_expose =SCTP_PF_EXPOSE_DISABLE ) { + retval = -EACCES ; + goto out; + } pinfo.spinfo_assoc_id =sctp_assoc2id (transport->asoc); pinfo.spinfo_state = transport->state;
net/sctp/sysctl.c +1 -0
@@ -34,6 +34,7 @@ static int rto_alpha_min = 0;static int rto_beta_min =0 ;static int rto_alpha_max =1000 ;static int rto_beta_max =1000 ; +static int pf_expose_max =SCTP_PF_EXPOSE_MAX ;static unsigned long max_autoclose_min =0 ; static unsigned long max_autoclose_max @@ -318,6 +319,15 @@ static struct ctl_table sctp_net_table[] = {
.mode = 0644,
.proc_handler = proc_dointvec,
},
+ {
+ .procname = "pf_expose",
+ .data = &init_net.sctp.pf_expose,
+ .maxlen = sizeof(int),
+ .mode = 0644,
+ .proc_handler = proc_dointvec_minmax,
+ .extra1 = SYSCTL_ZERO,
+ .extra2 = &pf_expose_max,
+ },
{ /* sentinel */ }
};
Signature · 1 line
2.1.0
Xin Long
maintainerPATCH v3 3/5 sctp: add SCTP_EXPOSE_POTENTIALLY_FAILED_STATE sockopt
This is a sockopt defined in section 7.3 of rfc7829: "Exposing the Potentially Failed Path State", by which users can change pf_expose per sock and asoc.
v1->v2:
- no change.v2->v3:
- return -EINVAL if params.assoc_value > SCTP_PF_EXPOSE_MAX.
- define SCTP_EXPOSE_PF_STATE SCTP_EXPOSE_POTENTIALLY_FAILED_STATE.
--- include/uapi/linux/sctp.h | 2 ++ net/sctp/socket.c | 79 +++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 81 insertions(+)
include/uapi/linux/sctp.h +2 -0
@@ -137,6 +137,8 @@ typedef __s32 sctp_assoc_t;#define SCTP_ASCONF_SUPPORTED 128#define SCTP_AUTH_SUPPORTED 129#define SCTP_ECN_SUPPORTED 130 +#define SCTP_EXPOSE_POTENTIALLY_FAILED_STATE 131 +#define SCTP_EXPOSE_PF_STATE SCTP_EXPOSE_POTENTIALLY_FAILED_STATE/* PR-SCTP policies */ #define SCTP_PR_SCTP_NONE 0x0000
net/sctp/socket.c +79 -0
103 lines not on this page · raw message
Signature · 1 line
2.1.0
Xin Long
maintainerPATCH v3 4/5 sctp: add support for Primary Path Switchover
This is a new feature defined in section 5 of rfc7829: "Primary Path Switchover". By introducing a new tunable parameter:
Primary.Switchover.Max.Retrans (PSMR)
The primary path will be changed to another active path when the path error counter on the old primary path exceeds PSMR, so that "the SCTP sender is allowed to continue data transmission on a new working path even when the old primary destination address becomes active again".
This patch is to add this tunable parameter, 'ps_retrans' per netns, sock, asoc and transport. It also allows a user to change ps_retrans per netns by sysctl, and ps_retrans per sock/asoc/transport will be initialized with it.
The check will be done in sctp_do_8_2_transport_strike() when this feature is enabled.
Note this feature is disabled by initializing 'ps_retrans' per netns as 0xffff by default, and its value can't be less than 'pf_retrans' when changing by sysctl.
--- include/net/netns/sctp.h | 6 ++++++ include/net/sctp/structs.h | 11 ++++++++--- net/sctp/associola.c | 3 +++ net/sctp/protocol.c | 3 +++ net/sctp/sm_sideeffect.c | 5 +++++ net/sctp/socket.c | 1 + net/sctp/sysctl.c | 9 +++++++++ 7 files changed, 35 insertions(+), 3 deletions(-)
include/net/netns/sctp.h +6 -0
@@ -89,6 +89,12 @@ struct netns_sctp {*/ int pf_retrans; +/* Primary.Switchover.Max.Retrans sysctl value +* taken from: +* https://tools.ietf.org/html/rfc7829 +*/ +int ps_retrans; +/* * Disable Potentially-Failed feature, the feature is enabled by default * pf_enable - 0 : disable pf
include/net/sctp/structs.h +8 -3
@@ -184,7 +184,8 @@ struct sctp_sock {__u32 flowlabel;__u8 dscp; -int pf_retrans; +__u16 pf_retrans; +__u16 ps_retrans;/* The initial Path MTU to use for new associations. */ __u32 pathmtu;
@@ -897,7 +898,9 @@ struct sctp_transport {* and will be initialized from the assocs value. This can be changed * using the SCTP_PEER_ADDR_THLDS socket option */ -int pf_retrans; +__u16 pf_retrans; +/* Used for primary path switchover. */ +__u16 ps_retrans;/* PMTU : The current known path MTU. */ __u32 pathmtu;
@@ -1773,7 +1776,9 @@ struct sctp_association {* and will be initialized from the assocs value. This can be * changed using the SCTP_PEER_ADDR_THLDS socket option */ -int pf_retrans; +__u16 pf_retrans; +/* Used for primary path switchover. */ +__u16 ps_retrans;/* Maximum number of times the endpoint will retransmit INIT */ __u16 max_init_attempts;
net/sctp/associola.c +3 -0
@@ -86,6 +86,7 @@ static struct sctp_association *sctp_association_init(*/ asoc->max_retrans = sp->assocparams.sasoc_asocmaxrxt; asoc->pf_retrans = sp->pf_retrans; + asoc->ps_retrans = sp->ps_retrans; asoc->pf_expose = sp->pf_expose; asoc->rto_initial =msecs_to_jiffies (sp->rtoinfo.srto_initial);
@@ -628,6 +629,8 @@ struct sctp_transport *sctp_assoc_add_peer(struct sctp_association *asoc,/* And the partial failure retrans threshold */ peer->pf_retrans = asoc->pf_retrans; +/* And the primary path switchover retrans threshold */ + peer->ps_retrans = asoc->ps_retrans;/* Initialize the peer's SACK delay timeout based on the * association configured value.
net/sctp/protocol.c +3 -0
@@ -1217,6 +1217,9 @@ static int __net_init sctp_defaults_init(struct net *net)/* Max.Burst - 4 */ net->sctp.max_burst =SCTP_DEFAULT_MAX_BURST ; +/* Disable of Primary Path Switchover by default */ + net->sctp.ps_retrans =0xffff ; +/* Enable pf state by default */ net->sctp.pf_enable =1 ;
net/sctp/sm_sideeffect.c +5 -0
@@ -567,6 +567,11 @@ static void sctp_do_8_2_transport_strike(struct sctp_cmd_seq *commands, SCTP_FAILED_THRESHOLD); } +if (transport->error_count > transport->ps_retrans && + asoc->peer.primary_path = transport && + asoc->peer.active_path != transport) +sctp_assoc_set_primary (asoc, asoc->peer.active_path); +/* E2) For the destination address for which the timer * expires, set RTO <- RTO * 2 ("back off the timer"). The * maximum value discussed in rule C7 above (RTO.max) may be
net/sctp/socket.c +1 -0
@@ -5078,6 +5078,7 @@ static int sctp_init_sock(struct sock *sk) sp->hbinterval = net->sctp.hb_interval; sp->pathmaxrxt = net->sctp.max_retrans_path; sp->pf_retrans = net->sctp.pf_retrans; + sp->ps_retrans = net->sctp.ps_retrans; sp->pf_expose = net->sctp.pf_expose; sp->pathmtu =0 ;/* allow default discovery */ sp->sackdelay = net->sctp.sack_timeout;
net/sctp/sysctl.c +9 -0
@@ -213,6 +213,15 @@ static struct ctl_table sctp_net_table[] = { .mode = 0644, .proc_handler = proc_dointvec_minmax, .extra1 = SYSCTL_ZERO, + .extra2 = &init_net.sctp.ps_retrans, + }, + { + .procname = "ps_retrans", + .data = &init_net.sctp.ps_retrans, + .maxlen = sizeof(int), + .mode = 0644, + .proc_handler = proc_dointvec_minmax, + .extra1 = &init_net.sctp.pf_retrans, .extra2 = SYSCTL_INT_MAX, }, {
Signature · 1 line
2.1.0
Xin Long
maintainerPATCH v3 5/5 sctp: add SCTP_PEER_ADDR_THLDS_V2 sockopt
Section 7.2 of rfc7829: "Peer Address Thresholds (SCTP_PEER_ADDR_THLDS) Socket Option" extends 'struct sctp_paddrthlds' with 'spt_pathcpthld' added to allow a user to change ps_retrans per sock/asoc/transport, as other 2 paddrthlds: pf_retrans, pathmaxrxt.
Note: to not break the user's program, here to support pf_retrans dump and setting by adding a new sockopt SCTP_PEER_ADDR_THLDS_V2, and a new structure sctp_paddrthlds_v2 instead of extending sctp_paddrthlds.
Also, when setting ps_retrans, the value is not allowed to be greater than pf_retrans.
v1->v2:
- use SCTP_PEER_ADDR_THLDS_V2 to set/get pf_retrans instead, as Marcelo and David Laight suggested.v2->v3:
- no change.
--- include/uapi/linux/sctp.h | 10 +++++++++ net/sctp/socket.c | 54 +++++++++++++++++++++++++++++++++++------------ 2 files changed, 50 insertions(+), 14 deletions(-)
include/uapi/linux/sctp.h +10 -0
@@ -105,6 +105,7 @@ typedef __s32 sctp_assoc_t;#define SCTP_DEFAULT_SNDINFO 34#define SCTP_AUTH_DEACTIVATE_KEY 35#define SCTP_REUSE_PORT 36 +#define SCTP_PEER_ADDR_THLDS_V2 37/* Internal Socket Options. Some of the sctp library functions are * implemented using these socket options.
@@ -1087,6 +1088,15 @@ struct sctp_paddrthlds {__u16 spt_pathpfthld; }; +/* Use a new structure with spt_pathcpthld for back compatibility */ +struct sctp_paddrthlds_v2 { +sctp_assoc_t spt_assoc_id; +struct sockaddr_storage spt_address; +__u16 spt_pathmaxrxt; +__u16 spt_pathpfthld; +__u16 spt_pathcpthld; +}; +/* * Socket Option for Getting the Association/Stream-Specific PR-SCTP Status */
net/sctp/socket.c +40 -14
130 lines not on this page · raw message
Signature · 1 line
2.1.0
Quoted 27 lines · Xin Long
SCTP-PF was implemented based on a Internet-Draft in 2012:
https://tools.ietf.org/html/draft-nishida-tsvwg-sctp-failover-05
It's been updated quite a few by rfc7829 in 2016.
This patchset adds the following features:
1. add
SCTP_ADDR_POTENTIALLY_FAILEDnotification
2. addpf_exposeper netns/sock/asoc
3. addSCTP_EXPOSE_POTENTIALLY_FAILED_STATEsockopt
4. addps_retransper netns/sock/asoc/transport (Primary Path Switchover)
5. addspt_pathcpthldforSCTP_PEER_ADDR_THLDSsockopt
v1->v2:
- See Patch 2/5 and Patch 5/5.v2->v3:
- See Patch 1/5, 2/5 and 3/5.Xin Long (5):
sctp: addSCTP_ADDR_POTENTIALLY_FAILEDnotification
sctp: addpf_exposeper netns and sock and asoc
sctp: addSCTP_EXPOSE_POTENTIALLY_FAILED_STATEsockopt
sctp: add support for Primary Path Switchover
sctp: addSCTP_PEER_ADDR_THLDS_V2sockopt
Quoted 15 lines
include/net/netns/sctp.h | 14 +++++ include/net/sctp/constants.h | 10 +++ include/net/sctp/structs.h | 13 +++- include/uapi/linux/sctp.h | 15 +++++ net/sctp/associola.c | 31 ++++----- net/sctp/protocol.c | 6 ++ net/sctp/sm_sideeffect.c | 5 ++ net/sctp/socket.c | 147 ++++++++++++++++++++++++++++++++++++++----- net/sctp/sysctl.c | 19 ++++++ 9 files changed, 226 insertions(+), 34 deletions(-)Signature · 1 line
2.1.0
Series
David Miller
maintainerFrom: Xin Long <[email protected]>
Date: Mon, 14 Oct 2019 14:14:43 +0800
Quoted 6 lines
SCTP-PF was implemented based on a Internet-Draft in 2012:
https://tools.ietf.org/html/draft-nishida-tsvwg-sctp-failover-05
It's been updated quite a few by rfc7829 in 2016.
Quoted 8 lines
This patchset adds the following features:
1. add
SCTP_ADDR_POTENTIALLY_FAILEDnotification
2. addpf_exposeper netns/sock/asoc
3. addSCTP_EXPOSE_POTENTIALLY_FAILED_STATEsockopt
4. addps_retransper netns/sock/asoc/transport (Primary Path Switchover)
5. addspt_pathcpthldforSCTP_PEER_ADDR_THLDSsockopt
I would like to see some SCTP expert ACKs here.
Thank you.
From: David Miller
Quoted 12 lines
Sent: 16 October 2019 01:57
From: Xin Long <[email protected]>
Date: Mon, 14 Oct 2019 14:14:43 +0800Quoted 8 lines
SCTP-PF was implemented based on a Internet-Draft in 2012:
https://tools.ietf.org/html/draft-nishida-tsvwg-sctp-failover-05
It's been updated quite a few by rfc7829 in 2016.
This patchset adds the following features:
Quoted 8 lines
Quoted 6 lines
1. add
SCTP_ADDR_POTENTIALLY_FAILEDnotification
2. addpf_exposeper netns/sock/asoc
3. addSCTP_EXPOSE_POTENTIALLY_FAILED_STATEsockopt
4. addps_retransper netns/sock/asoc/transport (Primary Path Switchover)
5. addspt_pathcpthldforSCTP_PEER_ADDR_THLDSsockoptI would like to see some SCTP expert ACKs here.
I'm only an SCTP user, but I think some of the API changes aren't right. I'm not going to try to grok the sctp code - it makes my brain hurt. (Even though I've written plenty of protocol stack code.)
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK Registration No: 1397386 (Wales)
David Miller
maintainerFrom: Xin Long <[email protected]>
Date: Mon, 14 Oct 2019 14:14:43 +0800
Quoted 7 lines
SCTP-PF was implemented based on a Internet-Draft in 2012:
https://tools.ietf.org/html/draft-nishida-tsvwg-sctp-failover-05
It's been updated quite a few by rfc7829 in 2016.
This patchset adds the following features:
Sorry but I'm tossing these until an knowledgable SCTP person can look at them.
Marcelo Ricardo Leitner
maintainerQuoted 5 lines · David Miller
From: Xin Long <[email protected]>
Date: Mon, 14 Oct 2019 14:14:43 +0800Quoted 2 lines
SCTP-PF was implemented based on a Internet-Draft in 2012:
Quoted 8 lines
Quoted 5 lines
https://tools.ietf.org/html/draft-nishida-tsvwg-sctp-failover-05
It's been updated quite a few by rfc7829 in 2016.
This patchset adds the following features:
Sorry but I'm tossing these until an knowledgable SCTP person can look at them.
Hi Dave,
Maybe the email didn't get through but Neil actually already acked it, 2 days ago.
Message-ID: <[email protected]>
I won't be able to review it :-(
Thanks,
Marcelo
David Miller
maintainerFrom: Marcelo Ricardo Leitner <[email protected]>
Date: Wed, 16 Oct 2019 15:32:09 -0300
Quoted 15 lines · David Miller
Quoted 5 lines
From: Xin Long <[email protected]>
Date: Mon, 14 Oct 2019 14:14:43 +0800Quoted 2 lines
SCTP-PF was implemented based on a Internet-Draft in 2012:
Quoted 8 lines
Quoted 5 lines
https://tools.ietf.org/html/draft-nishida-tsvwg-sctp-failover-05
It's been updated quite a few by rfc7829 in 2016.
This patchset adds the following features:
Sorry but I'm tossing these until an knowledgable SCTP person can look at them.
Quoted 7 lines
Hi Dave,
Maybe the email didn't get through but Neil actually already acked it, 2 days ago.
Message-ID: <[email protected]>I won't be able to review it :-(
All I saw was David Laight replying saying he thought the APIs weren't implemented correctly.
I have to admit that I'm really going to proceed carefully with SCTP API changes because there has been a lot of discussions in the past involving backwards-incompatible things happening.
I'm not saying that is happening here, but my confidence in SCTP API changes is very low.
I want this to sit for a while and Xin can respin and resubmit in a day or two.
Xin Long
maintainerQuoted 21 lines · David Laight
From: David Miller
Quoted 19 lines
Sent: 16 October 2019 01:57
From: Xin Long <[email protected]>
Date: Mon, 14 Oct 2019 14:14:43 +0800Quoted 14 lines
SCTP-PF was implemented based on a Internet-Draft in 2012:
https://tools.ietf.org/html/draft-nishida-tsvwg-sctp-failover-05
It's been updated quite a few by rfc7829 in 2016.
This patchset adds the following features:
1. add
SCTP_ADDR_POTENTIALLY_FAILEDnotification
2. addpf_exposeper netns/sock/asoc
3. addSCTP_EXPOSE_POTENTIALLY_FAILED_STATEsockopt
4. addps_retransper netns/sock/asoc/transport (Primary Path Switchover)
5. addspt_pathcpthldforSCTP_PEER_ADDR_THLDSsockopt
Quoted 3 lines
Quoted 1 line
I would like to see some SCTP expert ACKs here.
I'm only an SCTP user, but I think some of the API changes aren't right.
Hi, David L.
I think you must know quite a few user cases.
Before I repost, can you pls give the exact places where the API changes may not be right as you've already done in v1 and v2, so that I can correct them.
Thanks.
Quoted 9 lines
I'm not going to try to grok the sctp code - it makes my brain hurt. (Even though I've written plenty of protocol stack code.)
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK Registration No: 1397386 (Wales)
RnJvbTogWGluIExvbmcNCj4gU2VudDogMTcgT2N0b2JlciAyMDE5IDA1OjU3DQouLi4NCj4gPiBJ J20gb25seSBhbiBTQ1RQIHVzZXIsIGJ1dCBJIHRoaW5rIHNvbWUgb2YgdGhlIEFQSSBjaGFuZ2Vz IGFyZW4ndCByaWdodC4NCj4gSGksIERhdmlkIEwuDQo+IA0KPiBJIHRoaW5rIHlvdSBtdXN0IGtu b3cgcXVpdGUgYSBmZXcgdXNlciBjYXNlcy4NCj4gDQo+IEJlZm9yZSBJIHJlcG9zdCwgY2FuIHlv dSBwbHMgZ2l2ZSB0aGUgZXhhY3QgcGxhY2VzIHdoZXJlIHRoZSBBUEkNCj4gY2hhbmdlcyBtYXkg bm90IGJlIHJpZ2h0IGFzIHlvdSd2ZSBhbHJlYWR5IGRvbmUgaW4gdjEgYW5kIHYyLCBzbw0KPiB0 aGF0IEkgY2FuIGNvcnJlY3QgdGhlbS4NCg0KSSdsbCB0cnkgdG8gZmluZCB0aW1lIHRvIGxvb2sg bGF0ZXIgdG9kYXkuDQoNCglEYXZpZA0KDQotDQpSZWdpc3RlcmVkIEFkZHJlc3MgTGFrZXNpZGUs IEJyYW1sZXkgUm9hZCwgTW91bnQgRmFybSwgTWlsdG9uIEtleW5lcywgTUsxIDFQVCwgVUsNClJl Z2lzdHJhdGlvbiBObzogMTM5NzM4NiAoV2FsZXMpDQo
RE: [PATCHv3 net-next 1/5] sctp: add SCTP_ADDR_POTENTIALLY_FAILED notification
In reply to Xin LongI've found v3 :-)
But it isn't that much better than v2.
From: Xin Long
Quoted 41 lines
Sent: 14 October 2019 07:15
SCTP Quick failover draft section 5.1, point 5 has been removed from rfc7829. Instead, "the sender SHOULD (i) notify the Upper Layer Protocol (ULP) about this state transition", as said in section 3.2, point 8.So this patch is to add
SCTP_ADDR_POTENTIALLY_FAILED, defined in section 7.1, "which is reported if the affected address becomes PF". Also remove transport cwnd's update when moving from PF back to ACTIVE , which is no longer in rfc7829 either.
v1->v2:
- no changev2->v3:
- defineSCTP_ADDR_PFSCTP_ADDR_POTENTIALLY_FAILEDSigned-off-by Xin Long <[email protected]>--- include/uapi/linux/sctp.h | 2 ++ net/sctp/associola.c | 17 ++++------------- 2 files changed, 6 insertions(+), 13 deletions(-)include/uapi/linux/sctp.h +2
-0@@ -410,6 +410,8 @@ enum sctp_spc_state {SCTP_ADDR_ADDED ,SCTP_ADDR_MADE_PRIM ,SCTP_ADDR_CONFIRMED , +SCTP_ADDR_POTENTIALLY_FAILED , +#define SCTP_ADDR_PF SCTP_ADDR_POTENTIALLY_FAILED };net/sctp/associola.c +0
-0@@ -801,14 +801,6 @@ void sctp_assoc_control_transport(struct sctp_association *asoc, spc_state =SCTP_ADDR_CONFIRMED ;
net/sctp/associola.c void sctp_assoc_control_transport(struct sctp_association *asoc, · line 811
Quoted 10 lines
net/sctp/associola.c +0
-8else spc_state =SCTP_ADDR_AVAILABLE ; -/* Don't inform ULP about transition from PF to -* active state and set cwnd to 1 MTU, see SCTP -* Quick failover draft section 5.1, point 5 -*/ -if (transport->state =SCTP_PF ) { - ulp_notify = false; - transport->cwnd = asoc->pathmtu; - }
This is wrong.
If the old state is PF and the application hasn't exposed PF the event should be ignored.
Quoted 13 lines
net/sctp/associola.c +3
-2transport->state =SCTP_ACTIVE ;break ;@@ -817,19 +809,18 @@ void sctp_assoc_control_transport(struct sctp_association *asoc,* to inactive state. Also, release the cached route since * there may be a better route next time. */ -if (transport->state !=SCTP_UNCONFIRMED ) +if (transport->state !=SCTP_UNCONFIRMED ) { transport->state =SCTP_INACTIVE ; -else { + spc_state =SCTP_ADDR_UNREACHABLE ; + }else {
net/sctp/associola.c void sctp_assoc_control_transport(struct sctp_association *asoc, · line 832
Quoted 10 lines
net/sctp/associola.c +0
-3sctp_transport_dst_release (transport); ulp_notify = false; } - - spc_state =SCTP_ADDR_UNREACHABLE ;break ;case SCTP_TRANSPORT_PF : transport->state =SCTP_PF ; - ulp_notify = false;
Again the event should be supressed if PF isn't exposed.
Quoted 6 lines
net/sctp/associola.c +1
-1+ spc_state =SCTP_ADDR_POTENTIALLY_FAILED ;break ;default : --2.1.0
I also haven't spotted where the test that the application has actually enabled state transition events is in the code.
I'd have thought it would be anything is built and allocated.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK Registration No: 1397386 (Wales)
Xin Long
maintainerRe: [PATCHv3 net-next 1/5] sctp: add SCTP_ADDR_POTENTIALLY_FAILED notification
Quoted 2 lines · David Laight
I've found v3 :-)
ah okay. sorry.
Quoted 50 lines
But it isn't that much better than v2.
From: Xin Long
Quoted 47 lines
Sent: 14 October 2019 07:15
SCTP Quick failover draft section 5.1, point 5 has been removed from rfc7829. Instead, "the sender SHOULD (i) notify the Upper Layer Protocol (ULP) about this state transition", as said in section 3.2, point 8.So this patch is to add
SCTP_ADDR_POTENTIALLY_FAILED, defined in section 7.1, "which is reported if the affected address becomes PF". Also remove transport cwnd's update when moving from PF back to ACTIVE , which is no longer in rfc7829 either.
v1->v2:
- no changev2->v3:
- defineSCTP_ADDR_PFSCTP_ADDR_POTENTIALLY_FAILEDSigned-off-by Xin Long <[email protected]>--- include/uapi/linux/sctp.h | 2 ++ net/sctp/associola.c | 17 ++++------------- 2 files changed, 6 insertions(+), 13 deletions(-)include/uapi/linux/sctp.h +2
-0@@ -410,6 +410,8 @@ enum sctp_spc_state {SCTP_ADDR_ADDED ,SCTP_ADDR_MADE_PRIM ,SCTP_ADDR_CONFIRMED , +SCTP_ADDR_POTENTIALLY_FAILED , +#define SCTP_ADDR_PF SCTP_ADDR_POTENTIALLY_FAILED };net/sctp/associola.c +0
-4@@ -801,14 +801,6 @@ void sctp_assoc_control_transport(struct sctp_association *asoc, spc_state =SCTP_ADDR_CONFIRMED ; else spc_state =SCTP_ADDR_AVAILABLE ; -/* Don't inform ULP about transition from PF to -* active state and set cwnd to 1 MTU, see SCTP -* Quick failover draft section 5.1, point 5 -*/
Quoted 8 lines
net/sctp/associola.c void sctp_assoc_control_transport(struct sctp_association *asoc, · line 811
Quoted 4 lines
net/sctp/associola.c +0
-4-if (transport->state ==SCTP_PF ) { - ulp_notify = false; - transport->cwnd = asoc->pathmtu; - }This is wrong.
If the old state is PF and the application hasn't exposed PF the event should be ignored.
yeps, in Patch 2/5:
+ if (transport->state == SCTP_PF &&
+ asoc->pf_expose != SCTP_PF_EXPOSE_ENABLE)
+ ulp_notify = false;
+ else if (transport->state == SCTP_UNCONFIRMED &&
+ error == SCTP_HEARTBEAT_SUCCESS)
spc_state = SCTP_ADDR_CONFIRMED;
else
spc_state = SCTP_ADDR_AVAILABLE;Quoted 21 lines
Quoted 21 lines
net/sctp/associola.c +3
-4transport->state =SCTP_ACTIVE ;break ;@@ -817,19 +809,18 @@ void sctp_assoc_control_transport(struct sctp_association *asoc,* to inactive state. Also, release the cached route since * there may be a better route next time. */ -if (transport->state !=SCTP_UNCONFIRMED ) +if (transport->state !=SCTP_UNCONFIRMED ) { transport->state =SCTP_INACTIVE ; -else { + spc_state =SCTP_ADDR_UNREACHABLE ; + }else {sctp_transport_dst_release (transport); ulp_notify = false; } - - spc_state =SCTP_ADDR_UNREACHABLE ;break ;
Quoted 5 lines
net/sctp/associola.c void sctp_assoc_control_transport(struct sctp_association *asoc, · line 832
Quoted 3 lines
net/sctp/associola.c +0
-1case SCTP_TRANSPORT_PF : transport->state =SCTP_PF ; - ulp_notify = false;Again the event should be supressed if PF isn't exposed.
it will be suppressed after Patch 2/5:
+ if (asoc->pf_expose != SCTP_PF_EXPOSE_ENABLE)
+ ulp_notify = false;
+ else
+ spc_state = SCTP_ADDR_POTENTIALLY_FAILED;
break;Quoted 10 lines
Quoted 7 lines
net/sctp/associola.c +1
-1+ spc_state =SCTP_ADDR_POTENTIALLY_FAILED ;break ;default : --2.1.0
I also haven't spotted where the test that the application has actually enabled state transition events is in the code.
all events will be created, but dropped in sctp_ulpq_tail_event() when trying to deliver up:
/* Check if the user wishes to receive this event. */
if (!sctp_ulpevent_is_enabled(event, ulpq->asoc->subscribe))
goto out_free;Quoted 8 lines
I'd have thought it would be anything is built and allocated.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK Registration No: 1397386 (Wales)
Xin Long
maintainerRe: [PATCHv3 net-next 1/5] sctp: add SCTP_ADDR_POTENTIALLY_FAILED notification
Hi, David L.
I will repost if you don't have any other dissent.
Thanks for your nice review.
Quoted 132 lines · Xin Long
Quoted 2 lines · David Laight
I've found v3 :-)
ah okay. sorry.
Quoted 50 lines
But it isn't that much better than v2.
From: Xin Long
Quoted 47 lines
Sent: 14 October 2019 07:15
SCTP Quick failover draft section 5.1, point 5 has been removed from rfc7829. Instead, "the sender SHOULD (i) notify the Upper Layer Protocol (ULP) about this state transition", as said in section 3.2, point 8.So this patch is to add
SCTP_ADDR_POTENTIALLY_FAILED, defined in section 7.1, "which is reported if the affected address becomes PF". Also remove transport cwnd's update when moving from PF back to ACTIVE , which is no longer in rfc7829 either.
v1->v2:
- no changev2->v3:
- defineSCTP_ADDR_PFSCTP_ADDR_POTENTIALLY_FAILEDSigned-off-by Xin Long <[email protected]>--- include/uapi/linux/sctp.h | 2 ++ net/sctp/associola.c | 17 ++++------------- 2 files changed, 6 insertions(+), 13 deletions(-)include/uapi/linux/sctp.h +2
-0@@ -410,6 +410,8 @@ enum sctp_spc_state {SCTP_ADDR_ADDED ,SCTP_ADDR_MADE_PRIM ,SCTP_ADDR_CONFIRMED , +SCTP_ADDR_POTENTIALLY_FAILED , +#define SCTP_ADDR_PF SCTP_ADDR_POTENTIALLY_FAILED };net/sctp/associola.c +0
-4@@ -801,14 +801,6 @@ void sctp_assoc_control_transport(struct sctp_association *asoc, spc_state =SCTP_ADDR_CONFIRMED ; else spc_state =SCTP_ADDR_AVAILABLE ; -/* Don't inform ULP about transition from PF to -* active state and set cwnd to 1 MTU, see SCTP -* Quick failover draft section 5.1, point 5 -*/ Quoted 8 lines
net/sctp/associola.c void sctp_assoc_control_transport(struct sctp_association *asoc, · line 811
Quoted 4 lines
net/sctp/associola.c +0
-4-if (transport->state ==SCTP_PF ) { - ulp_notify = false; - transport->cwnd = asoc->pathmtu; - }This is wrong.
If the old state is PF and the application hasn't exposed PF the event should be ignored.yeps, in Patch 2/5:
(quoted diff) +5
-0+ if (transport->state == SCTP_PF && + asoc->pf_expose != SCTP_PF_EXPOSE_ENABLE) + ulp_notify = false; + else if (transport->state == SCTP_UNCONFIRMED && + error == SCTP_HEARTBEAT_SUCCESS) spc_state = SCTP_ADDR_CONFIRMED; else spc_state = SCTP_ADDR_AVAILABLE;Quoted 22 lines
Quoted 22 lines
net/sctp/associola.c +3
-4transport->state =SCTP_ACTIVE ;break ;@@ -817,19 +809,18 @@ void sctp_assoc_control_transport(struct sctp_association *asoc,* to inactive state. Also, release the cached route since * there may be a better route next time. */ -if (transport->state !=SCTP_UNCONFIRMED ) +if (transport->state !=SCTP_UNCONFIRMED ) { transport->state =SCTP_INACTIVE ; -else { + spc_state =SCTP_ADDR_UNREACHABLE ; + }else {sctp_transport_dst_release (transport); ulp_notify = false; } - - spc_state =SCTP_ADDR_UNREACHABLE ;break ;Quoted 5 lines
net/sctp/associola.c void sctp_assoc_control_transport(struct sctp_association *asoc, · line 832
Quoted 3 lines
net/sctp/associola.c +0
-1case SCTP_TRANSPORT_PF : transport->state =SCTP_PF ; - ulp_notify = false;Again the event should be supressed if PF isn't exposed.
it will be suppressed after Patch 2/5:
(quoted diff) +4
-0+ if (asoc->pf_expose != SCTP_PF_EXPOSE_ENABLE) + ulp_notify = false; + else + spc_state = SCTP_ADDR_POTENTIALLY_FAILED; break;Quoted 11 lines
Quoted 8 lines
net/sctp/associola.c +1
-1+ spc_state =SCTP_ADDR_POTENTIALLY_FAILED ;break ;default : --2.1.0
I also haven't spotted where the test that the application has actually enabled state transition events is in the code.
all events will be created, but dropped in
sctp_ulpq_tail_event()when trying to deliver up:/* Check if the user wishes to receive this event. */ if (!sctp_ulpevent_is_enabled(event, ulpq->asoc->subscribe)) goto out_free;Quoted 8 lines
I'd have thought it would be anything is built and allocated.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK Registration No: 1397386 (Wales)
Marcelo Ricardo Leitner
maintainerRe: [PATCHv3 net-next 1/5] sctp: add SCTP_ADDR_POTENTIALLY_FAILED notification
In reply to Xin LongHi,
Sorry for the long delay on this review.
net/sctp/associola.c void sctp_assoc_control_transport(struct sctp_association *asoc,
Quoted 39 lines · Xin Long
SCTP Quick failover draft section 5.1, point 5 has been removed from rfc7829. Instead, "the sender SHOULD (i) notify the Upper Layer Protocol (ULP) about this state transition", as said in section 3.2, point 8.
So this patch is to add
SCTP_ADDR_POTENTIALLY_FAILED, defined in section 7.1, "which is reported if the affected address becomes PF". Also remove transport cwnd's update when moving from PF back to ACTIVE , which is no longer in rfc7829 either.
v1->v2:
- no changev2->v3:
- defineSCTP_ADDR_PFSCTP_ADDR_POTENTIALLY_FAILEDSigned-off-by Xin Long <[email protected]>--- include/uapi/linux/sctp.h | 2 ++ net/sctp/associola.c | 17 ++++------------- 2 files changed, 6 insertions(+), 13 deletions(-)include/uapi/linux/sctp.h +2
-0@@ -410,6 +410,8 @@ enum sctp_spc_state {SCTP_ADDR_ADDED ,SCTP_ADDR_MADE_PRIM ,SCTP_ADDR_CONFIRMED , +SCTP_ADDR_POTENTIALLY_FAILED , +#define SCTP_ADDR_PF SCTP_ADDR_POTENTIALLY_FAILED };net/sctp/associola.c +0
-0@@ -801,14 +801,6 @@ void sctp_assoc_control_transport(struct sctp_association *asoc,
While at here, dealing with spc_state, please seize the moment and initialize it to the enum instead:
@@ -787,7 +787,7 @@ void sctp_assoc_control_transport(struct sctp_association *asoc,
sctp_sn_error_t error)
{
bool ulp_notify = true;- int spc_state = 0;
+ int spc_state = SCTP_ADDR_AVAILABLE;
net/sctp/associola.c void sctp_assoc_control_transport(struct sctp_association *asoc, · line 803
Quoted 3 lines
net/sctp/associola.c +0
-0spc_state =SCTP_ADDR_CONFIRMED ; else spc_state =SCTP_ADDR_AVAILABLE ;
This else could be removed (equals to initial value).
Quoted 38 lines
net/sctp/associola.c +4
-13-/* Don't inform ULP about transition from PF to -* active state and set cwnd to 1 MTU, see SCTP -* Quick failover draft section 5.1, point 5 -*/ -if (transport->state =SCTP_PF ) { - ulp_notify = false; - transport->cwnd = asoc->pathmtu; - } transport->state =SCTP_ACTIVE ;break ;@@ -817,19 +809,18 @@ void sctp_assoc_control_transport(struct sctp_association *asoc,* to inactive state. Also, release the cached route since * there may be a better route next time. */ -if (transport->state !=SCTP_UNCONFIRMED ) +if (transport->state !=SCTP_UNCONFIRMED ) { transport->state =SCTP_INACTIVE ; -else { + spc_state =SCTP_ADDR_UNREACHABLE ; + }else {sctp_transport_dst_release (transport); ulp_notify = false; } - - spc_state =SCTP_ADDR_UNREACHABLE ;break ;case SCTP_TRANSPORT_PF : transport->state =SCTP_PF ; - ulp_notify = false; + spc_state =SCTP_ADDR_POTENTIALLY_FAILED ;break ;default :Signature · 1 line
2.1.0
Marcelo Ricardo Leitner
maintainerRe: [PATCHv3 net-next 1/5] sctp: add SCTP_ADDR_POTENTIALLY_FAILED notification
In reply to Xin LongQuoted 17 lines · Xin Long
Quoted 8 lines
Quoted 8 lines
net/sctp/associola.c +0
-4@@ -801,14 +801,6 @@ void sctp_assoc_control_transport(struct sctp_association *asoc, spc_state =SCTP_ADDR_CONFIRMED ; else spc_state =SCTP_ADDR_AVAILABLE ; -/* Don't inform ULP about transition from PF to -* active state and set cwnd to 1 MTU, see SCTP -* Quick failover draft section 5.1, point 5 -*/ Quoted 8 lines
net/sctp/associola.c void sctp_assoc_control_transport(struct sctp_association *asoc, · line 811
Quoted 4 lines
net/sctp/associola.c +0
-4-if (transport->state =SCTP_PF ) { - ulp_notify = false; - transport->cwnd = asoc->pathmtu; - }This is wrong.
If the old state is PF and the application hasn't exposed PF the event should be ignored.yeps, in Patch 2/5:
Review
Quoted 8 lines
(quoted diff) +5
-0+ if (transport->state = SCTP_PF && + asoc->pf_expose != SCTP_PF_EXPOSE_ENABLE) + ulp_notify = false; + else if (transport->state = SCTP_UNCONFIRMED && + error = SCTP_HEARTBEAT_SUCCESS) spc_state = SCTP_ADDR_CONFIRMED; else spc_state = SCTP_ADDR_AVAILABLE;
Right, yet for one bisecting the kernel, a checkout on this patch will see this change regardless of patch 2. Patches 1 and 2 could be swapped to avoid this situation.
Quoted 28 lines
Quoted 22 lines
Quoted 22 lines
net/sctp/associola.c +3
-4transport->state =SCTP_ACTIVE ;break ;@@ -817,19 +809,18 @@ void sctp_assoc_control_transport(struct sctp_association *asoc,* to inactive state. Also, release the cached route since * there may be a better route next time. */ -if (transport->state !=SCTP_UNCONFIRMED ) +if (transport->state !=SCTP_UNCONFIRMED ) { transport->state =SCTP_INACTIVE ; -else { + spc_state =SCTP_ADDR_UNREACHABLE ; + }else {sctp_transport_dst_release (transport); ulp_notify = false; } - - spc_state =SCTP_ADDR_UNREACHABLE ;break ;Quoted 5 lines
net/sctp/associola.c void sctp_assoc_control_transport(struct sctp_association *asoc, · line 832
Quoted 3 lines
net/sctp/associola.c +0
-1case SCTP_TRANSPORT_PF : transport->state =SCTP_PF ; - ulp_notify = false;Again the event should be supressed if PF isn't exposed.
it will be suppressed after Patch 2/5:
Review
Quoted 5 lines
(quoted diff) +4
-0+ if (asoc->pf_expose != SCTP_PF_EXPOSE_ENABLE) + ulp_notify = false; + else + spc_state = SCTP_ADDR_POTENTIALLY_FAILED; break;
Same here.
Quoted 27 lines
Quoted 11 lines
Quoted 8 lines
net/sctp/associola.c +1
-1+ spc_state =SCTP_ADDR_POTENTIALLY_FAILED ;break ;default : --2.1.0
I also haven't spotted where the test that the application has actually enabled state transition events is in the code.
all events will be created, but dropped in
sctp_ulpq_tail_event()when trying to deliver up:/* Check if the user wishes to receive this event. */ if (!sctp_ulpevent_is_enabled(event, ulpq->asoc->subscribe)) goto out_free;Quoted 8 lines
I'd have thought it would be anything is built and allocated.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK Registration No: 1397386 (Wales)
Marcelo Ricardo Leitner
maintainerRe: [PATCHv3 net-next 2/5] sctp: add pf_expose per netns and sock and asoc
In reply to Xin LongQuoted 14 lines · Xin Long
As said in rfc7829, section 3, point 12:
The SCTP stack SHOULD expose the PF state of its destination addresses to the ULP as well as provide the means to notify the ULP of state transitions of its destination addresses from active to PF, and vice versa. However, it is recommended that an SCTP stack implementing SCTP-PF also allows for the ULP to be kept ignorant of the PF state of its destinations and the associated state transitions, thus allowing for retention of the simpler state transition model of [RFC4960] in the ULP.
Not only does it allow to expose the PF state to ULP, but also allow to ignore sctp-pf to ULP.
Quoted 6 lines
So this patch is to add
pf_exposeper netns, sock and asoc. And insctp_assoc_control_transport(),ulp_notifywill be set to false ifasoc->exposeis not set.It also allows a user to change
pf_exposeper netns by sysctl, andpf_exposeper sock and asoc will be initialized with it.
I also do see value on this sysctl. We currently have an implementation that sits in between the states that the RFC defines and this allows the system to remain using the original Linux behavior, while also forcing especially the disabled state. This can help on porting applications to Linux.
Quoted 10 lines
Note that
pf_exposealso works forSCTP_GET_PEER_ADDR_INFOsockopt, to not allow a user to query the state of a sctp-pf peer address whenpf_exposeis not enabled, as said in section 7.3.
v1->v2:
- Fix a build warning noticed by Nathan Chancellor.v2->v3:
- setpf_exposeto UNUSED by default to keep compatible with old applications.
Hmmm UNUSED can be quite confusing.
What about "UNSET" instead? (though I'm not that happy with UNSET either, but couldn't come up with a better name)
And make UNSET=0. (first on the enum)
So we have it like:
"If unset, the exposure is done as Linux used to do it, while setting it to 1 blocks it and 2, enables it, according to the RFC."
Needs a new entry on Documentation/ip-sysctl.txt, btw. We have pf_enable in there.
...
Quoted 6 lines
net/sctp/socket.c +0
-2@@ -5521,8 +5522,16 @@ static int sctp_getsockopt_peer_addr_info(struct sock *sk, int len, transport =sctp_addr_id2transport (sk, &pinfo.spinfo_address, pinfo.spinfo_assoc_id); -if (!transport) -return -EINVAL ;
net/sctp/socket.c static int sctp_getsockopt_peer_addr_info(struct sock *sk, int len, · line 5534
Quoted 10 lines
net/sctp/socket.c +10
-0+if (!transport) { + retval = -EINVAL ; + goto out; + } + +if (transport->state =SCTP_PF && + transport->asoc->pf_expose =SCTP_PF_EXPOSE_DISABLE ) { + retval = -EACCES ; + goto out; + }
As is on v3, this is NOT an UAPI violation. The user has to explicitly set the system or the socket into the disabled state in order to trigger this new check.
Quoted 33 lines
net/sctp/socket.c +0
-0pinfo.spinfo_assoc_id =sctp_assoc2id (transport->asoc); pinfo.spinfo_state = transport->state;net/sctp/sysctl.c +1
-0@@ -34,6 +34,7 @@ static int rto_alpha_min = 0;static int rto_beta_min =0 ;static int rto_alpha_max =1000 ;static int rto_beta_max =1000 ; +static int pf_expose_max =SCTP_PF_EXPOSE_MAX ;static unsigned long max_autoclose_min =0 ; static unsigned long max_autoclose_max > @@ -318,6 +319,15 @@ static struct ctl_table sctp_net_table[] = {net/sctp/sysctl.c +9
-0.mode = 0644, .proc_handler = proc_dointvec, }, + { + .procname = "pf_expose", + .data = &init_net.sctp.pf_expose, + .maxlen = sizeof(int), + .mode = 0644, + .proc_handler = proc_dointvec_minmax, + .extra1 = SYSCTL_ZERO, + .extra2 = &pf_expose_max, + }, {/* sentinel */ } };Signature · 1 line
2.1.0
Marcelo Ricardo Leitner
maintainerRe: [PATCHv3 net-next 3/5] sctp: add SCTP_EXPOSE_POTENTIALLY_FAILED_STATE sockopt
In reply to Xin LongQuoted 9 lines · Xin Long
This is a sockopt defined in section 7.3 of rfc7829: "Exposing the Potentially Failed Path State", by which users can change
pf_exposeper sock and asoc.
v1->v2:
- no change.v2->v3:
- return-EINVALif params.assoc_value >SCTP_PF_EXPOSE_MAX.
- defineSCTP_EXPOSE_PF_STATESCTP_EXPOSE_POTENTIALLY_FAILED_STATE.
Hm, why again? Please add it to the changelog, as it's an exception on the list below.
Quoted 20 lines
Signed-off-by Xin Long <[email protected]>--- include/uapi/linux/sctp.h | 2 ++ net/sctp/socket.c | 79 +++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 81 insertions(+)include/uapi/linux/sctp.h +2
-0@@ -137,6 +137,8 @@ typedef __s32 sctp_assoc_t;#define SCTP_ASCONF_SUPPORTED 128#define SCTP_AUTH_SUPPORTED 129#define SCTP_ECN_SUPPORTED 130 +#define SCTP_EXPOSE_POTENTIALLY_FAILED_STATE 131 +#define SCTP_EXPOSE_PF_STATE SCTP_EXPOSE_POTENTIALLY_FAILED_STATE/* PR-SCTP policies */ #define SCTP_PR_SCTP_NONE 0x0000
Marcelo Ricardo Leitner
maintainerRe: [PATCHv3 net-next 4/5] sctp: add support for Primary Path Switchover
In reply to Xin LongQuoted 157 lines · Xin Long
This is a new feature defined in section 5 of rfc7829: "Primary Path Switchover". By introducing a new tunable parameter:
Primary.Switchover.Max.Retrans (PSMR)
The primary path will be changed to another active path when the path error counter on the old primary path exceeds PSMR, so that "the SCTP sender is allowed to continue data transmission on a new working path even when the old primary destination address becomes active again".
This patch is to add this tunable parameter, '
ps_retrans' per netns, sock, asoc and transport. It also allows a user to changeps_retransper netns by sysctl, andps_retransper sock/asoc/transport will be initialized with it.The check will be done in
sctp_do_8_2_transport_strike()when this feature is enabled.Note this feature is disabled by initializing '
ps_retrans' per netns as0xffffby default, and its value can't be less than 'pf_retrans' when changing by sysctl.Signed-off-by Xin Long <[email protected]>--- include/net/netns/sctp.h | 6 ++++++ include/net/sctp/structs.h | 11 ++++++++--- net/sctp/associola.c | 3 +++ net/sctp/protocol.c | 3 +++ net/sctp/sm_sideeffect.c | 5 +++++ net/sctp/socket.c | 1 + net/sctp/sysctl.c | 9 +++++++++ 7 files changed, 35 insertions(+), 3 deletions(-)include/net/netns/sctp.h +6
-0@@ -89,6 +89,12 @@ struct netns_sctp {*/ int pf_retrans; +/* Primary.Switchover.Max.Retrans sysctl value +* taken from: +* https://tools.ietf.org/html/rfc7829 +*/ +int ps_retrans; +/* * Disable Potentially-Failed feature, the feature is enabled by default * pf_enable - 0 : disable pf include/net/sctp/structs.h +8
-3@@ -184,7 +184,8 @@ struct sctp_sock {__u32 flowlabel;__u8 dscp; -int pf_retrans; +__u16 pf_retrans; +__u16 ps_retrans;/* The initial Path MTU to use for new associations. */ __u32 pathmtu;@@ -897,7 +898,9 @@ struct sctp_transport {* and will be initialized from the assocs value. This can be changed * using the SCTP_PEER_ADDR_THLDS socket option */ -int pf_retrans; +__u16 pf_retrans; +/* Used for primary path switchover. */ +__u16 ps_retrans;/* PMTU : The current known path MTU. */ __u32 pathmtu;@@ -1773,7 +1776,9 @@ struct sctp_association {* and will be initialized from the assocs value. This can be * changed using the SCTP_PEER_ADDR_THLDS socket option */ -int pf_retrans; +__u16 pf_retrans; +/* Used for primary path switchover. */ +__u16 ps_retrans;/* Maximum number of times the endpoint will retransmit INIT */ __u16 max_init_attempts;net/sctp/associola.c +3
-0@@ -86,6 +86,7 @@ static struct sctp_association *sctp_association_init(*/ asoc->max_retrans = sp->assocparams.sasoc_asocmaxrxt; asoc->pf_retrans = sp->pf_retrans; + asoc->ps_retrans = sp->ps_retrans; asoc->pf_expose = sp->pf_expose; asoc->rto_initial =msecs_to_jiffies (sp->rtoinfo.srto_initial);@@ -628,6 +629,8 @@ struct sctp_transport *sctp_assoc_add_peer(struct sctp_association *asoc,/* And the partial failure retrans threshold */ peer->pf_retrans = asoc->pf_retrans; +/* And the primary path switchover retrans threshold */ + peer->ps_retrans = asoc->ps_retrans;/* Initialize the peer's SACK delay timeout based on the * association configured value. net/sctp/protocol.c +3
-0@@ -1217,6 +1217,9 @@ static int __net_init sctp_defaults_init(struct net *net)/* Max.Burst - 4 */ net->sctp.max_burst =SCTP_DEFAULT_MAX_BURST ; +/* Disable of Primary Path Switchover by default */ + net->sctp.ps_retrans =0xffff ; +/* Enable pf state by default */ net->sctp.pf_enable =1 ;net/sctp/sm_sideeffect.c +5
-0@@ -567,6 +567,11 @@ static void sctp_do_8_2_transport_strike(struct sctp_cmd_seq *commands, SCTP_FAILED_THRESHOLD); } +if (transport->error_count > transport->ps_retrans && + asoc->peer.primary_path = transport && + asoc->peer.active_path != transport) +sctp_assoc_set_primary (asoc, asoc->peer.active_path); +/* E2) For the destination address for which the timer * expires, set RTO <- RTO * 2 ("back off the timer"). The * maximum value discussed in rule C7 above (RTO.max) may be net/sctp/socket.c +1
-0@@ -5078,6 +5078,7 @@ static int sctp_init_sock(struct sock *sk) sp->hbinterval = net->sctp.hb_interval; sp->pathmaxrxt = net->sctp.max_retrans_path; sp->pf_retrans = net->sctp.pf_retrans; + sp->ps_retrans = net->sctp.ps_retrans; sp->pf_expose = net->sctp.pf_expose; sp->pathmtu =0 ;/* allow default discovery */ sp->sackdelay = net->sctp.sack_timeout;net/sctp/sysctl.c +0
-0@@ -213,6 +213,15 @@ static struct ctl_table sctp_net_table[] = { .mode = 0644, .proc_handler = proc_dointvec_minmax, .extra1 = SYSCTL_ZERO,
net/sctp/sysctl.c static struct ctl_table sctp_net_table[] = { · line 225
Quoted 10 lines
net/sctp/sysctl.c +9
-0+ .extra2 = &init_net.sctp.ps_retrans, + }, + { + .procname = "ps_retrans", + .data = &init_net.sctp.ps_retrans, + .maxlen = sizeof(int), + .mode = 0644, + .proc_handler = proc_dointvec_minmax, + .extra1 = &init_net.sctp.pf_retrans, .extra2 = SYSCTL_INT_MAX,
pf_retrans got shrunk to 16 bits on other structs (why? I'm thinking it was just to keep the structs size in check). INT_MAX doesn't make sense anymore then and in fact it can lead to unexpected behavior. Like, setting 0x10000 becoming effectively 0.
(yes, usage of >16bits values are probably unreasoable, but..)
Quoted 5 lines
net/sctp/sysctl.c +0
-0}, {Signature · 1 line
2.1.0
Xin Long
maintainerRe: [PATCHv3 net-next 1/5] sctp: add SCTP_ADDR_POTENTIALLY_FAILED notification
In reply to Marcelo Ricardo LeitnerQuoted 59 lines · Marcelo Ricardo Leitner
Quoted 17 lines · Xin Long
Quoted 8 lines
Quoted 8 lines
net/sctp/associola.c +0
-4@@ -801,14 +801,6 @@ void sctp_assoc_control_transport(struct sctp_association *asoc, spc_state =SCTP_ADDR_CONFIRMED ; else spc_state =SCTP_ADDR_AVAILABLE ; -/* Don't inform ULP about transition from PF to -* active state and set cwnd to 1 MTU, see SCTP -* Quick failover draft section 5.1, point 5 -*/ Quoted 8 lines
net/sctp/associola.c void sctp_assoc_control_transport(struct sctp_association *asoc, · line 811
Quoted 4 lines
net/sctp/associola.c +0
-4-if (transport->state =SCTP_PF ) { - ulp_notify = false; - transport->cwnd = asoc->pathmtu; - }This is wrong.
If the old state is PF and the application hasn't exposed PF the event should be ignored.yeps, in Patch 2/5:
Review
Quoted 8 lines
(quoted diff) +5
-0+ if (transport->state = SCTP_PF && + asoc->pf_expose != SCTP_PF_EXPOSE_ENABLE) + ulp_notify = false; + else if (transport->state = SCTP_UNCONFIRMED && + error = SCTP_HEARTBEAT_SUCCESS) spc_state = SCTP_ADDR_CONFIRMED; else spc_state = SCTP_ADDR_AVAILABLE;Right, yet for one bisecting the kernel, a checkout on this patch will see this change regardless of patch 2. Patches 1 and 2 could be swapped to avoid this situation.
Quoted 27 lines
Quoted 27 lines
Quoted 15 lines
net/sctp/associola.c +3
-2transport->state =SCTP_ACTIVE ;break ;@@ -817,19 +809,18 @@ void sctp_assoc_control_transport(struct sctp_association *asoc,* to inactive state. Also, release the cached route since * there may be a better route next time. */ -if (transport->state !=SCTP_UNCONFIRMED ) +if (transport->state !=SCTP_UNCONFIRMED ) { transport->state =SCTP_INACTIVE ; -else { + spc_state =SCTP_ADDR_UNREACHABLE ; + }else {net/sctp/associola.c void sctp_assoc_control_transport(struct sctp_association *asoc, · line 832
Quoted 10 lines
net/sctp/associola.c +0
-3sctp_transport_dst_release (transport); ulp_notify = false; } - - spc_state =SCTP_ADDR_UNREACHABLE ;break ;case SCTP_TRANSPORT_PF : transport->state =SCTP_PF ; - ulp_notify = false;Again the event should be supressed if PF isn't exposed.
Quoted 8 lines
Review
Quoted 6 lines
it will be suppressed after Patch 2/5:
(quoted diff) +4
-0+ if (asoc->pf_expose != SCTP_PF_EXPOSE_ENABLE) + ulp_notify = false; + else + spc_state = SCTP_ADDR_POTENTIALLY_FAILED; break;Same here.
okay, will swap them. thanks.
Quoted 28 lines
Quoted 28 lines
Quoted 6 lines
Quoted 6 lines
net/sctp/associola.c +1
-0+ spc_state =SCTP_ADDR_POTENTIALLY_FAILED ;break ;Quoted 6 lines
Quoted 3 lines
(quoted diff) +0
-1default: --2.1.0
I also haven't spotted where the test that the application has actually enabled state transition events is in the code.
all events will be created, but dropped in
sctp_ulpq_tail_event()when trying to deliver up:/* Check if the user wishes to receive this event. */ if (!sctp_ulpevent_is_enabled(event, ulpq->asoc->subscribe)) goto out_free;Quoted 8 lines
I'd have thought it would be anything is built and allocated.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK Registration No: 1397386 (Wales)
Xin Long
maintainerRe: [PATCHv3 net-next 1/5] sctp: add SCTP_ADDR_POTENTIALLY_FAILED notification
In reply to Marcelo Ricardo LeitnerQuoted 61 lines · Marcelo Ricardo Leitner
Hi,
Sorry for the long delay on this review.
net/sctp/associola.c void sctp_assoc_control_transport(struct sctp_association *asoc,
Quoted 39 lines · Xin Long
SCTP Quick failover draft section 5.1, point 5 has been removed from rfc7829. Instead, "the sender SHOULD (i) notify the Upper Layer Protocol (ULP) about this state transition", as said in section 3.2, point 8.
So this patch is to add
SCTP_ADDR_POTENTIALLY_FAILED, defined in section 7.1, "which is reported if the affected address becomes PF". Also remove transport cwnd's update when moving from PF back to ACTIVE , which is no longer in rfc7829 either.
v1->v2:
- no changev2->v3:
- defineSCTP_ADDR_PFSCTP_ADDR_POTENTIALLY_FAILEDSigned-off-by Xin Long <[email protected]>--- include/uapi/linux/sctp.h | 2 ++ net/sctp/associola.c | 17 ++++------------- 2 files changed, 6 insertions(+), 13 deletions(-)include/uapi/linux/sctp.h +2
-0@@ -410,6 +410,8 @@ enum sctp_spc_state {SCTP_ADDR_ADDED ,SCTP_ADDR_MADE_PRIM ,SCTP_ADDR_CONFIRMED , +SCTP_ADDR_POTENTIALLY_FAILED , +#define SCTP_ADDR_PF SCTP_ADDR_POTENTIALLY_FAILED };net/sctp/associola.c +0
-0@@ -801,14 +801,6 @@ void sctp_assoc_control_transport(struct sctp_association *asoc,While at here, dealing with
spc_state, please seize the moment and initialize it to the enum instead:(quoted diff) +1
-1@@ -787,7 +787,7 @@ void sctp_assoc_control_transport(struct sctp_association *asoc, sctp_sn_error_t error) { bool ulp_notify = true; - int spc_state = 0; + int spc_state = SCTP_ADDR_AVAILABLE; > spc_state = SCTP_ADDR_CONFIRMED;net/sctp/associola.c void sctp_assoc_control_transport(struct sctp_association *asoc, · line 803
Quoted 2 lines
net/sctp/associola.c +0
-0else spc_state =SCTP_ADDR_AVAILABLE ;
Quoted 1 line
This else could be removed (equals to initial value).
yes, will improve it.
Quoted 39 lines
Quoted 39 lines
net/sctp/associola.c +4
-14-/* Don't inform ULP about transition from PF to -* active state and set cwnd to 1 MTU, see SCTP -* Quick failover draft section 5.1, point 5 -*/ -if (transport->state =SCTP_PF ) { - ulp_notify = false; - transport->cwnd = asoc->pathmtu; - } transport->state =SCTP_ACTIVE ;break ;@@ -817,19 +809,18 @@ void sctp_assoc_control_transport(struct sctp_association *asoc,* to inactive state. Also, release the cached route since * there may be a better route next time. */ -if (transport->state !=SCTP_UNCONFIRMED ) +if (transport->state !=SCTP_UNCONFIRMED ) { transport->state =SCTP_INACTIVE ; -else { + spc_state =SCTP_ADDR_UNREACHABLE ; + }else {sctp_transport_dst_release (transport); ulp_notify = false; } - - spc_state =SCTP_ADDR_UNREACHABLE ;break ;case SCTP_TRANSPORT_PF : transport->state =SCTP_PF ; - ulp_notify = false; + spc_state =SCTP_ADDR_POTENTIALLY_FAILED ;break ;default : --2.1.0
Xin Long
maintainerRe: [PATCHv3 net-next 2/5] sctp: add pf_expose per netns and sock and asoc
In reply to Marcelo Ricardo LeitnerQuoted 20 lines · Marcelo Ricardo Leitner
Quoted 18 lines · Xin Long
As said in rfc7829, section 3, point 12:
The SCTP stack SHOULD expose the PF state of its destination addresses to the ULP as well as provide the means to notify the ULP of state transitions of its destination addresses from active to PF, and vice versa. However, it is recommended that an SCTP stack implementing SCTP-PF also allows for the ULP to be kept ignorant of the PF state of its destinations and the associated state transitions, thus allowing for retention of the simpler state transition model of [RFC4960] in the ULP.
Not only does it allow to expose the PF state to ULP, but also allow to ignore sctp-pf to ULP.
So this patch is to add
pf_exposeper netns, sock and asoc. And insctp_assoc_control_transport(),ulp_notifywill be set to false ifasoc->exposeis not set.
Quoted 8 lines
Quoted 2 lines
It also allows a user to change
pf_exposeper netns by sysctl, andpf_exposeper sock and asoc will be initialized with it.I also do see value on this sysctl. We currently have an implementation that sits in between the states that the RFC defines and this allows the system to remain using the original Linux behavior, while also forcing especially the disabled state. This can help on porting applications to Linux.
Agreed.
Quoted 17 lines
Quoted 11 lines
Note that
pf_exposealso works forSCTP_GET_PEER_ADDR_INFOsockopt, to not allow a user to query the state of a sctp-pf peer address whenpf_exposeis not enabled, as said in section 7.3.
v1->v2:
- Fix a build warning noticed by Nathan Chancellor.v2->v3:
- setpf_exposeto UNUSED by default to keep compatible with old applications.Hmmm UNUSED can be quite confusing.
What about "UNSET" instead? (though I'm not that happy with UNSET either, but couldn't come up with a better name)
And make UNSET=0. (first on the enum)
Quoted 6 lines
So we have it like:
"If unset, the exposure is done as Linux used to do it, while setting it to 1 blocks it and 2, enables it, according to the RFC."Needs a new entry on
Documentation/ip-sysctl.txt, btw. We havepf_enablein there.
will add it meanwhile. Thanks.
Quoted 15 lines
...
Quoted 12 lines
net/sctp/socket.c +6
-2@@ -5521,8 +5522,16 @@ static int sctp_getsockopt_peer_addr_info(struct sock *sk, int len, transport =sctp_addr_id2transport (sk, &pinfo.spinfo_address, pinfo.spinfo_assoc_id); -if (!transport) -return -EINVAL ; +if (!transport) { + retval = -EINVAL ; + goto out; + } + + if (transport->state = SCTP_PF &&
Quoted 8 lines
net/sctp/socket.c static int sctp_getsockopt_peer_addr_info(struct sock *sk, int len, · line 5534
Quoted 4 lines
net/sctp/socket.c +4
-0+ transport->asoc->pf_expose = SCTP_PF_EXPOSE_DISABLE) { + retval = -EACCES ; + goto out; + }As is on v3, this is NOT an UAPI violation. The user has to explicitly set the system or the socket into the disabled state in order to trigger this new check.
Agreed.
Quoted 34 lines
Quoted 34 lines
net/sctp/socket.c +0
-0pinfo.spinfo_assoc_id =sctp_assoc2id (transport->asoc); pinfo.spinfo_state = transport->state;net/sctp/sysctl.c +1
-0@@ -34,6 +34,7 @@ static int rto_alpha_min = 0;static int rto_beta_min =0 ;static int rto_alpha_max =1000 ;static int rto_beta_max =1000 ; +static int pf_expose_max =SCTP_PF_EXPOSE_MAX ;static unsigned long max_autoclose_min =0 ; static unsigned long max_autoclose_max > > @@ -318,6 +319,15 @@ static struct ctl_table sctp_net_table[] = {.mode = 0644, .proc_handler = proc_dointvec, },net/sctp/sysctl.c +9
-1+ { + .procname = "pf_expose", + .data = &init_net.sctp.pf_expose, + .maxlen = sizeof(int), + .mode = 0644, + .proc_handler = proc_dointvec_minmax, + .extra1 = SYSCTL_ZERO, + .extra2 = &pf_expose_max, + }, {/* sentinel */ } }; --2.1.0
Xin Long
maintainerRe: [PATCHv3 net-next 3/5] sctp: add SCTP_EXPOSE_POTENTIALLY_FAILED_STATE sockopt
In reply to Marcelo Ricardo LeitnerQuoted 6 lines · Marcelo Ricardo Leitner
Quoted 4 lines · Xin Long
This is a sockopt defined in section 7.3 of rfc7829: "Exposing the Potentially Failed Path State", by which users can change
pf_exposeper sock and asoc.
Quoted 8 lines
Quoted 5 lines
v1->v2:
- no change.v2->v3:
- return-EINVALif params.assoc_value >SCTP_PF_EXPOSE_MAX.
- defineSCTP_EXPOSE_PF_STATESCTP_EXPOSE_POTENTIALLY_FAILED_STATE.Hm, why again? Please add it to the changelog, as it's an exception on the list below.
will do. thanks.
Quoted 21 lines
Quoted 21 lines
Signed-off-by Xin Long <[email protected]>--- include/uapi/linux/sctp.h | 2 ++ net/sctp/socket.c | 79 +++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 81 insertions(+)include/uapi/linux/sctp.h +2
-0@@ -137,6 +137,8 @@ typedef __s32 sctp_assoc_t;#define SCTP_ASCONF_SUPPORTED 128#define SCTP_AUTH_SUPPORTED 129#define SCTP_ECN_SUPPORTED 130 +#define SCTP_EXPOSE_POTENTIALLY_FAILED_STATE 131 +#define SCTP_EXPOSE_PF_STATE SCTP_EXPOSE_POTENTIALLY_FAILED_STATE/* PR-SCTP policies */ #define SCTP_PR_SCTP_NONE 0x0000
Xin Long
maintainerRe: [PATCHv3 net-next 4/5] sctp: add support for Primary Path Switchover
In reply to Marcelo Ricardo LeitnerQuoted 167 lines · Marcelo Ricardo Leitner
Quoted 165 lines · Xin Long
This is a new feature defined in section 5 of rfc7829: "Primary Path Switchover". By introducing a new tunable parameter:
Primary.Switchover.Max.Retrans (PSMR)
The primary path will be changed to another active path when the path error counter on the old primary path exceeds PSMR, so that "the SCTP sender is allowed to continue data transmission on a new working path even when the old primary destination address becomes active again".
This patch is to add this tunable parameter, '
ps_retrans' per netns, sock, asoc and transport. It also allows a user to changeps_retransper netns by sysctl, andps_retransper sock/asoc/transport will be initialized with it.The check will be done in
sctp_do_8_2_transport_strike()when this feature is enabled.Note this feature is disabled by initializing '
ps_retrans' per netns as0xffffby default, and its value can't be less than 'pf_retrans' when changing by sysctl.Signed-off-by Xin Long <[email protected]>--- include/net/netns/sctp.h | 6 ++++++ include/net/sctp/structs.h | 11 ++++++++--- net/sctp/associola.c | 3 +++ net/sctp/protocol.c | 3 +++ net/sctp/sm_sideeffect.c | 5 +++++ net/sctp/socket.c | 1 + net/sctp/sysctl.c | 9 +++++++++ 7 files changed, 35 insertions(+), 3 deletions(-)include/net/netns/sctp.h +6
-0@@ -89,6 +89,12 @@ struct netns_sctp {*/ int pf_retrans; +/* Primary.Switchover.Max.Retrans sysctl value +* taken from: +* https://tools.ietf.org/html/rfc7829 +*/ +int ps_retrans; +/* * Disable Potentially-Failed feature, the feature is enabled by default * pf_enable - 0 : disable pf include/net/sctp/structs.h +8
-3@@ -184,7 +184,8 @@ struct sctp_sock {__u32 flowlabel;__u8 dscp; -int pf_retrans; +__u16 pf_retrans; +__u16 ps_retrans;/* The initial Path MTU to use for new associations. */ __u32 pathmtu;@@ -897,7 +898,9 @@ struct sctp_transport {* and will be initialized from the assocs value. This can be changed * using the SCTP_PEER_ADDR_THLDS socket option */ -int pf_retrans; +__u16 pf_retrans; +/* Used for primary path switchover. */ +__u16 ps_retrans;/* PMTU : The current known path MTU. */ __u32 pathmtu;@@ -1773,7 +1776,9 @@ struct sctp_association {* and will be initialized from the assocs value. This can be * changed using the SCTP_PEER_ADDR_THLDS socket option */ -int pf_retrans; +__u16 pf_retrans; +/* Used for primary path switchover. */ +__u16 ps_retrans;/* Maximum number of times the endpoint will retransmit INIT */ __u16 max_init_attempts;net/sctp/associola.c +3
-0@@ -86,6 +86,7 @@ static struct sctp_association *sctp_association_init(*/ asoc->max_retrans = sp->assocparams.sasoc_asocmaxrxt; asoc->pf_retrans = sp->pf_retrans; + asoc->ps_retrans = sp->ps_retrans; asoc->pf_expose = sp->pf_expose; asoc->rto_initial =msecs_to_jiffies (sp->rtoinfo.srto_initial);@@ -628,6 +629,8 @@ struct sctp_transport *sctp_assoc_add_peer(struct sctp_association *asoc,/* And the partial failure retrans threshold */ peer->pf_retrans = asoc->pf_retrans; +/* And the primary path switchover retrans threshold */ + peer->ps_retrans = asoc->ps_retrans;/* Initialize the peer's SACK delay timeout based on the * association configured value. net/sctp/protocol.c +3
-0@@ -1217,6 +1217,9 @@ static int __net_init sctp_defaults_init(struct net *net)/* Max.Burst - 4 */ net->sctp.max_burst =SCTP_DEFAULT_MAX_BURST ; +/* Disable of Primary Path Switchover by default */ + net->sctp.ps_retrans =0xffff ; +/* Enable pf state by default */ net->sctp.pf_enable =1 ;net/sctp/sm_sideeffect.c +5
-0@@ -567,6 +567,11 @@ static void sctp_do_8_2_transport_strike(struct sctp_cmd_seq *commands, SCTP_FAILED_THRESHOLD); } +if (transport->error_count > transport->ps_retrans && + asoc->peer.primary_path = transport && + asoc->peer.active_path != transport) +sctp_assoc_set_primary (asoc, asoc->peer.active_path); +/* E2) For the destination address for which the timer * expires, set RTO <- RTO * 2 ("back off the timer"). The * maximum value discussed in rule C7 above (RTO.max) may be net/sctp/socket.c +1
-0@@ -5078,6 +5078,7 @@ static int sctp_init_sock(struct sock *sk) sp->hbinterval = net->sctp.hb_interval; sp->pathmaxrxt = net->sctp.max_retrans_path; sp->pf_retrans = net->sctp.pf_retrans; + sp->ps_retrans = net->sctp.ps_retrans; sp->pf_expose = net->sctp.pf_expose; sp->pathmtu =0 ;/* allow default discovery */ sp->sackdelay = net->sctp.sack_timeout;net/sctp/sysctl.c +8
-0@@ -213,6 +213,15 @@ static struct ctl_table sctp_net_table[] = { .mode = 0644, .proc_handler = proc_dointvec_minmax, .extra1 = SYSCTL_ZERO, + .extra2 = &init_net.sctp.ps_retrans, + }, + { + .procname = "ps_retrans", + .data = &init_net.sctp.ps_retrans, + .maxlen = sizeof(int), + .mode = 0644, + .proc_handler = proc_dointvec_minmax,
Quoted 8 lines
net/sctp/sysctl.c static struct ctl_table sctp_net_table[] = { · line 225
Quoted 2 lines
net/sctp/sysctl.c +1
-0+ .extra1 = &init_net.sctp.pf_retrans, .extra2 = SYSCTL_INT_MAX,
pf_retransgot shrunk to 16 bits on other structs (why? I'm thinking it was just to keep the structs size in check).INT_MAXdoesn't make sense anymore then and in fact it can lead to unexpected behavior. Like, setting0x10000becoming effectively 0.
(yes, usage of >16bits values are probably unreasoable, but..)
I'll add "#define SCTP_PS_RETRANS_MAX 0xffff", which will be used by both initializaion and sysctl extra2.
Quoted 6 lines
Quoted 6 lines
net/sctp/sysctl.c +0
-1}, { --2.1.0
RE: [PATCHv3 net-next 2/5] sctp: add pf_expose per netns and sock and asoc
In reply to Marcelo Ricardo LeitnerFrom: Marcelo Ricardo Leitner
Quoted 1 line
Sent: 25 October 2019 04:24
...
Quoted 12 lines
Quoted 12 lines
net/sctp/socket.c +6
-2@@ -5521,8 +5522,16 @@ static int sctp_getsockopt_peer_addr_info(struct sock *sk, int len, transport =sctp_addr_id2transport (sk, &pinfo.spinfo_address, pinfo.spinfo_assoc_id); -if (!transport) -return -EINVAL ; +if (!transport) { + retval = -EINVAL ; + goto out; + } + + if (transport->state = SCTP_PF &&
Quoted 8 lines
net/sctp/socket.c static int sctp_getsockopt_peer_addr_info(struct sock *sk, int len, · line 5534
Quoted 4 lines
net/sctp/socket.c +4
-0+ transport->asoc->pf_expose = SCTP_PF_EXPOSE_DISABLE) { + retval = -EACCES ; + goto out; + }As is on v3, this is NOT an UAPI violation. The user has to explicitly set the system or the socket into the disabled state in order to trigger this new check.
Only because the default isn't to be backwards compatible with the old kernel and old applications.
An old application running on a system that has the protocol parts of PF enabled mustn't see any PF events, states or obscure error returns.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK Registration No: 1397386 (Wales)
'Marcelo Ricardo Leitner'
maintainerRe: [PATCHv3 net-next 2/5] sctp: add pf_expose per netns and sock and asoc
Quoted 24 lines · David Laight
From: Marcelo Ricardo Leitner
Quoted 1 line
Sent: 25 October 2019 04:24
...
Quoted 12 lines
Quoted 12 lines
net/sctp/socket.c +6
-2@@ -5521,8 +5522,16 @@ static int sctp_getsockopt_peer_addr_info(struct sock *sk, int len, transport =sctp_addr_id2transport (sk, &pinfo.spinfo_address, pinfo.spinfo_assoc_id); -if (!transport) -return -EINVAL ; +if (!transport) { + retval = -EINVAL ; + goto out; + } + + if (transport->state = SCTP_PF &&Quoted 8 lines
net/sctp/socket.c static int sctp_getsockopt_peer_addr_info(struct sock *sk, int len, · line 5534
Quoted 4 lines
net/sctp/socket.c +4
-0+ transport->asoc->pf_expose = SCTP_PF_EXPOSE_DISABLE) { + retval = -EACCES ; + goto out; + }As is on v3, this is NOT an UAPI violation. The user has to explicitly set the system or the socket into the disabled state in order to trigger this new check.
Quoted 1 line
Only because the default isn't to be backwards compatible with the
^^^^^
You meant "is", right? Then we're agreeing.
Quoted 4 lines
old kernel and old applications.
An old application running on a system that has the protocol parts of PF enabled mustn't see any PF events, states or obscure error returns.
Yes. With the patchset, the application will only see the new error return if it (the app or the sysadmin) explicitly choose to be more compliant to the RFC. There's no harm in that.
RE: [PATCHv3 net-next 2/5] sctp: add pf_expose per netns and sock and asoc
From: 'Marcelo Ricardo Leitner'
Quoted 26 lines
Sent: 25 October 2019 14:22
Quoted 24 lines · David Laight
From: Marcelo Ricardo Leitner
Quoted 1 line
Sent: 25 October 2019 04:24
...
Quoted 20 lines
Quoted 6 lines
net/sctp/socket.c +0
-2@@ -5521,8 +5522,16 @@ static int sctp_getsockopt_peer_addr_info(struct sock *sk, int len, transport =sctp_addr_id2transport (sk, &pinfo.spinfo_address, pinfo.spinfo_assoc_id); -if (!transport) -return -EINVAL ;net/sctp/socket.c static int sctp_getsockopt_peer_addr_info(struct sock *sk, int len, · line 5534
Quoted 10 lines
net/sctp/socket.c +10
-0+if (!transport) { + retval = -EINVAL ; + goto out; + } + +if (transport->state =SCTP_PF && + transport->asoc->pf_expose =SCTP_PF_EXPOSE_DISABLE ) { + retval = -EACCES ; + goto out; + }As is on v3, this is NOT an UAPI violation. The user has to explicitly set the system or the socket into the disabled state in order to trigger this new check.
Quoted 4 lines
Quoted 1 line
Only because the default isn't to be backwards compatible with the
^^^^^You meant "is", right? Then we're agreeing.
No, I meant isn't.
The application must see a backwards compatible interface unless the application itself requests something different.
The sysadmin can't be allowed to change the API seen by old applications.
AFAICT if the protocol part of PF is enabled (which handles primary path failure better than the older version) and ' transport->state = SCTP_PF' is true then an old application binary will get a completely unexpected -EACCESS rather than a valid state (out of the old valid states) if it requests 'peer addr_info'.
You cannot assume that just because some sysctl is set (because someone building a distribution suddenly decided it was a 'good idea') that an application binary will not fall in a big heap due to an error condition that couldn't ever happen before.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK Registration No: 1397386 (Wales)
'Marcelo Ricardo Leitner'
maintainerRe: [PATCHv3 net-next 2/5] sctp: add pf_expose per netns and sock and asoc
Quoted 27 lines · David Laight
From: 'Marcelo Ricardo Leitner'
Quoted 26 lines
Sent: 25 October 2019 14:22
Quoted 24 lines · David Laight
From: Marcelo Ricardo Leitner
Quoted 1 line
Sent: 25 October 2019 04:24
...
Quoted 20 lines
Quoted 6 lines
net/sctp/socket.c +0
-2@@ -5521,8 +5522,16 @@ static int sctp_getsockopt_peer_addr_info(struct sock *sk, int len, transport =sctp_addr_id2transport (sk, &pinfo.spinfo_address, pinfo.spinfo_assoc_id); -if (!transport) -return -EINVAL ;net/sctp/socket.c static int sctp_getsockopt_peer_addr_info(struct sock *sk, int len, · line 5534
Quoted 10 lines
net/sctp/socket.c +10
-0+if (!transport) { + retval = -EINVAL ; + goto out; + } + +if (transport->state =SCTP_PF && + transport->asoc->pf_expose =SCTP_PF_EXPOSE_DISABLE ) { + retval = -EACCES ; + goto out; + }As is on v3, this is NOT an UAPI violation. The user has to explicitly set the system or the socket into the disabled state in order to trigger this new check.
Quoted 6 lines
Quoted 4 lines
Quoted 1 line
Only because the default isn't to be backwards compatible with the
^^^^^You meant "is", right? Then we're agreeing.
No, I meant isn't.
Then you missed this detail in the patch. The default here IS to be backwards compatible.
Quoted 3 lines
The application must see a backwards compatible interface unless the application itself requests something different.
The sysadmin can't be allowed to change the API seen by old applications.
Disagree. Sysadmins should be able to harden their systems as much as they want/need. Yet, if that causes issues with old applications, that's on them.
Quoted 10 lines
AFAICT if the protocol part of PF is enabled (which handles primary path failure better than the older version) and '
transport->state=SCTP_PF' is true then an old application binary will get a completely unexpected-EACCESSrather than a valid state (out of the old valid states) if it requests 'peeraddr_info'.You cannot assume that just because some sysctl is set (because someone building a distribution suddenly decided it was a 'good idea') that an application binary will not fall in a big heap due to an error condition that couldn't ever happen before.
Agree, but that assumption doesn't have a room here. If the distribution decided to harden the system, that's on them. Ditto for many many other decisions, like having SELinux policies to block sshd to bind only on port 22 and so, or for building the kernel without SCTP_COOKIE_HMAC_MD5 because they think it's weak, etc.
Marcelo