[lkml]   [2012]   [Jul]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH] sctp: Make "Invalid Stream Identifier" ERROR follows SACK when bundling
    On Thu, Jul 19, 2012 at 01:57:30PM +0800, wrote:
    > 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 <>

    Not sure I understand how you came into this error. If we get an invalid
    stream, we issue an SCTP_REPORT_TSN side effect, followed by an SCTP_CMD_REPLY
    which sends the error chunk. The reply goes through
    That last function checks to see if a sack is already part of the packet, and if
    there isn't one, appends one, using the updated tsn map. So Can you explain in
    some more detail how you're getting into this situation?


     \ /
      Last update: 2012-07-23 03:21    [W:0.022 / U:37.024 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site