From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: linux-sctp@vger.kernel.org
Subject: Re: [PATCH 2/2] sctp: COOKIE-ACK should back to where the COOKIE-ECHO
Date: Wed, 28 Apr 2010 02:35:11 +0000 [thread overview]
Message-ID: <4BD79EDF.9070407@hp.com> (raw)
In-Reply-To: <4BD174DC.40308@cn.fujitsu.com>
Hi Wei
Wei Yongjun wrote:
> This patch fixed to send COOKIE-ACK back to where the COOKIE-ECHO
> came from, and if COOKIE ACK is sent to an UNCONFIRMED address,
> bundled it with a HEARTBEAT including a nonce. Based on RFC4960:
>
> Section 6.4. Multi-Homed SCTP Endpoints
>
> An endpoint SHOULD transmit reply chunks (e.g., SACK, HEARTBEAT ACK,
> etc.) to the same destination transport address from which it
> received the DATA or control chunk to which it is replying.
>
> Section 5.4. Path Verification:
>
> - A COOKIE ACK MAY be sent to an UNCONFIRMED address, but it MUST be
> bundled with a HEARTBEAT including a nonce. An implementation
> that does NOT support bundling MUST NOT send a COOKIE ACK to an
> UNCONFIRMED address.
>
> Signed-off-by: Wei Yongjun <yjwei@cn.fujitsu.com>
> ---
> net/sctp/output.c | 22 ++++++++++++++++++++++
> net/sctp/outqueue.c | 1 +
> net/sctp/sm_make_chunk.c | 3 +++
> 3 files changed, 26 insertions(+), 0 deletions(-)
>
> diff --git a/net/sctp/output.c b/net/sctp/output.c
> index fad261d..a68a57d 100644
> --- a/net/sctp/output.c
> +++ b/net/sctp/output.c
> @@ -260,6 +260,25 @@ static sctp_xmit_t sctp_packet_bundle_sack(struct sctp_packet *pkt,
> return retval;
> }
>
> +/* Try to bundle a HEARTBEAT with the packet. */
> +static sctp_xmit_t sctp_packet_bundle_hb(struct sctp_packet *pkt,
> + struct sctp_chunk *chunk)
> +{
> + sctp_xmit_t retval = SCTP_XMIT_OK;
> +
> + if (pkt->transport->state = SCTP_UNCONFIRMED &&
> + chunk->chunk_hdr->type = SCTP_CID_COOKIE_ACK) {
> + struct sctp_transport *transport = pkt->transport;
> + struct sctp_chunk *hb;
> +
> + hb = sctp_make_heartbeat(transport->asoc, transport);
> + if (hb)
> + retval = sctp_packet_append_chunk(pkt, hb);
> + }
> +
> + return retval;
> +}
> +
> /* Append a chunk to the offered packet reporting back any inability to do
> * so.
> */
> @@ -329,6 +348,9 @@ sctp_xmit_t sctp_packet_append_chunk(struct sctp_packet *packet,
> list_add_tail(&chunk->list, &packet->chunk_list);
> packet->size += chunk_len;
> chunk->transport = packet->transport;
> +
> + /* Try to bundle HEARTBEAT chunk */
> + retval = sctp_packet_bundle_hb(packet, chunk);
Not sure if this is the right place. Also, this will add the HB after cookie-ACK.
I am wondering if it should go before. Seems a more correct thing to do is
to elicit HB-ACK before any further data might flow over the transport.
Also, what about all the HB related things like error counters, timers, etc...
Seems that we should also do that.
May be we can just cue the HB to the control queue if we are not replying to the
source of INIT-ACK?
> finish:
> return retval;
> }
> diff --git a/net/sctp/outqueue.c b/net/sctp/outqueue.c
> index abfc0b8..322ecd1 100644
> --- a/net/sctp/outqueue.c
> +++ b/net/sctp/outqueue.c
> @@ -788,6 +788,7 @@ static int sctp_outq_flush(struct sctp_outq *q, int rtx_timeout)
> */
> if (chunk->chunk_hdr->type != SCTP_CID_HEARTBEAT &&
> chunk->chunk_hdr->type != SCTP_CID_HEARTBEAT_ACK &&
> + chunk->chunk_hdr->type != SCTP_CID_COOKIE_ACK &&
> chunk->chunk_hdr->type != SCTP_CID_ASCONF_ACK)
> new_transport = asoc->peer.active_path;
> }
> diff --git a/net/sctp/sm_make_chunk.c b/net/sctp/sm_make_chunk.c
> index 04c45dd..b9f08f0 100644
> --- a/net/sctp/sm_make_chunk.c
> +++ b/net/sctp/sm_make_chunk.c
> @@ -584,6 +584,9 @@ struct sctp_chunk *sctp_make_cookie_ack(const struct sctp_association *asoc,
> if (retval && chunk)
> retval->transport = chunk->transport;
>
> + if (retval && !retval->transport)
> + retval->dest = chunk->source;
> +
This one is good, but I am thinking that transport assignment may be incorrect.
Like I said before, when we are restarting, the transport assigned is from the
existing association, but the packet is transmitted on the temporary association
that's about to vanish. Not sure if this is ok.
> return retval;
> }
>
next prev parent reply other threads:[~2010-04-28 2:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-23 10:22 [PATCH 2/2] sctp: COOKIE-ACK should back to where the COOKIE-ECHO Wei Yongjun
2010-04-23 15:09 ` Vlad Yasevich
2010-04-27 3:31 ` Wei Yongjun
2010-04-28 2:35 ` Vlad Yasevich [this message]
2010-04-28 3:50 ` Wei Yongjun
2010-04-30 1:14 ` 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=4BD79EDF.9070407@hp.com \
--to=vladislav.yasevich@hp.com \
--cc=linux-sctp@vger.kernel.org \
/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.