[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [lwip-devel] Bad memory ref in tcp_input() after tcp_close()
From: |
Per Ekman |
Subject: |
Re: [lwip-devel] Bad memory ref in tcp_input() after tcp_close() |
Date: |
Thu, 23 Jan 2014 11:20:08 +0100 |
User-agent: |
Gnus/5.110009 (No Gnus v0.9) Emacs/22.2 (gnu/linux) |
"address@hidden" <address@hidden> writes:
> Valery Ushakov wrote:
>> [..]
>> Arguably, callback must not return ERR_OK in this case, since by
>> calling tcp_close() without acknowledging incoming data it effectively
>> aborts the connection.
>> [..]
>> If the close is indeed intended to abort the
>> connection, then callback should return ERR_ABRT.
>
> I didn't quite get it, yet, but I think returning ERR_OK after calling
> tcp_close() should always be OK for application code. I don't want to
> force people writing raw api code to have to know too much about
> TCP...
I agree, this is how I understood the documentation.
> Could anyone file a bug, please?
I finally managed to get a login on my third try.
This bus has been filed as #41318.
https://savannah.nongnu.org/bugs/index.php?41318
Sincerely
Per Ekman
H&D Wireless AB