Re: [PATCH] sctp: allow setting path_maxrxt independent of SPP_PMTUD_ENABLE

[Vlad Yasevich <vladislav.yasevich@hp.com>]

Andrei Pelinescu-Onciul wrote:
> 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.
> 

applied, thanks

-vlad

> Signed-off-by: Andrei Pelinescu-Onciul <andrei@iptel.org>
> ---
>  net/sctp/socket.c |    7 +++----
>  1 files changed, 3 insertions(+), 4 deletions(-)
> 
> diff --git a/net/sctp/socket.c b/net/sctp/socket.c
> index 2a21d50..1b04ade 100644
> --- a/net/sctp/socket.c
> +++ b/net/sctp/socket.c
> @@ -2300,11 +2300,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) {