On 16-10-25 06:34 AM, Marcelo Ricardo Leitner wrote:
On Tue, Oct 25, 2016 at 05:05:41PM +0800, Xin Long wrote:
in case [1], user can't see the ENOMEM, ENOMEM is more like
Thing is, it may lead to duplicate messages in Application layer, as the
msg that was errored out may have been actually queued and later
retransmitted.
That's why I said the recovery steps from this depends on the
application on top of SCTP, if it can handle such duplicate messages or
not.
Yes, I was worried about duplicate messages.
Which is a bug on SCTP implementation on Linux, unfortunately. IOW,
transport should take care of duplicates - not the app.
i.e any app change is a workaround which will be unnecessary in newer
kernels.
cheers,
jamal
--
To unsubscribe from this list: send the line "unsubscribe linux-sctp" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
