[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20181119.124213.78418049979979609.davem@davemloft.net>
Date: Mon, 19 Nov 2018 12:42:13 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: lucien.xin@...il.com
Cc: netdev@...r.kernel.org, linux-sctp@...r.kernel.org,
marcelo.leitner@...il.com, nhorman@...driver.com
Subject: Re: [PATCHv2 net] sctp: not allow to set asoc prsctp_enable by
sockopt
From: Xin Long <lucien.xin@...il.com>
Date: Sun, 18 Nov 2018 15:21:53 +0800
> As rfc7496#section4.5 says about SCTP_PR_SUPPORTED:
>
> This socket option allows the enabling or disabling of the
> negotiation of PR-SCTP support for future associations. For existing
> associations, it allows one to query whether or not PR-SCTP support
> was negotiated on a particular association.
>
> It means only sctp sock's prsctp_enable can be set.
>
> Note that for the limitation of SCTP_{CURRENT|ALL}_ASSOC, we will
> add it when introducing SCTP_{FUTURE|CURRENT|ALL}_ASSOC for linux
> sctp in another patchset.
>
> v1->v2:
> - drop the params.assoc_id check as Neil suggested.
>
> Fixes: 28aa4c26fce2 ("sctp: add SCTP_PR_SUPPORTED on sctp sockopt")
> Reported-by: Ying Xu <yinxu@...hat.com>
> Signed-off-by: Xin Long <lucien.xin@...il.com>
Applied and queued up for -stable.
Powered by blists - more mailing lists