From: Vlad Yasevich <vyasevich@gmail.com>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: linux-sctp@vger.kernel.org,
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
netdev@vger.kernel.org, davem@davemloft.net
Subject: Re: [PATCH net-next stable v2] sctp: fully initialize sctp_outq in sctp_outq_init
Date: Wed, 12 Jun 2013 18:40:16 +0000 [thread overview]
Message-ID: <51B8C090.8050502@gmail.com> (raw)
In-Reply-To: <1371061604-27312-1-git-send-email-nhorman@tuxdriver.com>
On 06/12/2013 02:26 PM, Neil Horman wrote:
> In commit 2f94aabd9f6c925d77aecb3ff020f1cc12ed8f86
> (refactor sctp_outq_teardown to insure proper re-initalization)
> we modified sctp_outq_teardown to use sctp_outq_init to fully re-initalize the
> outq structure. Steve West recently asked me why I removed the q->error = 0
> initalization from sctp_outq_teardown. I did so because I was operating under
> the impression that sctp_outq_init would properly initalize that value for us,
> but it doesn't. sctp_outq_init operates under the assumption that the outq
> struct is all 0's (as it is when called from sctp_association_init), but using
> it in __sctp_outq_teardown violates that assumption. We should do a memset in
> sctp_outq_init to ensure that the entire structure is in a known state there
> instead.
>
> Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
> Reported-by: "West, Steve (NSN - US/Fort Worth)" <steve.west@nsn.com>
> CC: Vlad Yasevich <vyasevich@gmail.com>
Acked-by: Vlad Yasevich <vyasevich@gmail.com>
-vlad
> CC: netdev@vger.kernel.org
> CC: davem@davemloft.net
> ---
> net/sctp/outqueue.c | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/net/sctp/outqueue.c b/net/sctp/outqueue.c
> index 32a4625..be35e2d 100644
> --- a/net/sctp/outqueue.c
> +++ b/net/sctp/outqueue.c
> @@ -206,6 +206,8 @@ static inline int sctp_cacc_skip(struct sctp_transport *primary,
> */
> void sctp_outq_init(struct sctp_association *asoc, struct sctp_outq *q)
> {
> + memset(q, 0, sizeof(struct sctp_outq));
> +
> q->asoc = asoc;
> INIT_LIST_HEAD(&q->out_chunk_list);
> INIT_LIST_HEAD(&q->control_chunk_list);
> @@ -213,11 +215,7 @@ void sctp_outq_init(struct sctp_association *asoc, struct sctp_outq *q)
> INIT_LIST_HEAD(&q->sacked);
> INIT_LIST_HEAD(&q->abandoned);
>
> - q->fast_rtx = 0;
> - q->outstanding_bytes = 0;
> q->empty = 1;
> - q->cork = 0;
> - q->out_qlen = 0;
> }
>
> /* Free the outqueue structure and any related pending chunks.
>
WARNING: multiple messages have this Message-ID (diff)
From: Vlad Yasevich <vyasevich@gmail.com>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: linux-sctp@vger.kernel.org,
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
netdev@vger.kernel.org, davem@davemloft.net
Subject: Re: [PATCH net-next stable v2] sctp: fully initialize sctp_outq in sctp_outq_init
Date: Wed, 12 Jun 2013 14:40:16 -0400 [thread overview]
Message-ID: <51B8C090.8050502@gmail.com> (raw)
In-Reply-To: <1371061604-27312-1-git-send-email-nhorman@tuxdriver.com>
On 06/12/2013 02:26 PM, Neil Horman wrote:
> In commit 2f94aabd9f6c925d77aecb3ff020f1cc12ed8f86
> (refactor sctp_outq_teardown to insure proper re-initalization)
> we modified sctp_outq_teardown to use sctp_outq_init to fully re-initalize the
> outq structure. Steve West recently asked me why I removed the q->error = 0
> initalization from sctp_outq_teardown. I did so because I was operating under
> the impression that sctp_outq_init would properly initalize that value for us,
> but it doesn't. sctp_outq_init operates under the assumption that the outq
> struct is all 0's (as it is when called from sctp_association_init), but using
> it in __sctp_outq_teardown violates that assumption. We should do a memset in
> sctp_outq_init to ensure that the entire structure is in a known state there
> instead.
>
> Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
> Reported-by: "West, Steve (NSN - US/Fort Worth)" <steve.west@nsn.com>
> CC: Vlad Yasevich <vyasevich@gmail.com>
Acked-by: Vlad Yasevich <vyasevich@gmail.com>
-vlad
> CC: netdev@vger.kernel.org
> CC: davem@davemloft.net
> ---
> net/sctp/outqueue.c | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/net/sctp/outqueue.c b/net/sctp/outqueue.c
> index 32a4625..be35e2d 100644
> --- a/net/sctp/outqueue.c
> +++ b/net/sctp/outqueue.c
> @@ -206,6 +206,8 @@ static inline int sctp_cacc_skip(struct sctp_transport *primary,
> */
> void sctp_outq_init(struct sctp_association *asoc, struct sctp_outq *q)
> {
> + memset(q, 0, sizeof(struct sctp_outq));
> +
> q->asoc = asoc;
> INIT_LIST_HEAD(&q->out_chunk_list);
> INIT_LIST_HEAD(&q->control_chunk_list);
> @@ -213,11 +215,7 @@ void sctp_outq_init(struct sctp_association *asoc, struct sctp_outq *q)
> INIT_LIST_HEAD(&q->sacked);
> INIT_LIST_HEAD(&q->abandoned);
>
> - q->fast_rtx = 0;
> - q->outstanding_bytes = 0;
> q->empty = 1;
> - q->cork = 0;
> - q->out_qlen = 0;
> }
>
> /* Free the outqueue structure and any related pending chunks.
>
next prev parent reply other threads:[~2013-06-12 18:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 18:26 [PATCH net-next stable v2] sctp: fully initialize sctp_outq in sctp_outq_init Neil Horman
2013-06-12 18:26 ` Neil Horman
2013-06-12 18:40 ` Vlad Yasevich [this message]
2013-06-12 18:40 ` Vlad Yasevich
2013-06-13 9:44 ` David Miller
2013-06-13 9:44 ` David Miller
2013-06-13 13:08 ` Neil Horman
2013-06-13 13:08 ` Neil Horman
2013-06-14 1:06 ` David Miller
2013-06-14 1:06 ` 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=51B8C090.8050502@gmail.com \
--to=vyasevich@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-sctp@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=sergei.shtylyov@cogentembedded.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.