[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [bug #26267] Simultaneous close
From: |
Greg Nelson |
Subject: |
[lwip-devel] [bug #26267] Simultaneous close |
Date: |
Tue, 16 Jun 2009 20:22:23 +0000 |
User-agent: |
Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.0.3705) |
Follow-up Comment #20, bug #26267 (project lwip):
I have a possibly related issue that needs to be considered when looking at
what to do with SND_NXT and SND_MAX.
When an LWIP client closes a connection (leaving the socket in LAST_ACK
state), and then receives an ACK that covers outstanding data *AND* the FIN,
the following test in tcp_process() fails:
if (flags & TCP_ACK && ackno == pcb->snd_nxt) ...
because ackno is *greater than* pcb->snd_nxt. It is equal to pcb->snd_max,
actually. As far as I can tell, this is completely legal (comprehensive ACK)
but not handled correctly.
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?26267>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/