sctp: allow setting path_maxrxt independent of SPP_PMTUD_ENABLE
Since draft-ietf-tsvwg-sctpsocket-15.txt, setting the SPP_MTUD_ENABLE flag when changing pathmaxrxt via the SCTP_PEER_ADDR_PARAMS setsockopt is not required any longer. Signed-off-by: Andrei Pelinescu-Onciul <andrei@iptel.org> Signed-off-by: Vlad Yasevich <vladislav.yasevich@hp.com>
This commit is contained in:
parent
90f2f5318b
commit
37051f7386
|
@ -2311,11 +2311,10 @@ static int sctp_apply_peer_addr_params(struct sctp_paddrparams *params,
|
|||
}
|
||||
}
|
||||
|
||||
/* Note that unless the spp_flag is set to SPP_PMTUD_ENABLE the value
|
||||
* of this field is ignored. Note also that a value of zero
|
||||
* indicates the current setting should be left unchanged.
|
||||
/* Note that a value of zero indicates the current setting should be
|
||||
left unchanged.
|
||||
*/
|
||||
if ((params->spp_flags & SPP_PMTUD_ENABLE) && params->spp_pathmaxrxt) {
|
||||
if (params->spp_pathmaxrxt) {
|
||||
if (trans) {
|
||||
trans->pathmaxrxt = params->spp_pathmaxrxt;
|
||||
} else if (asoc) {
|
||||
|
|
Loading…
Reference in a new issue