From: Vlad Yasevich <vyasevich@gmail.com>
To: Chang Xiangzhong <changxiangzhong@gmail.com>,
nhorman@tuxdriver.com, davem@davemloft.net
Cc: linux-sctp@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, dreibh@simula.no
Subject: Re: [PATCH 1/1] net: sctp: bug fixing when sctp path recovers
Date: Wed, 13 Nov 2013 02:37:45 +0000 [thread overview]
Message-ID: <5282E5F9.5000506@gmail.com> (raw)
In-Reply-To: <1384306486-31345-1-git-send-email-changxiangzhong@gmail.com>
On 11/12/2013 08:34 PM, Chang Xiangzhong wrote:
> Look for the __two__ most recently used path/transport and set to active_path
> and retran_path respectively
>
> Signed-off-by: changxiangzhong@gmail.com
> ---
> net/sctp/associola.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/net/sctp/associola.c b/net/sctp/associola.c
> index ab67efc..070011a 100644
> --- a/net/sctp/associola.c
> +++ b/net/sctp/associola.c
> @@ -913,11 +913,15 @@ void sctp_assoc_control_transport(struct sctp_association *asoc,
> if (!first || t->last_time_heard > first->last_time_heard) {
> second = first;
> first = t;
> + continue;
> }
> if (!second || t->last_time_heard > second->last_time_heard)
> second = t;
You might as well remove this bit and then you don't need a continue.
> }
>
> + if (!second)
> + second = first;
> +
This needs to move down 1 more block. Set the second transport after we
check to see if the primary is back up and we need to go back to using it.
-vlad
> /* RFC 2960 6.4 Multi-Homed SCTP Endpoints
> *
> * By default, an endpoint should always transmit to the
>
WARNING: multiple messages have this Message-ID (diff)
From: Vlad Yasevich <vyasevich@gmail.com>
To: Chang Xiangzhong <changxiangzhong@gmail.com>,
nhorman@tuxdriver.com, davem@davemloft.net
Cc: linux-sctp@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, dreibh@simula.no
Subject: Re: [PATCH 1/1] net: sctp: bug fixing when sctp path recovers
Date: Tue, 12 Nov 2013 21:37:45 -0500 [thread overview]
Message-ID: <5282E5F9.5000506@gmail.com> (raw)
In-Reply-To: <1384306486-31345-1-git-send-email-changxiangzhong@gmail.com>
On 11/12/2013 08:34 PM, Chang Xiangzhong wrote:
> Look for the __two__ most recently used path/transport and set to active_path
> and retran_path respectively
>
> Signed-off-by: changxiangzhong@gmail.com
> ---
> net/sctp/associola.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/net/sctp/associola.c b/net/sctp/associola.c
> index ab67efc..070011a 100644
> --- a/net/sctp/associola.c
> +++ b/net/sctp/associola.c
> @@ -913,11 +913,15 @@ void sctp_assoc_control_transport(struct sctp_association *asoc,
> if (!first || t->last_time_heard > first->last_time_heard) {
> second = first;
> first = t;
> + continue;
> }
> if (!second || t->last_time_heard > second->last_time_heard)
> second = t;
You might as well remove this bit and then you don't need a continue.
> }
>
> + if (!second)
> + second = first;
> +
This needs to move down 1 more block. Set the second transport after we
check to see if the primary is back up and we need to go back to using it.
-vlad
> /* RFC 2960 6.4 Multi-Homed SCTP Endpoints
> *
> * By default, an endpoint should always transmit to the
>
next prev parent reply other threads:[~2013-11-13 2:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 1:34 [PATCH 1/1] net: sctp: bug fixing when sctp path recovers Chang Xiangzhong
2013-11-13 1:34 ` Chang Xiangzhong
2013-11-13 2:37 ` Vlad Yasevich [this message]
2013-11-13 2:37 ` Vlad Yasevich
2013-11-13 2:54 ` Chang
2013-11-13 2:54 ` Chang
2013-11-13 8:44 ` Daniel Borkmann
2013-11-13 8:44 ` Daniel Borkmann
2013-11-13 19:06 ` Chang
2013-11-13 19:06 ` Chang
2013-11-13 19:10 ` Daniel Borkmann
2013-11-13 19:10 ` Daniel Borkmann
2013-11-13 20:48 ` Chang
2013-11-13 20:48 ` Chang
2013-11-13 21:23 ` Chang
2013-11-13 21:23 ` Chang
2013-11-13 21:31 ` Daniel Borkmann
2013-11-13 21:31 ` Daniel Borkmann
2013-11-13 21:39 ` Vlad Yasevich
2013-11-13 21:39 ` Vlad Yasevich
2013-11-13 14:22 ` Vlad Yasevich
2013-11-13 14:22 ` Vlad Yasevich
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=5282E5F9.5000506@gmail.com \
--to=vyasevich@gmail.com \
--cc=changxiangzhong@gmail.com \
--cc=davem@davemloft.net \
--cc=dreibh@simula.no \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sctp@vger.kernel.org \
--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.