linux-kernel - Re: Address already in use problem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CADvbK_fk1vQ2hR5yF0Z2agTOZdjSHNwnq-Nk5LQ_m3=jDSqUHg@mail.gmail.com>
Date:   Thu, 22 Sep 2016 01:28:12 +0800
From:   Xin Long <lucien.xin@...il.com>
To:     Marcelo Ricardo Leitner <marcelo.leitner@...il.com>
Cc:     Sun Paul <paulrbk@...il.com>, linux-sctp@...r.kernel.org,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: Address already in use problem

On Wed, Sep 21, 2016 at 10:21 PM, Marcelo Ricardo Leitner
<marcelo.leitner@...il.com> wrote:
> On Wed, Sep 21, 2016 at 10:15:43PM +0800, Sun Paul wrote:
>> Hi
>>
>> 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.leitner@...il.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.