All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: Xin Long <lucien.xin@gmail.com>
Cc: network dev <netdev@vger.kernel.org>,
	linux-sctp@vger.kernel.org, davem@davemloft.net,
	Neil Horman <nhorman@tuxdriver.com>
Subject: Re: [PATCH net] sctp: reinit stream if stream outcnt has been change by sinit in sendmsg
Date: Mon, 15 Jan 2018 19:44:03 +0000	[thread overview]
Message-ID: <20180115194403.GI7571@localhost.localdomain> (raw)
In-Reply-To: <1330acc7e606c50a26e7f972eb9875da82ad8ce9.1516006879.git.lucien.xin@gmail.com>

On Mon, Jan 15, 2018 at 05:01:19PM +0800, Xin Long wrote:
> After introducing sctp_stream structure, sctp uses stream->outcnt as the
> out stream nums instead of c.sinit_num_ostreams.
> 
> However when users use sinit in cmsg, it only updates c.sinit_num_ostreams
> in sctp_sendmsg. At that moment, stream->outcnt is still using previous
> value. If it's value is not updated, the sinit_num_ostreams of sinit could
> not really work.
> 
> This patch is to fix it by updating stream->outcnt and reiniting stream
> if stream outcnt has been change by sinit in sendmsg.
> 
> Fixes: a83863174a61 ("sctp: prepare asoc stream for stream reconf")
> Signed-off-by: Xin Long <lucien.xin@gmail.com>

Acked-by: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>

> ---
>  net/sctp/socket.c | 10 ++++++++--
>  1 file changed, 8 insertions(+), 2 deletions(-)
> 
> diff --git a/net/sctp/socket.c b/net/sctp/socket.c
> index 9b01e99..15ae018 100644
> --- a/net/sctp/socket.c
> +++ b/net/sctp/socket.c
> @@ -1883,8 +1883,14 @@ static int sctp_sendmsg(struct sock *sk, struct msghdr *msg, size_t msg_len)
>  		 */
>  		if (sinit) {
>  			if (sinit->sinit_num_ostreams) {
> -				asoc->c.sinit_num_ostreams > -					sinit->sinit_num_ostreams;
> +				__u16 outcnt = sinit->sinit_num_ostreams;
> +
> +				asoc->c.sinit_num_ostreams = outcnt;
> +				/* outcnt has been changed, so re-init stream */
> +				err = sctp_stream_init(&asoc->stream, outcnt, 0,
> +						       GFP_KERNEL);
> +				if (err)
> +					goto out_free;
>  			}
>  			if (sinit->sinit_max_instreams) {
>  				asoc->c.sinit_max_instreams > -- 
> 2.1.0
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-sctp" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

WARNING: multiple messages have this Message-ID (diff)
From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: Xin Long <lucien.xin@gmail.com>
Cc: network dev <netdev@vger.kernel.org>,
	linux-sctp@vger.kernel.org, davem@davemloft.net,
	Neil Horman <nhorman@tuxdriver.com>
Subject: Re: [PATCH net] sctp: reinit stream if stream outcnt has been change by sinit in sendmsg
Date: Mon, 15 Jan 2018 17:44:03 -0200	[thread overview]
Message-ID: <20180115194403.GI7571@localhost.localdomain> (raw)
In-Reply-To: <1330acc7e606c50a26e7f972eb9875da82ad8ce9.1516006879.git.lucien.xin@gmail.com>

On Mon, Jan 15, 2018 at 05:01:19PM +0800, Xin Long wrote:
> After introducing sctp_stream structure, sctp uses stream->outcnt as the
> out stream nums instead of c.sinit_num_ostreams.
> 
> However when users use sinit in cmsg, it only updates c.sinit_num_ostreams
> in sctp_sendmsg. At that moment, stream->outcnt is still using previous
> value. If it's value is not updated, the sinit_num_ostreams of sinit could
> not really work.
> 
> This patch is to fix it by updating stream->outcnt and reiniting stream
> if stream outcnt has been change by sinit in sendmsg.
> 
> Fixes: a83863174a61 ("sctp: prepare asoc stream for stream reconf")
> Signed-off-by: Xin Long <lucien.xin@gmail.com>

Acked-by: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>

> ---
>  net/sctp/socket.c | 10 ++++++++--
>  1 file changed, 8 insertions(+), 2 deletions(-)
> 
> diff --git a/net/sctp/socket.c b/net/sctp/socket.c
> index 9b01e99..15ae018 100644
> --- a/net/sctp/socket.c
> +++ b/net/sctp/socket.c
> @@ -1883,8 +1883,14 @@ static int sctp_sendmsg(struct sock *sk, struct msghdr *msg, size_t msg_len)
>  		 */
>  		if (sinit) {
>  			if (sinit->sinit_num_ostreams) {
> -				asoc->c.sinit_num_ostreams =
> -					sinit->sinit_num_ostreams;
> +				__u16 outcnt = sinit->sinit_num_ostreams;
> +
> +				asoc->c.sinit_num_ostreams = outcnt;
> +				/* outcnt has been changed, so re-init stream */
> +				err = sctp_stream_init(&asoc->stream, outcnt, 0,
> +						       GFP_KERNEL);
> +				if (err)
> +					goto out_free;
>  			}
>  			if (sinit->sinit_max_instreams) {
>  				asoc->c.sinit_max_instreams =
> -- 
> 2.1.0
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-sctp" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

  parent reply	other threads:[~2018-01-15 19:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-15  9:01 [PATCH net] sctp: reinit stream if stream outcnt has been change by sinit in sendmsg Xin Long
2018-01-15  9:01 ` Xin Long
2018-01-15 12:40 ` Neil Horman
2018-01-15 12:40   ` Neil Horman
2018-01-15 19:44 ` Marcelo Ricardo Leitner [this message]
2018-01-15 19:44   ` Marcelo Ricardo Leitner
2018-01-16 19:20 ` David Miller
2018-01-16 19:20   ` David Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180115194403.GI7571@localhost.localdomain \
    --to=marcelo.leitner@gmail.com \
    --cc=davem@davemloft.net \
    --cc=linux-sctp@vger.kernel.org \
    --cc=lucien.xin@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@tuxdriver.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.