netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: xufengzhang.main@gmail.com
Cc: vyasevich@gmail.com, sri@us.ibm.com, linux-sctp@vger.kernel.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sctp: Make "Invalid Stream Identifier" ERROR follows SACK when bundling
Date: Sun, 22 Jul 2012 12:45:14 -0700 (PDT)	[thread overview]
Message-ID: <20120722.124514.239340989320198501.davem@davemloft.net> (raw)
In-Reply-To: <1342677450-21810-1-git-send-email-xufengzhang.main@gmail.com>

From: <xufengzhang.main@gmail.com>
Date: Thu, 19 Jul 2012 13:57:30 +0800

> When "Invalid Stream Identifier" ERROR happens after process the
> received DATA chunks, this ERROR chunk is enqueued into outqueue
> before SACK chunk, so when bundling ERROR chunk with SACK chunk,
> the ERROR chunk is always placed first in the packet because of
> the chunk's position in the outqueue.
> This violates sctp specification:
>     RFC 4960 6.5. Stream Identifier and Stream Sequence Number
>     ...The endpoint may bundle the ERROR chunk in the same
>     packet as the SACK as long as the ERROR follows the SACK.
> So we must place SACK first when bundling "Invalid Stream Identifier"
> ERROR and SACK in one packet.
> Although we can do that by enqueue SACK chunk into outqueue before
> ERROR chunk, it will violate the side-effect interpreter processing.
> It's easy to do this job when dequeue chunks from the outqueue,
> by this way, we introduce a flag 'has_isi_err' which indicate
> whether or not the "Invalid Stream Identifier" ERROR happens.
> 
> Signed-off-by: Xufeng Zhang <xufeng.zhang@windriver.com>

Can some SCTP experts please review this?

  reply	other threads:[~2012-07-22 19:45 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-19  5:57 [PATCH] sctp: Make "Invalid Stream Identifier" ERROR follows SACK when bundling xufengzhang.main
2012-07-22 19:45 ` David Miller [this message]
2012-07-23  0:49 ` Neil Horman
2012-07-23  2:30   ` xufeng zhang
2012-07-23 12:14     ` Neil Horman
2012-07-24  1:53       ` Xufeng Zhang
     [not found]       ` <500DFF5A.20203@windriver.com>
2012-07-24 11:38         ` Neil Horman
2012-07-25  2:34           ` Xufeng Zhang
2012-07-25 11:15             ` Neil Horman
2012-07-23  5:16 ` xufeng zhang
2012-07-24  2:27   ` Vlad Yasevich
2012-07-24  3:02     ` xufeng zhang
2012-07-24 14:05       ` Vlad Yasevich
2012-07-25  2:28         ` Xufeng Zhang
2012-07-25  7:16           ` Vlad Yasevich
2012-07-25  8:05             ` Xufeng Zhang
2012-07-25  9:22               ` Xufeng Zhang
2012-07-25 11:27                 ` Neil Horman
2012-07-26  1:34                   ` Xufeng Zhang
2012-07-25 15:00                 ` Vlad Yasevich
2012-07-26  1:30                   ` Xufeng Zhang
2012-07-26  2:45                     ` Vlad Yasevich
2012-07-26  2:50                     ` Xufeng Zhang
2012-07-26  2:55                       ` Vlad Yasevich
2012-07-26  3:12                         ` Xufeng Zhang
2012-07-27 21:22                           ` Vlad Yasevich
2012-07-30  4:58                             ` Xufeng Zhang
2012-07-30  5:47                               ` Xufeng Zhang
2012-07-31  6:17                                 ` Xufeng Zhang
2012-07-31  6:51                                   ` xufeng zhang
2012-08-02 21:17                                     ` Vlad Yasevich
2012-08-03  2:24                                       ` xufeng zhang

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=20120722.124514.239340989320198501.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sctp@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sri@us.ibm.com \
    --cc=vyasevich@gmail.com \
    --cc=xufengzhang.main@gmail.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).