From: Vlad Yasevich <vyasevich@gmail.com>
To: Karl Heiss <kheiss@gmail.com>, netdev@vger.kernel.org
Cc: linux-sctp@vger.kernel.org, davem@davemloft.net, nhorman@tuxdriver.com
Subject: Re: [PATCH v4 net] net: sctp: Don't transition to PF state when transport has exhausted 'Path.Max.Retrans'.
Date: Fri, 25 Apr 2014 15:58:40 -0400 [thread overview]
Message-ID: <535ABE70.6020200@gmail.com> (raw)
In-Reply-To: <1398450390-23630-1-git-send-email-kheiss@gmail.com>
On 04/25/2014 02:26 PM, Karl Heiss wrote:
> Don't transition to the PF state on every strike after 'Path.Max.Retrans'.
> Per draft-ietf-tsvwg-sctp-failover-03 Section 5.1.6:
>
> Additional (PMR - PFMR) consecutive timeouts on a PF destination
> confirm the path failure, upon which the destination transitions to the
> Inactive state. As described in [RFC4960], the sender (i) SHOULD notify
> ULP about this state transition, and (ii) transmit heartbeats to the
> Inactive destination at a lower frequency as described in Section 8.3 of
> [RFC4960].
>
> This also prevents sending SCTP_ADDR_UNREACHABLE to the user as the state
> bounces between SCTP_INACTIVE and SCTP_PF for each subsequent strike.
>
> Signed-off-by: Karl Heiss <kheiss@gmail.com>
Hi Karl
Looks good. Thanks.
Acked-by: Vlad Yasevich <vyasevich@gmail.com>
-vlad
> ---
> Changes in v2:
> - Flesh out commit message
>
> Changes in v3:
> - Compare transport state instead of pathmaxrxt
>
> Changes in v4:
> - Simplify transport state comparison
>
> net/sctp/sm_sideeffect.c | 7 +++----
> 1 files changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/net/sctp/sm_sideeffect.c b/net/sctp/sm_sideeffect.c
> index 5d6883f..f900f8e 100644
> --- a/net/sctp/sm_sideeffect.c
> +++ b/net/sctp/sm_sideeffect.c
> @@ -496,11 +496,10 @@ static void sctp_do_8_2_transport_strike(sctp_cmd_seq_t *commands,
>
> /* If the transport error count is greater than the pf_retrans
> * threshold, and less than pathmaxrtx, and if the current state
> - * is not SCTP_UNCONFIRMED, then mark this transport as Partially
> - * Failed, see SCTP Quick Failover Draft, section 5.1
> + * is SCTP_ACTIVE, then mark this transport as Partially Failed,
> + * see SCTP Quick Failover Draft, section 5.1
> */
> - if ((transport->state != SCTP_PF) &&
> - (transport->state != SCTP_UNCONFIRMED) &&
> + if ((transport->state == SCTP_ACTIVE) &&
> (asoc->pf_retrans < transport->pathmaxrxt) &&
> (transport->error_count > asoc->pf_retrans)) {
>
>
next prev parent reply other threads:[~2014-04-25 19:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-25 18:26 [PATCH v4 net] net: sctp: Don't transition to PF state when transport has exhausted 'Path.Max.Retrans' Karl Heiss
2014-04-25 19:58 ` Vlad Yasevich [this message]
2014-04-28 3:41 ` 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=535ABE70.6020200@gmail.com \
--to=vyasevich@gmail.com \
--cc=davem@davemloft.net \
--cc=kheiss@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).