On Wed, Sep 21, 2016 at 10:21 PM, Marcelo Ricardo Leitner
> On Wed, Sep 21, 2016 at 10:15:43PM +0800, Sun Paul wrote:
>> we are using redhat 2.6.32-642.4.2.el6.x86_64
>> On Wed, Sep 21, 2016 at 10:04 PM, Marcelo Ricardo Leitner
>> <marcelo.leit...@gmail.com> wrote:
>> > Hi,
>> > Which kernel are you using? Depending on it, that may be fixed by a
>> > recent patchset from Xin Long, 'sctp: fix the transmit err process'
>> > patchset more exactly.
>> > Marcelo
> Ah no, then that's another thing. If you cannot test/use an upstream
> kernel, then I'd recommend you to open a support case/bug with them.
It may be still this issue, I checked the codes of 2.6.32-642.
It's not using sctp_datamsg_free, which means once sctp_primitive_SEND
fail to send msg because of the asoc->state is unavailable, chunks have no
chance to be freed, and they hold asoc each one. so Address already in use.