[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190819145843.GE2870@localhost.localdomain>
Date: Mon, 19 Aug 2019 11:58:43 -0300
From: Marcelo Ricardo Leitner <marcelo.leitner@...il.com>
To: Xin Long <lucien.xin@...il.com>
Cc: network dev <netdev@...r.kernel.org>, linux-sctp@...r.kernel.org,
Neil Horman <nhorman@...driver.com>, davem@...emloft.net
Subject: Re: [PATCH net-next 4/8] sctp: add SCTP_ASCONF_SUPPORTED sockopt
On Mon, Aug 19, 2019 at 10:02:46PM +0800, Xin Long wrote:
> +static int sctp_setsockopt_asconf_supported(struct sock *sk,
> + char __user *optval,
> + unsigned int optlen)
> +{
> + struct sctp_assoc_value params;
> + struct sctp_association *asoc;
> + struct sctp_endpoint *ep;
> + int retval = -EINVAL;
> +
> + if (optlen != sizeof(params))
> + goto out;
> +
> + if (copy_from_user(¶ms, optval, optlen)) {
> + retval = -EFAULT;
> + goto out;
> + }
> +
> + asoc = sctp_id2assoc(sk, params.assoc_id);
> + if (!asoc && params.assoc_id != SCTP_FUTURE_ASSOC &&
> + sctp_style(sk, UDP))
> + goto out;
> +
> + ep = sctp_sk(sk)->ep;
> + ep->asconf_enable = !!params.assoc_value;
Considering this will be negotiated on handshake, shouldn't it deny
changes to Established asocs? (Same for Auth)
> +
> + if (ep->asconf_enable && ep->auth_enable) {
> + sctp_auth_ep_add_chunkid(ep, SCTP_CID_ASCONF);
> + sctp_auth_ep_add_chunkid(ep, SCTP_CID_ASCONF_ACK);
> + }
> +
> + retval = 0;
> +
> +out:
> + return retval;
> +}
Powered by blists - more mailing lists